Unable to connect noVNC to my x11vnc server in docker container

[Anu]

Hi, 

I'm running a playwright script in a Linux docker container on my Mac.

I run the playwright script head-fully using Xvfb, and i've set up an x11vnc server in the container (on port 5900), which I can connect to through my Mac's screen share utility. (I mapped port 5910:5900 when I run the container). I can easily view this and interact with the running browser this way.

However, I want to load the vnc in a browser window. 

When I run the noVNC server using the command,./novnc_proxy --vnc localhost:5900 --listen 6080 

the novnc server is unable to connect here, even though I've mapped port 6080:6080 in the docker run command

What am I missing in my set up?

[Anu]

Edit: The server not being "connected" means that I'm able to enter the VNC password successfully, but the VNC immediately "disconnects" and shows the message: "Disconnected". This is a different error message than my entering invalid credentials (so the error is not associated with that)

This is what the noVNC logs look like

172.17.0.4 - - [18/Sep/2024 03:32:52] 172.17.0.4: Plain non-SSL (ws://) WebSocket connection
172.17.0.4 - - [18/Sep/2024 03:32:52] 172.17.0.4: Path: '/websockify'
172.17.0.4 - - [18/Sep/2024 03:32:52] connecting to: localhost:5900

[Pierre Ossman]

On 18/09/2024 05:37, Anu wrote:
> Edit: The server not being "connected" means that I'm able to enter the VNC
> password successfully, but the VNC immediately "disconnects" and shows the
> message: "Disconnected". This is a different error message than my entering
> invalid credentials (so the error is not associated with that)
>
> This is what the noVNC logs look like
>
> 172.17.0.4 - - [18/Sep/2024 03:32:52] 172.17.0.4: Plain non-SSL (ws://)
> WebSocket connection
> 172.17.0.4 - - [18/Sep/2024 03:32:52] 172.17.0.4: Path: '/websockify'
> 172.17.0.4 - - [18/Sep/2024 03:32:52] connecting to: localhost:5900
>

What can you see in the logs from x11vnc?

Regards,
--
Pierre Ossman Software Development
Cendio AB https://cendio.com
Teknikringen 8 https://twitter.com/ThinLinc
583 30 Linköping https://facebook.com/ThinLinc
Phone: +46-13-214600

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?