Nextcloud on Umbrel fails to start after reboot — shows “Starting” then “Not started”

Support and Troubleshooting
1

Hi everyone,

I’ve been struggling with Nextcloud on my Umbrel installation — it shows “Starting” in Umbrel’s dashboard after a reboot, but eventually flips to “Not started” and the containers never run. Reinstalling Nextcloud didn’t help; it still fails to auto‑start. Other apps on Umbrel start fine.

Here are the details and what I’ve tried so far:

What I observed

  • After reboot, Nextcloud’s web & cron containers are in Docker’s Created state (not running).

  • When I manually docker start or via Umbrel UI, Nextcloud starts and works fine (valid logs, web UI, etc.).

  • I changed restart policies (to unless-stopped) for all Nextcloud containers (web, cron, db, redis), but it still doesn’t auto-launch on boot.

  • In Umbrel’s logs (journalctl -u umbrel -f), I see:

    dependency failed to start: container nextcloud_db_1 is unhealthy
Error: Command failed with exit code 1: /opt/umbreld/source/modules/apps/legacy-compat/app-script start nextcloud

    Even though Docker reports the DB container is healthy (inspect shows .State.Health.Status = "healthy").

What I’ve tried

  • Inspecting logs: docker logs nextcloud_web_1 and docker logs nextcloud_cron_1 — empty (they never start).

  • Inspecting DB health and logs — DB container is running and healthy.

  • Reinstalling Nextcloud via Umbrel, hoping it’d repair whatever broken state, but same behavior persists.

  • Ensuring file/folder permissions on the data directories, verifying volumes are intact.

  • Manually starting the containers works (web, cron come up).

I’m running UmbrelOS 1.5 Beta 2 on Raspberry Pi 4 8GB. If it’s helpful, I can also share the docker-compose.yml I’m using, and full Umbrel logs. Thanks in advance for any pointers or suggestions — I’m stuck and would love to get this working reliably on boot.

2

That is very weird. Since you already tried reinstalling the app, we would need to find out specifically why it’s not able to use the db. Could you share the full logs from going into Settings > Troubleshoot > App > nextcloud? And seeing the docker-compose could be useful if you modified it otherwise I can just look at mine for reference.

3 
nextcloud_redis_1  | 1:C 22 Oct 2025 20:26:43.905 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
nextcloud_redis_1  | 1:C 22 Oct 2025 20:26:43.906 # Redis version=6.2.2, bits=64, commit=00000000, modified=0, pid=1, just started
nextcloud_redis_1  | 1:C 22 Oct 2025 20:26:43.906 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
nextcloud_redis_1  | 1:M 22 Oct 2025 20:26:43.910 * monotonic clock: POSIX clock_gettime
nextcloud_redis_1  | 1:M 22 Oct 2025 20:26:44.111 * Running mode=standalone, port=6379.
nextcloud_redis_1  | 1:M 22 Oct 2025 20:26:44.111 # Server initialized
nextcloud_redis_1  | 1:M 22 Oct 2025 20:26:44.111 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add ‘vm.overcommit_memory = 1’ to /etc/sysctl.conf and then reboot or run the command ‘sysctl vm.overcommit_memory=1’ for this to take effect.
nextcloud_redis_1  | 1:M 22 Oct 2025 20:26:44.575 * Loading RDB produced by version 6.2.2
nextcloud_redis_1  | 1:M 22 Oct 2025 20:26:44.575 * RDB age 129 seconds
nextcloud_redis_1  | 1:M 22 Oct 2025 20:26:44.575 * RDB memory usage when created 0.82 Mb
nextcloud_redis_1  | 1:M 22 Oct 2025 20:26:44.576 * DB loaded from disk: 0.222 seconds
nextcloud_redis_1  | 1:M 22 Oct 2025 20:26:44.576 * Ready to accept connections
nextcloud_db_1     | 2025-10-22 20:26:41+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.6.21+maria~ubu2004 started.
nextcloud_db_1         | 2025-10-22 20:27:00+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
nextcloud_db_1         | 2025-10-22 20:27:00 0 [Note] Starting MariaDB 10.6.21-MariaDB-ubu2004 source revision 066e8d6aeabc13242193780341e0f845528105de server_uid QdcSLmRYiUsPnJt70wyiaRsXbTI= as process 1
nextcloud_db_1         | 2025-10-22 20:27:00 0 [Warning] You need to use --log-bin to make --binlog-format work.
nextcloud_db_1         | 2025-10-22 20:27:00 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
nextcloud_db_1         | 2025-10-22 20:27:00 0 [Note] InnoDB: Number of pools: 1
nextcloud_db_1         | 2025-10-22 20:27:00 0 [Note] InnoDB: Using ARMv8 crc32 instructions
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_db_1         | 2025-10-22 20:27:00 0 [Note] InnoDB: Using Linux native AIO
nextcloud_db_1         | 2025-10-22 20:27:00 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
nextcloud_db_1         | 2025-10-22 20:27:00 0 [Note] InnoDB: Completed initialization of buffer pool
nextcloud_db_1         | 2025-10-22 20:27:11 0 [Note] InnoDB: 128 rollback segments are active.
nextcloud_db_1         | 2025-10-22 20:27:12 0 [Note] InnoDB: Creating shared tablespace for temporary tables
nextcloud_db_1         | 2025-10-22 20:27:12 0 [Note] InnoDB: Setting file ‘./ibtmp1’ size to 12 MB. Physically writing the file full; Please wait …
nextcloud_db_1         | 2025-10-22 20:27:12 0 [Note] InnoDB: File ‘./ibtmp1’ size is now 12 MB.
nextcloud_db_1         | 2025-10-22 20:27:12 0 [Note] InnoDB: 10.6.21 started; log sequence number 57506614; transaction id 105291
nextcloud_db_1         | 2025-10-22 20:27:12 0 [Note] Plugin ‘FEEDBACK’ is disabled.
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_db_1         | 2025-10-22 20:27:12 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
nextcloud_app_proxy_1  | Retrying…
nextcloud_db_1         | 2025-10-22 20:27:12 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
nextcloud_db_1         | 2025-10-22 20:27:12 0 [Note] Server socket created on IP: ‘0.0.0.0’.
nextcloud_db_1         | 2025-10-22 20:27:12 0 [Note] Server socket created on IP: ‘::’.
nextcloud_db_1         | 2025-10-22 20:27:17 0 [Note] mariadbd: ready for connections.
nextcloud_db_1         | Version: ‘10.6.21-MariaDB-ubu2004’  socket: ‘/run/mysqld/mysqld.sock’  port: 3306  mariadb.org binary distribution
nextcloud_db_1         | 2025-10-22 20:27:33 0 [Note] InnoDB: Buffer pool(s) load completed at 251022 20:27:33
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…
nextcloud_app_proxy_1  | Error waiting for port: “The address ‘nextcloud_web_1’ cannot be found”
nextcloud_app_proxy_1  | Retrying…