The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.
If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.
Getting help
In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.
Before clicking submit: Please check if your query is already addressed via the following resources:
(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).
Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can.
The Basics
Nextcloud Server version (e.g., 29.x.x):
35.0.0.10
Operating system and version (e.g., Ubuntu 24.04):
replace me
Web server and version (e.g, Apache 2.4.25):
13.7
Reverse proxy and version _(e.g. nginx 1.27.2)
2.15.1
PHP version (e.g, 8.3):
in docker image
Is this the first time you’ve seen this error? (Yes / No):
No
When did this problem seem to first start?
long ago
Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
linuxserver.io docker image
Are you using CloudfIare, mod_security, or similar? (Yes / No)
No
Summary of the issue you are facing:
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.
And I see this message when accessing the web gui after a reboot:
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.
And this 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.
I’m little confused.. as you can see logs containers must have started? what is the output of docker compose ps in the directory? what happens if you run docker compose up? does the app start?
Also, the internal server error looks like it’s coming from Nextcloud, which would imply that the Nextcloud container is running. Maybe the issue is with the MariaDB or Redis container. If one of them does not start, that would explain the internal server error.
