jupyterhub 4.0.1 doesn't load jupyterlab automatically if Spawner.default_url is "/lab" #4510
Comments
Frank-Steiner
changed the title
|
I was able to find the reason as we had different users with some being able to access the GUIs, others getting the 404. The difference was that the working users had a file Thus, jupyterhub 4.x is not enabling the jupyterlab extension automatically if is set in the config. 3.x does. So I'm not sure if this is a bug or a design change, but I guess it makes sense to activate the jupyterlab extension automatically if that's set to be the default interface... |
|
Indeed, jupyterhub 4 loads itself as a jupyter server extension and no longer enables any other extensions itself. You can opt-out of the new extension implementation with JupyterHub 3 launches jupyter-labhub by default, which had the main effect of setting the default default url to But to the issue at hand, installing jupyterlab generally creates the file You might double check the permissions on It's unclear to me why it's not being enabled by default (possibly a peculiar environment, path, or permissions issue), but the solution is to ensure that the jupyterlab extension is enabled, e.g. Exactly how/when/where that should be done will depend on how you manage the environment your users use, but from the looks of it, it should work with: /opt/jhub/bin/jupyter-server extension enable jupyterlab --sys-prefix |
|
We're seeing this today, too, when using current versions of r-notebook for singleuser image. We also have been trying the workarounds listed here ( Interestingly, the same config works for deploying with r-notebook:r-4.2.2, but not on r-notebook:latest. |
|
@vwbusguy this issue is about differences in behaviour between JupyterHub 3 and 4.
is a bug in the notebook repo: |
|
Investigating this issue in jupyter/notebook#6997, which should fix it I think. If someone from the hub team would like to review it that would be great, thanks! |
|
thanks @jtpio for fixing this in jupyter/notebook#6997 fwiw, i believe that we can probably close this issue. :) |
|
Thanks @shaneknapp @jtpio ! |
Bug description
After upgrading from jupyerhub 3 to 4.0.1 using the same config as before, any user logging in or starting a server from hub home ends up with
404 : Not Found. You are requesting a page that does not exist!Expected behaviour
jupyterlab should open.
Actual behaviour
I get the 404 error page.
How to reproduce
No idea... I also uninstalled jhub compeletely, removed the sqlite db, and installed 4.0.1 from fresh, and received the same problem. Reverting back to 3.1.1 works find, the jupyterlab page is found again, going to 4.0.1 again shows the 404 page. But I guess that's not happening for everyone else :-)
Your personal set up
OS: SuSE Linux Enterprise 15 SP4
Version(s): jupyterhub 4.0.1, python 3.10
Full environment
Configuration
Logs
That's the full set of journal log messages from starting jupyterhub, andlogging in until receiving the 404.The text was updated successfully, but these errors were encountered: