Closed ryanlovett closed 8 years ago
I think it's because if jupyterhub is starting it, and it sets ip to ''. I've pushed a PR to fix it at https://github.com/jupyterhub/jupyterhub/pull/740
We can also work around this in nchp, but should put it in app.py rather than the jinja template.
Intermediate workaround is to set:
c.JupyterHub.ip = '0.0.0.0'
in your jupyterhub_config.py file
@ryanlovett can you try https://github.com/yuvipanda/jupyterhub-nginx-chp/pull/8
The patch worked! (modulo a small syntax issue) The host is no longer empty.
Despite the traitlet default of 0.0.0.0, if I don't append
--NCHPApp.public_ip=0.0.0.0
to c.JupyterHub.proxy_cmd, the nginx config will havelisten :<myport> ssl;
which will cause nginx to error withI can workaround this with the patch so that the listen line becomes
listen <myport> ssl;
which is fine in this instance. The real problem is that public_ip is getting overridden I guess, but I'm not sure how.