HTML export is not loading on codeberg pages but is working with python3 http.server

Godot Version

v4.3.stable.flathub [77dcf97d8]

Question

I’ve created a game (beta version) called AntiBillard (open source, source code on Codeberg). If I export it as html and publish it on Codeberg Pages, it is not loading and the progress bar stopped somewhere while loading.

What I have done

  • export the game to html with the export settings published on codeberg repo main branch.

What happens

  • If I clone the pages to my laptop and clear the browser cache and run python3 -m http.server, I can open the game using the url https://localhost:8000. The game is loading and I can play it.
  • If I clear the browser cache and open the game using the web page AntiBillard , it is not loading - progress bar get stuck. If I open the developer settings in Firefox or Chrome (F12), I can see some error message I didn’t understand (Chrome):
index.js:150 Uncaught (in promise) CompileError: WebAssembly.instantiateStreaming(): section (code 10, "Code") extends past end of the module (length 38742554, remaining bytes 19678636) @+263191
    at index.js:150:17
(anonymous) @ index.js:150
Promise.then
start @ index.js:149
getTrackedResponse @ index.js:147
(anonymous) @ index.js:166
Promise.then
loadFetch @ index.js:162
retry @ index.js:185
Preloader.loadPromise @ index.js:231
Engine.load @ index.js:672
init @ index.js:712
startGame @ index.js:831
(anonymous) @ AntiBillard/:182
(anonymous) @ AntiBillard/:196

Firefox:

Uncaught (in promise) TypeError: Error in input stream

That I would expect

  • The html export is playable with python3 -m http.server
  • The html export is playable on Codeberg Pages, too.

Is this reproducible?

No, is is not always reproducible: Sometimes it is loading, sometimes this error occurs.

EDIT: It turns out that this issue only exist on LAN (loads slowly), not on WLAN (loads faster).

It turns out that this error is caused by Codeberg Page, not by Godot and its export feature.