the-littlest-jupyterhub
the-littlest-jupyterhub copied to clipboard
jupyterhub
Terminal is blank - is port forwarding port 443 required?
When opening a new>terminal page from JupyterHub, the terminal is blank. I have a new install on AWS and followed all instructions (https://the-littlest-jupyterhub.readthedocs.io/en/latest/install/amazon.html) up to: Step 3, item 1 - Log in as an admin user and open a Terminal in your Jupyter Notebook. When I select new>terminal the terminal page opens on /user/xxx/terminals/1 and the top navigation bar is displayed, but the rest of the screen is grey. The server is a fresh install of the Ubuntu 18.04LTS AMI on EC2, with no HTTPS enabled (yet). Nothing looks wrong in the system log Client machines I have tested it on are Chrome, Firefox and Edge, on Windows and ChromeOS.
I am getting a similar issue with a non-interactive terminal, are you able to make and run some simple code in a notebook?
I just had a TLJH running on AWS the past few days and my terminal was fine. I wonder if it is the size of the system? I used the T1.medium size and had no issues. It was myself (admin) and one other person using it.
I am having this same problem on Google cloud. It seems everything installed correctly (logs looked fine with no errors), and I can login and even tried switching the url to the Lab option. But still get a non-responsive command window, and code will not run in the notebook either.
Tested it on both Chrome and Firefox with the same problem.
I have solved this issue with Google Cloud. Before I tried the TLJH, I tested a hub with a Kubernetes cluster. I then deleted the hub before attempting to do the TLJH install, however there were some files that weren't removed from my attached cloud shell storage. Once I ensured that all previous attached storage were either removed or reset and no previous files were remaining, I did a new install and it worked perfectly. I am not sure what files are the cause, but would recommend ensuring things are cleaned out from a previous install and see if that solves your problem.
I am also having similar issue ... I running an instance of TLJH in an EC2 instance .. i have port 80 opened on the public IP .... and when I try to access the terminal .. its blank and the developer tool console saids
terminado.js:4 WebSocket connection to 'ws://public_ip/terminals/websocket/1' failed: Error during WebSocket handshake: Unexpected response code: 400
traefik must be running ok since i could get to the hub login page and login ..
@greg-dusek I have install on a fresh ubuntu AMI more than 20 times today .. so there should be any left over files .. I also read somewhere about tornado version .. but that didn't help
Please help!!
Same issue here, non-responsive terminal, and code will not run in the notebook. AWS install using the TLJH tutorial on a 16 cores instances.
It seems the notebook is marked busy with constant connection/disconnection to the kernel
@victorkwannearmap Your sleuthing is interesting. You may not recall now, but did you only have port 80 open? You only mention that one. The directions say to open port 443, too. And so my idea is that the failing connection to the terminals/websocket you reference is trying to use WebSocket Secure (WSS) for a secure TLS/SSL connection, which uses port 443 by default.
The directions use changing the field to HTTPS as part of the process to get port 443 open, but I suspect, based on your post, that port is also possibly used by the WebSocket connection. The first post in this thread clearly stated not enabling HTTPS and that would be consistent.
Thanks @fomightez I think you are onto something!
Action points
- [ ] Figure out if this can happen also if accessing the hub via https Has anyone experienced that this can happen with HTTPS connections as well?
- [ ] Figure out if the terminal requires inbound 443 traffic to be accepted, and/or also a HTTPS certificate to be accepted
- [ ] Document findings
