Ffmpeg Stucked on Loading: SharedArrayBuffer is not defined

[leonard4546]

Thanks for this project. I deployed this using docker but I'm getting issue related to ffmpeg on webapp.

It keeps loading and throws error: SharedArrayBuffer is not defined

I read about it online, and seems like it is related to ffmpeg-core.

Can you help me in this?

and BTW there's one typo in readme file in docker run command. -p flag is missing.

Correct Command:
docker run -p 127.0.0.1:3000:3000 ffmpeg-web

Thank You

[dinoosauro]

Hi! Thank you for reporting this issue. That's strange: I tried setting up the Docker container on my machine (Linux Mint 21) and it seems to work. May I ask you which browser and OS you are using? Also, if you open the DevTools and write crossOriginIsolated in the console, which is the returned value?
In any case, I've done some quick searches about ffmpeg.wasm and it seems that now it's possible to run a slower version without SharedArrayBuffer. If, for some reason, we can't figure out why this error is triggered, I might implement it as a fallback when these type of errors occur
Thanks also for fixing the command – I'll update the README when I'll add that fallback in the following days

[leonard4546]

Hey, thanks for reply. I found the issue.

I am running it on vps and tried to access it using ip_address:3000, and it was throwing error because of that.

It's working if I run it locally and expose it using tunnel.

I had used this command before: docker run -p 3000:3000 ffmpeg-web

[velkrosmaak]

I had used this command before: docker run -p 3000:3000 ffmpeg-web

I also did this as using the supplied docker run 127.0.0.1:3000:3000 ffmpeg-web gave me docker: invalid reference format.

Could you elaborate on this bit?

It's working if I run it locally and expose it using tunnel.

What did your final docker CLI command look like? I can't browse to the docker instance locally as it's running on a headless ubuntu VM, I want to be able to access ffmpeg-web from any device on my network which I kinda thought was the whole purpose.

[thirdwheel]

Ok I had to set up an SSL reverse proxy to get this to work. It will not work in plain HTTP as far as I can see.