The code snippets and file system paths here fit an installation according to 1and1/debianized-jupyterhub. If you installed in another way, you have to adapt accordingly.
First, look into the log for anything out of the ordinary, using journalctl -eu jupyterhub
. Also try with an increased log level by setting JUPYTERHUB_LOGLEVEL=DEBUG
in /etc/default/jupyterhub
, and then restarting the hub service with systemctl restart jupyterhub
.
If you cannot see anything in the journal, the best route is to get more visibility and direct control by running a notebook server manually, in a shell prompt for your user account.
First, create a local configuration file.
/opt/venvs/jupyterhub/bin/jupyter notebook --generate-config
${EDITOR:-vi} ~/.jupyter/jupyter_notebook_config.py
Change these two settings:
c.NotebookApp.allow_remote_access = True
# Use empty string for bind-all, or your hostname
c.NotebookApp.ip = 'localhost'
Then start a notebook server, its log goes into your console window.
/opt/venvs/jupyterhub/bin/jupyter notebook .
Watch the console for any errors or other diagnostics while you try to reproduce your problem.
💡 Use Ctrl-C
twice to stop the server after you're done.
Finally, move your local configuration out of the way, since it might interfere with JupyterHub operations.
( cd ~/.jupyter && mv jupyter_notebook_config.py jupyter_notebook_config.py,debug )