-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ensure project works against TurboVNC - currently broken? #98
Comments
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 |
Summary of how this project work(extracted to #98) |
What goes wrong?The browser manages to connect to the jupyter-server-proxy provided websocket, but it doesn't seem like that Jupyter server logs after pressing the Desktop JupyterLab launcher button the first timeIt 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 (
TurboVNC reports the following in
The logs from TurboVNC looks similar to the logs from TigerVNC, also including some CRITICAL entries:
Not configuring port?Turbo VNC reported:
jupyter-server-proxy reported:
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 #96 (comment)
The text was updated successfully, but these errors were encountered: