You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi
I need some help setting up this plugin.
Can anyone comment if this should work when jupyterhub is behind a reverse proxy?
I have managed to see the page "Waiting for decode worker", then after timeout I get the connect.html but not success from there.
The logs show "Websocket connection established to ws://localhost:38631/" so it seems there are no websocket problems, but I am not sure. The host reverse proxy forwards to the jupyterhub proxy, but I am not sure websockets are also forwarded, because they use a random port, as 38631.
Other potential problem is the AES encryption. The connect page shows 3 options: AES-CBC, AES-CFB and AES-CTR. The plugin sends encryption=AES without more details.
Thanks
Victor
The text was updated successfully, but these errors were encountered:
Hi Victor,
this plugin starts an xpra session with the command you find here
The port is choosen by jupyter-server-proxy and fixed as you can see here
same as the encryption as you can see here
The AES key and the token are passed through the URL as you can see here
I would suggest you check your setup starting an xpra session manually on your system first and try to use jupyter-server-proxy's arbitrary-port-access ability to access it. This plugin is not doing anything else, just in a more convenient way.
Hi
I need some help setting up this plugin.
Can anyone comment if this should work when jupyterhub is behind a reverse proxy?
I have managed to see the page "Waiting for decode worker", then after timeout I get the connect.html but not success from there.
The logs show "Websocket connection established to ws://localhost:38631/" so it seems there are no websocket problems, but I am not sure. The host reverse proxy forwards to the jupyterhub proxy, but I am not sure websockets are also forwarded, because they use a random port, as 38631.
Other potential problem is the AES encryption. The connect page shows 3 options: AES-CBC, AES-CFB and AES-CTR. The plugin sends encryption=AES without more details.
Thanks
Victor
The text was updated successfully, but these errors were encountered: