Attention: Due to an upgrade beginning on Friday, the 22nd August 2025, any new collabs, groups and any changes to teams will not be kept beyond the weekend. User creation will also be disabled during this time. The actual upgrade will take place on Wednesday, 27th August. On that day, any service requiring a Keycloak login will be unavailable for the duration of the upgrade. Thank you for your understanding as we complete this important work.

For the duration of the maintenance period, Collaboration and Group creation features will be temporarily disabled and will return HTTP 503 Service Unavailable errors until further notice.


Troubleshooting

Version 9.1 by kindler on 2021/06/16 13:56

Problems with the Jupyter notebook environment ("Lab")

Error message "Error in Authenticator.pre_spawn_start: ... 401: Unauthorized"

When a new user accesses the Lab in a new collab for the first time, it is possible, that the JuypterLab is not starting and instead shows a "...401 Unauthorized" message.

To fix this error, please access the "Drive" link in the collab once (the "Drive" is also in the left hand navigation menu of the Collab). After the "Drive" has been accesses once the JupyterLab should start.

No example notebooks in the Jupyter notebook environment ("Lab")

When starting the Jupyter notebook environment for the first time it takes about a minute (without visible "in progress" indication) until the example files appear in the file-chooser. Until then the list is just empty. So the fix here is "have a minute patience"

NoFiles.png

Timeout when starting the Jupyter notebook environment ("Lab")

It is possible, that accessing the "Lab" link results in a "timeout" message. This can happen, when the lab environment is started for the first time on one of the virtual machines providing the service, as the very first start per machine takes quite some time (in the order of 2 minutes). Accessing the "Lab" link again after a few minutes usually works.