Trying to deploy webgl build, but the app is not running after successful upload

[Naima]

Hey there,
I have deployed a WebGL build to run it, However it keeps giving me an error

My site : Unity WebGL Player | YEETRASH

actually the file with an extension of .br (Brotli compression), I searched and mostly they are saying to build again with the compression disabled formate

But I don’t think its a good solution, nor I can change the format If someone can help me in this would be great


Thanks in Advance

[hrishikesh]

Related and probably useful:

Serving pre-compressed Brotli files

This is a follow-up to this comment: https://answers.netlify.com/t/gzip-file-serving/3445/15 In relation to this site: https://hugo-stork.netlify.app As part of the build process, a 6.0 MB binary file (stork.index.json) is created in the root of site, consumed by a Wasm file for embedded site search. By giving the file a json extension[1], Netlify compresses with Brotli to produce a 2.1 MB file. This is excellent. However, with aggressive Brotli compression ( -q 11) we can reduce the file s…

Netlify corrupting served data files by compressing already-compressed files

In my app we have some large (10-20 MB) wasm and data files that we pre-compress using Brotli in-order to minimize bandwidth. For example, this file https://62b142977e4d505a425e9438--adoring-tesla-fc69b1.netlify.app/spatial-webgl/Spatial_6.25.0_250c0f59_dev/Build/WebGL.wasm.br. It appears that Netlify is Brotli compressing the file again when serving it. At runtime, I’m getting WebAssembly compilation issues like this: CompileError: WebAssembly.instantiate(): expected magic word 00 61 73 6d, f…

[Naima]

have done with this, with compression disabled formate

Now the site is deployed but still not running showing me an alert that the unsecured WebSocket connection can’t be loaded over HTTPS, as I am using a NodeJs WebSocket server with ws protocol,

do you know any workaround, the WebSocket server running on AWS, and was is not working

[hrishikesh]

@Naima

do you know any workaround

The only one that I know is to add a SSL certificate to AWS to that it serves over HTTPS. Note that, please don’t try to make it work on HTTP - that would be a big security concern.