Nextcloud container not starting after server reboot

[Runningman2552]

Hello,
I have a weird issue with the nextcloud containers (image: latest). When the nextcloud containers are running, they can be accessed normally. But when I do a server reboot, all other docker containers restart automatically, except the nextcloud containers. How can I solve this, help is greatly appreciated.
regards,
Stefan

[drizuid]

you've not provided any info that would allow anyone to even venture a guess. We support the container, not the application in the container, so we would need to see your docker run or compose and your container logs. your best bet may be to ask nextcoud.

[Runningman2552]

Here are the logs after a reboot:

~$ docker logs nextcloud-app
[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] 02-default-location: skipped
[migrations] done
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────
Linuxserver.io version: 35.0.0-ls452
Build-date: 2026-09-16T00:49:05+00:00
───────────────────────────────────────

using keys found in /config/keys
Initializing nextcloud 35.0.0.10 (this can take a while) ...
Setting permissions
Initializing finished
[custom-init] No custom files found, skipping...
[ls.io-init] done.
[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] 02-default-location: skipped
[migrations] done
usermod: no changes
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────
Linuxserver.io version: 35.0.0-ls452
Build-date: 2026-09-16T00:49:05+00:00
───────────────────────────────────────

using keys found in /config/keys
After completing the web-based installer, restart the Nextcloud container to apply default memory caching and transactional file locking configurations.
Alternatively, you can apply your own configurations by editing /config/www/nextcloud/config/config.php following the documentation:
https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/caching_configuration.html
https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/files_locking_transactional.html
[custom-init] No custom files found, skipping...
[ls.io-init] done.

And I see this message when accessing the web gui:

Internal Server Error

The server encountered an internal error and was unable to complete your request.
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
More details can be found in the server log.

[j0nnymoe]

And what does the nextcloud.log say within the /data mount?

[drizuid]

check logs for your database too, this looks a lot like some database corruption. you ALWAYS need to gracefully shutdown apps using a database and then the database before restarting your server.

[Runningman2552]

When I do after a reboot:
docker compose down
docker compose up -d
Nextcloud comes up normally then.

Looking for more logs atm.

Edit: Even "docker compose up -d" is enough and its working again..

[Runningman2552]

logs from the database after a reboot:

~$ docker logs nextcloud-db
2026-09-21 17:08:03+02:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.8.9+maria~ubu2404 started.
2026-09-21 17:08:03+02:00 [Warn] [Entrypoint]: /sys/fs/cgroup///memory.pressure not writable, functionality unavailable to MariaDB
2026-09-21 17:08:03+02:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2026-09-21 17:08:03+02:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.8.9+maria~ubu2404 started.
2026-09-21 17:08:04+02:00 [Note] [Entrypoint]: MariaDB upgrade not required
2026-09-21 17:08:04 0 [Note] Starting MariaDB 11.8.9-MariaDB-ubu2404 source revision bf9193a939f515e95dd8def1a5468088c91cede6 server_uid O0KF+MBtxG3MV9PYeHxjpfCtkPs= as process 1
2026-09-21 17:08:04 0 [Note] InnoDB: Compressed tables use zlib 1.3
2026-09-21 17:08:04 0 [Note] InnoDB: Number of transaction pools: 1
2026-09-21 17:08:04 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2026-09-21 17:08:04 0 [Warning] mariadbd: io_uring_queue_init() failed with EPERM: sysctl kernel.io_uring_disabled has the value 2, or 1 and the user of the process is not a member of sysctl kernel.io_uring_group. (see man 2 io_uring_setup).
create_uring failed: falling back to libaio
2026-09-21 17:08:04 0 [Note] InnoDB: Using Linux native AIO
2026-09-21 17:08:04 0 [Note] InnoDB: innodb_buffer_pool_size_max=8388608m, innodb_buffer_pool_size=128m
2026-09-21 17:08:04 0 [Note] InnoDB: Completed initialization of buffer pool
2026-09-21 17:08:04 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2026-09-21 17:08:04 0 [Note] InnoDB: End of log at LSN=4675337559
2026-09-21 17:08:04 0 [Note] InnoDB: Opened 3 undo tablespaces
2026-09-21 17:08:04 0 [Note] InnoDB: 128 rollback segments in 3 undo tablespaces are active.
2026-09-21 17:08:04 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2026-09-21 17:08:04 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2026-09-21 17:08:04 0 [Note] InnoDB: log sequence number 4675337559; transaction id 16871845
2026-09-21 17:08:04 0 [Note] Plugin 'FEEDBACK' is disabled.
2026-09-21 17:08:04 0 [Note] Plugin 'wsrep-provider' is disabled.
2026-09-21 17:08:04 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2026-09-21 17:08:04 0 [Note] InnoDB: Buffer pool(s) load completed at 260921 17:08:04
2026-09-21 17:08:05 0 [Note] Server socket created on IP: '0.0.0.0', port: '3306'.
2026-09-21 17:08:05 0 [Note] Server socket created on IP: '::', port: '3306'.
2026-09-21 17:08:05 0 [Note] mariadbd: Event Scheduler: Loaded 0 events
2026-09-21 17:08:05 0 [Note] mariadbd: ready for connections.
Version: '11.8.9-MariaDB-ubu2404'  socket: '/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
2026-09-21 17:23:01 0 [Note] mariadbd (initiated by: unknown): Normal shutdown
2026-09-21 17:23:01 0 [Note] InnoDB: FTS optimize thread exiting.
2026-09-21 17:23:01 0 [Note] InnoDB: Starting shutdown...
2026-09-21 17:23:01 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
2026-09-21 17:23:01 0 [Note] InnoDB: Restricted to 2028 pages due to innodb_buf_pool_dump_pct=25
2026-09-21 17:23:01 0 [Note] InnoDB: Buffer pool(s) dump completed at 260921 17:23:01
2026-09-21 17:23:01 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
2026-09-21 17:23:01 0 [Note] Shutdown completed; log sequence number 4675723682; transaction id 16873041
2026-09-21 17:23:01 0 [Note] mariadbd: Shutdown complete

These are the last view lines of the nextcloud.log in the /data folder:

Message":"dirty table reads: SELECT `id` FROM `*PREFIX*jobs` WHERE (`class` = :dcValue1) AND (`argument_hash` = :dcValue2) LIMIT 1"}}
{"reqId":"RZWLZNnwK9oIDBx34kyZ","level":1,"time":"2026-09-19T11:01:55+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","scriptName":"/app/www/public/occ","message":"\\OC\\Updater::startCheckCodeIntegrity: Starting code integrity check...","userAgent":"--","version":"34.0.3.2","occ_command":["/app/www/public/occ","upgrade"],"data":{"app":"updater"}}
{"reqId":"RZWLZNnwK9oIDBx34kyZ","level":1,"time":"2026-09-19T11:02:05+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","scriptName":"/app/www/public/occ","message":"\\OC\\Updater::finishedCheckCodeIntegrity: Finished code integrity check","userAgent":"--","version":"34.0.3.2","occ_command":["/app/www/public/occ","upgrade"],"data":{"app":"updater"}}
{"reqId":"RZWLZNnwK9oIDBx34kyZ","level":1,"time":"2026-09-19T11:02:05+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","scriptName":"/app/www/public/occ","message":"\\OC\\Updater::updateEnd: Update successful","userAgent":"--","version":"35.0.0.10","occ_command":["/app/www/public/occ","upgrade"],"data":{"app":"updater"}}
{"reqId":"RZWLZNnwK9oIDBx34kyZ","level":1,"time":"2026-09-19T11:02:05+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","scriptName":"/app/www/public/occ","message":"\\OC\\Updater::maintenanceDisabled: Turned off maintenance mode","userAgent":"--","version":"35.0.0.10","occ_command":["/app/www/public/occ","upgrade"],"data":{"app":"updater"}}
{"reqId":"RZWLZNnwK9oIDBx34kyZ","level":1,"time":"2026-09-19T11:02:05+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","scriptName":"/app/www/public/occ","message":"\\OC\\Updater::resetLogLevel: Reset log level to Warning(2)","userAgent":"--","version":"35.0.0.10","occ_command":["/app/www/public/occ","upgrade"],"data":{"app":"updater"}}
{"reqId":"B7w2Lzpktdn2YZGW57az","level":2,"time":"2026-09-19T11:05:02+00:00","remoteAddr":"","user":"--","app":"no app in context","method":"","url":"--","scriptName":"/app/www/public/cron.php","message":"Skipping updater backup clean-up - could not find updater backup folder /data/updater-ocqxzbitb12c/backups","userAgent":"--","version":"35.0.0.10","occ_command":["/app/www/public/cron.php"],"data":[]}

[j0nnymoe]

At a guess it's a timing issue as one of the containers or filesystems nextcloud relies on isn't ready. Also echo driz's comments.

[Runningman2552]

Yes, it seems looking at the db logs that the db is shuting down after startup. Is there a hint why?

[drizuid]

the logs probably have a hint, but presumably you corrupted the db with ungraceful db shutdown

this is what you said you do

When I do after a reboot:
docker compose down
docker compose up -d
Nextcloud comes up normally then.

Looking for more logs atm.

Edit: Even "docker compose up -d" is enough and its working again..

you need to , in this order

1. stop containers using the database
2. stop the database
3. reboot the server
4. bring up the database
5. bring up the containers using the database

using depends_on is not an appropriate way to handle it.
check the logs in your database and be ready to restore a backup

[Runningman2552]

Found the error: was a "restart: unless-stopped" missing in the docker-compose.yml for the db. Now it works, thanks for the help.