Couldn't launch WebCT in Chrome

[gbzan]

I downloaded the Windows version WebCT from https://github.com/WebxCT/WebCT. I extracted the folder, double-click WebCT.exe to launch.

I couldn't launch it, the display in the Chrome is wired, as shown in the picture. I also uploaded a log file in case it is help. Could you give me any guidances to fix this?
Thanks,
Guibin

WEB-16-15.log

[WYVERN2742]

Hi and thanks for trying out WebCT!

From the looks of the logs and image, it seems like the frontend UI's scripts are failing to load. WebCT uses components from shoelace.style which are served from jsdelivr. At the moment these aren't bundled, meaning WebCT requires internet access to use.

Is offline access important for you? I can prioritise offline as a feature (#24), although my free development time on WebCT is limited for the new few months

If it helps, WebCT is validated on google chrome 136.0.7103.49 (latest) and I can confirm it works on my side using the v1.0.0 WebCT release.

[gbzan]

Thank you for quick response.
I solve the problem by using the address: 127.0.0.1:2742, instead of localhost:2742. Now the display works fine. I am not sure how this works, maybe the localhost setting in my computer is not correct. My google chrome version is: 136.0.7103.49 (latest) and this computer has the internet.

[WYVERN2742]

Hmm, that's strange, especially since localhost is commonly defined as a hostlookup, and I'm unable to reproduce using my version of chrome on the same version.

I suspect it's likely a CSRF error of some sort, but I'm unable to reproduce

[chou1404]

Thank you for quick response. I solve the problem by using the address: 127.0.0.1:2742, instead of localhost:2742. Now the display works fine. I am not sure how this works, maybe the localhost setting in my computer is not correct. My google chrome version is: 136.0.7103.49 (latest) and this computer has the internet.

I also encountered the same problem, have you solved it？ thank you

[WYVERN2742]

Thank you for quick response. I solve the problem by using the address: 127.0.0.1:2742, instead of localhost:2742. Now the display works fine. I am not sure how this works, maybe the localhost setting in my computer is not correct. My google chrome version is: 136.0.7103.49 (latest) and this computer has the internet.

I also encountered the same problem, have you solved it？ thank you

Does launching WebCT and then navigating to http://127.0.0.1:2742 solve the issue for you? In the next release I'll default to 127.0.0.1 rather than localhost, I'm still unable to reproduce this error across multiple computers and laptops, and therefore unable to debug this currently.

[chou1404]

I guess the problem is that the jsdelivr CDN service cannot be loaded normally in some countries, perhaps due to a server failure or node failure. Is there a way to use it offline, or to modify the jsdelivr node?

[WYVERN2742]

I guess the problem is that the jsdelivr CDN service cannot be loaded normally in some countries, perhaps due to a server failure or node failure. Is there a way to use it offline, or to modify the jsdelivr node?

Good catch! I didn't think of the fact that jsdelivr could be failing due to other reasons (but that still brings into question why 127.0.0.1 worked over localhost)

I'll take a look at bundling shoelace (the only thing we retrieve from jsdelivr) in with the next build of WebCT, this'll result in no external endpoints required so you could use WebCT entirely offline.

I'm currently working on detector gain and source flux modelling with v1.1.0, so this should be out within the next few weeks

[WYVERN2742]

I guess the problem is that the jsdelivr CDN service cannot be loaded normally in some countries, perhaps due to a server failure or node failure. Is there a way to use it offline, or to modify the jsdelivr node?

Good catch! I didn't think of the fact that jsdelivr could be failing due to other reasons (but that still brings into question why 127.0.0.1 worked over localhost)

I'll take a look at bundling shoelace (the only thing we retrieve from jsdelivr) in with the next build of WebCT, this'll result in no external endpoints required so you could use WebCT entirely offline.

I'm currently working on detector gain and source flux modelling with v1.1.0, so this should be out within the next few weeks

I've got vendor bundling working well, I can confirm the next version of WebCT will be entirely self-hosted and offline compatible 🎉

I'll close this issue when v1.1.0 is out!