ryanlovett / nbnovnc Goto Github PK

Not sure yet if this is an issue with the proxy, the choice of packages, or...

After I start the VNC session, I am usually kicked out pretty quickly with the message:

Server disconnected (code: 1005)

Right-clicking on the desktop is a pretty reliable way (maybe 30% chance each time) to prompt the disconnect, although other actions may trigger it too. This does not happen when I use the notebook that starts the session by hand as here: https://mybinder.org/v2/gh/ryanlovett/binder-novnc/master?filepath=start_vnc.ipynb

I suspect the binder configuration needs some version pins added somewhere. I tried the binder link today, and while it worked a couple of months ago, now the VNC handshake never completes.

Hello,

I came across this jupyter extension, and it seems very promising. I'm currently working on building a new research computing HPC cluster, and we use jupyterhub with this batch spawner extension which creates a new jupyterlab session.

I was working on installing nbnovnc, but after following the instructions in the readme, I don't seem to have any kind of option relating to a VNC session in jupyterlab. I tried adding a configuration option as defined in the readme, and no errors were thrown, and I can confirm the extension is enabled by running jupyter nbextension list. Any ideas on this?

JupyerLab Version: 1.1.4, running on Ubuntu 18.04

Don't use the hard coded template. Let them be specified by a traitlet.

Is there a straightforward way to get the VNC session to show up in the "running" tab of the notebook? I'm looking for a straightforward way to shut down the vnc server / session while still leaving jupyter running.

Choosing :0/5900 works in a single user container but not necessarily in other environments.

Again, thanks for taking the initiative to throw this together! I've gotten a great response in some demos I've run lately, and I've been asked to put some effort into moving this from proof-of-concept to something we're comfortable deploying at some kind of beta level. So I'd like to propose a roadmap for doing that.

• As you observe in #2 the extension should be less opinionated and more configurable (through traitlets?)
• Apropos of this, test with other VNC implementations (I'll probably be targeting tightVNC here)
• As mentioned in #1 see about adding some kind of heartbeat to keep the channel open
• #4 and #5 are good to address but simply making the display port configurable is probably enough for now

Thoughts? I will be working along these lines over the next few weeks, but it would be great to coordinate and try to avoid duplication of effort and/or working in conflicting directions.

So I've just gotten this working on a CentOS system. For reasons beyond my understanding, Debian derivatives ship with TightVNC, but RedHat derivatives use TigerVNC. This results in different executable naming (/usr/bin/Xvnc vs /usr/bin/Xtightvnc) and different defaults. In particular, TigerVNC defaults to security settings that wind up requiring the user to input a (not existing) password.

In my CentOS container I got around this by creating a /usr/bin/Xtightvnc shell script like:

#!/bin/sh
exec /usr/bin/Xvnc $@ -localhost -SecurityTypes=None

But it would be nicer to be able to either configure the command that supervisor runs, or at least drop a script like that in a less-hardcoded location.

SuperviseAndProxyHandler is supervising circus for us, but is actually proxying novnc. I need to configure circus to open the socket for novnc.

We currently use the notebook extension to visit vnc_auto.html and pass in a query string parameter to set the path to the websocket. Visiting /novnc should be sufficient to get things going.

See TigerVNC/tigervnc #639. This should simplify nbnovnc.