Hi Norman -
You are correct that Jupyterhub will serve without SSL simply by not
providing the SSL keys. There used to be an explicit "--no-ssl" flag but
that was deprecated with the 0.7 release.
My suspicion is that this is going to be more finicky than you would like.
Presumably you want users
Roland, hello.
On 22 Mar 2018, at 8:22, Roland Weber wrote:
Afaik, listening on two different ports is not possible without
changing
code.
Righto -- thanks for confirming.
You could also solve your problem by keeping JupyterHub on the
deprecated
SSL port, and encrypting the connection
Greetings.
It's not clear how I configure JuypterHub to run with plain HTTP rather
than HTTPS, or how to have it listen on two separate interfaces.
I plan to terminate SSL in an nginx reverse proxy, so I want JupyterHub
to to run without SSL. I can't work out quite how to do that: that is,
