docker behind nginx , websockify forwarding to docker to enable sound #262
-
hello , thank you very much for this docker image. i deployed it on my personal home server but I need to work with an nginx to route this docker container under a certain path . i referred to your instructions about the situation what the container behind nginx. and I applied this code (similar) to my nginx settings
the docker container started and I can see the firebox UI from localhost:port/firefox/ , but there is no sound . when I checked the terminal log , it is calling localhost:port/websockify-audio instead of going under /firefox/websockify as I might expect. which resulted in so sound in the browser. i could have done the following code in my nginx settings to also forward the websockify to that container.
but my problem is that the firefox docker container's port is different everytime as I want to setup multiple firefox docker containers at the same time using different port. so I am wondering if there is any suggestions or advises , any idea is welcome . much appreciated ! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
So the main VNC server (noVNC) uses websocket library (websock.js) to connect. It uses
It hardcoded the url as |
Beta Was this translation helpful? Give feedback.
-
Thank you for reporting. This is a bug that will be fixed in the baseimage. |
Beta Was this translation helpful? Give feedback.
So the main VNC server (noVNC) uses websocket library (websock.js) to connect. It uses
this._url
, which is whatever your current address, e.g.:wss://<domain>:443/firefox/websockify
The audio call for connecting is in noVNC (app/ui.js), in this function:
connectWebSocket()
It hardcoded the url as
document.location.hostname+':'+window.location.port+'/websockify-audio'
so we getwss://<domain>:443/websockify-audio
instead ofwss://<domain…