search

jlesage / docker-firefox

Docker container for Firefox
MIT License
1.61k stars 288 forks source link

Problem with Routing Based on URL Path #138

Closed ctonton closed 1 year ago

ctonton commented 1 year ago

I have followed the instructions in the README to set up a reverse proxy with Routing Based on URL Path in nginx, but no matter what I try, I am getting the same result. A red bar that says "X Failed to connect". The container works fine alone and a reverse proxy with Routing Based on Hostname also works, but I need to be able to call multiple apps by URL path.

jlesage commented 1 year ago

Looks like the WebSocket connection fails.

Did you check the logs of your reverse proxy to see if there is any clue ?

ctonton commented 1 year ago

I started fresh in a virtual machine and have the same result. I can not tell what is happening. It looks like noVNC can not connect to the vncserver when using this type of reverse proxy. I have attached a copy of the log from nginx and a copy of my default site. access.txt default.txt

ctonton commented 1 year ago

And here is a copy of the nginx log from the container itself. I don't recognize the server ip address in this log access.txt

jlesage commented 1 year ago

Could you try with version 1.18.0 of the image to see if you have the same issue ? This can be done by using the Docker image tag v1.18.0.

ctonton commented 1 year ago

I tested it and image v1.18.0 works fine. There must be something happening in the new version.

jlesage commented 1 year ago

Thanks of confirming. I found the issue and will provide a fix.

ctonton commented 1 year ago

The newest version is now working.