Closed consideRatio closed 6 months ago
I think what we pass now doesn't work with TurboVNC, or at least something is broken for TurboVNC right now. I have issues to get TurboVNC to provide something functional by doing.
docker run -p 8888:8888 --security-opt seccomp=unconfined -e JUPYTER_TOKEN=secret quay.io/jupyterhub/jupyter-remote-desktop-proxy:main-turbovnc
# then visiting http://127.0.0.1:8888/lab?token=secret
# then clicking on "desktop" button in jupyterlab
# possibly refreshing page a few times
# I should see the desktop now
Doing the same, but with -tigervnc
suffix works after one page refresh.
(extracted to https://github.com/jupyterhub/jupyter-remote-desktop-proxy/issues/98)
The browser manages to connect to the jupyter-server-proxy provided websocket, but it doesn't seem like that
It seems like we acquire index.html from /desktop/, load viewer.js referenced by the index.html, access /desktop-websockify/ and manages to open a websocket connection (Websocket connection established to ws://localhost:34489/
). But this is just one part, browser -> jupyter-server-proxy, then jupyter-server-proxy needs to successfully open a websocket connection to the VNC server as well, and this fails (Failed to connect to 127.0.0.1:55791: [Errno 111] Connection refused
).
TurboVNC reports the following in /home/jovyan/.vnc/f0407bb15b20:1.log
, compared to TigerVNC it misses a connection entry in the end:
The logs from TurboVNC looks similar to the logs from TigerVNC, also including some CRITICAL entries:
Turbo VNC reported:
08/03/2024 05:00:52 Listening for VNC connections on TCP port 5901
jupyter-server-proxy reported:
127.0.0.1 - - [08/Mar/2024 05:00:52] Failed to connect to 127.0.0.1:55791: [Errno 111] Connection refused
I think we start TurboVNC without detailing what port it should listen to, and that is the issue. Sure we can't use a unix socket - but we need to specify a port.
By @goekce in https://github.com/jupyterhub/jupyter-remote-desktop-proxy/pull/96#issuecomment-1972940545