Cloudron Forum

After updating Cloudron from v9.2.0 to v10.0.3, the integration no longer works. The Jupyter server doesn't even start anymore; instead, it displays the error message "500: Internal Server Error
Unhandled error starting server".
Here is the output from my log file:

Sep 01 08:26:54 [E 2026-09-01 06:26:54.598 JupyterHub user:1012](B Unhandled error starting [USER]'s server: 400 Client Error for http://172.18.0.1:3003/v1.55/containers/create?name=[UUID]-[USER]: Bad Request ("Binds must be under /app/data")
Sep 01 08:26:54 [E 2026-09-01 06:26:54.687 JupyterHub pages:364](B Error starting server [USER]: 400 Client Error for http://172.18.0.1:3003/v1.55/containers/create?name=[UUID]-[USER]: Bad Request ("Binds must be under /app/data")
Sep 01 08:26:54 [E 2026-09-01 06:26:54.690 JupyterHub log:184](B {
Sep 01 08:26:54 [E 2026-09-01 06:26:54.690 JupyterHub log:192](B 500 GET /hub/spawn/[USER] ([USER]@[IP-REDACTED]) 307.71ms

Have you considered this yet?
Or is there a practical way to set up an MQTT broker?
Is it possible to simply set up another Docker container alongside Cloudron?
Since the server already has a static IP address, it would be great if there were a way to run a broker.

@girish same problem as before

We have version v7.7.2.

Most of the files are probably located within Nextcloud. I counted up the user directories once: We have around 165000 files under /app/data/<user>/files/ with a size of 160GB.

How can I change the buffer size? Is there a command or do I have to change something directly in a file?

Hi,

my last backup failed with

saveFsMetadata errored with code ERR_CHILD_PROCESS_STDIO_MAXBUFFER message stdout maxBuffer length exceeded

I tried it again, but it crashes and I still get this error.
Can anyone tell me what is going wrong and how I can fix it?

If you want to share a volume with Jupyterlab, this is unfortunately not enough. Each user gets their own Jupyterlab container from a notebook image. By default, this is jupyter/datascience-notebook. However, no media group is created in this container. There is also no user cloudron.
Since I created my own image, I could simply create the group media and add the user Jovyan. Now it works.

That's okay with me.
Unfortunately, I've noticed another problem: I have also included the volume in the Nextcloud app. Files are uploaded here, which I then have to edit in Jupyterhub. But I don't have write permissions for this file. The user of the file is www-data. When I edit or create files in the Juyperhub app, it belongs to the user wcd.

Is there a way to fix this problem?

@girish I have tested and it works. I can share data with other users. But it is possible to get access to mounted volume from the user container? The mounted volume is only accessible in the Jupyterhub container, but not in the user container.

@girish Where or how can I find the log files from Jupyterhub?

No manual changes have been made so far.
I could not find jupyterhub-idle-culler in the list of 'pip list' in the terminal of the Jupyterhub container.

@girish: I have checked if the shutdown is related to an update and thus a restart of Jupyterhub. This is not the case.
There must be something running in the background of Jupyterhub that stops the notebook server/Docker container as soon as there is a certain amount of inactivity.

@girish: Yes, I use Cloudron to deploy Jupyterhub.

I would like to use the Jupyter Scheduler extension.

https://jupyter-scheduler.readthedocs.io/en/latest/users/index.html#installation

The installation is working fine.
I then set up a job that runs once a day. This also works without any problems.

However, I have noticed one issue. If I don't use the app for a few days, my notebook server is shut down and thus the job will not run again until I start the notebook server.

Is there a way to prevent the Notebook Server from shutting down in the Jupyterhub settings?

In the settings of Jupyterhub there are
c.DockerSpawner.volumes and
c.SwarmSpawner.read_only_volumes
(https://jupyterhub-dockerspawner.readthedocs.io/en/latest/api/index.html)

Would this perhaps be a possibility? Currently, however, these config settings do not work.

Since I have day files with data that I need to read and edit. Therefore it is very inconvenient if I would have to upload them manually. Besides, my colleagues also work with the data. So it would be great if there was a directory "shared" which is in the home directory. Great would be a setting in custumconfig.py like
c.DockerSpawner.volumes = {'/media/shareddata' : '/home/jovyan/shared'}

see also https://jupyterhub-dockerspawner.readthedocs.io/en/latest/data-persistence.html#volume-mapping

Is there already a solution here?

Hi,
is there a solution by now?

I have the same problem.

I'm using the media manager to upload the images. I can see the settings of the images but it doesn't appear in preview.

The files are stored under /app/data/data/media/

I insert the images on the wiki with {{ ::image.png?400 |}}

What is the reason that the images are not visible on the page?

Thanks for your help!