D’oh! I forgot about the /jhub. Thanks. Having done that, I can report wild success. I was able to login (different user this time, just to be sure there wasn’t a conflict) and started a notebook and cells are evaluated:
So, I guess this tells us that there’s something involved with the handoff from Apache that is messing things up. The firewall is still off. What else can I check?
Thanks for your patience!
Scott
PS: I repeated the experiment of talking directly to Jupyterhub but with the firewall running and it still worked, so I think the firewall is not the culprit.
PPS: I looked in the web console for the working version, and I saw this message:
Starting WebSocket: ws://localhost:8080/jhub/user/cs304node/api/kernels/73e49043-52d7-4246-a9d3-960a56ed3ca1
comparing that to the earlier connection that failed:
Firefox can’t establish a connection to the server at wss://cs.wellesley.edu/jhub/user/cs299/api/kernels/3828591a-fcf4-4bd3-9a1b-945cc9601ac9/channels?session_id=e680b4e2-2e08-4269-ab33-ab63c6f84a6c.
I notice the change in the protocol (ws: versus wss:), the change in the hostname:port (localhost:8080 is the SSH tunnel I set up to the jupyterhub server). But the path is entirely different, so maybe I’m comparing the wrong two URLs. The current reverse proxy rewrite rules are:
RewriteRule /jhub/(.*) wss://127.0.0.1:9389/jhub/$1 [P,L]
RewriteRule /jhub/(.*) http://127.0.0.1:9389/jhub/$1 [P,L]