Support intro
Sorry to hear you’re facing problems. 
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:
- Official documentation (searchable and regularly updated)
- How to topics and FAQs
- Forum search
(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):
Nextcloud AIO v10.13.0
- Operating system and version (e.g., Ubuntu 24.04):
Ubuntu 22.04.5 LTS
- Web server and version (e.g, Apache 2.4.25):
n/a
- Reverse proxy and version _(e.g. nginx 1.27.2)
n/a
- PHP version (e.g, 8.3):
n/a
- Is this the first time you’ve seen this error? (Yes / No):
yes
- When did this problem seem to first start?
2 days ago after I stopped Nextcloud AIO docker containers
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
AIO - Docker compose
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
Cloudflare - ZeroTrust tunnel
Summary of the issue you are facing:
[ 2 days ago I stopped all the AIO Docker containers because I wanted to move the ncdata folder from my NAS ‘A’ to NAS ‘B’. Before starting the folder move, I tried to start the containers again just to confirm everything was working fine before making any changes. I was surprised that Nextcloud wanted to set up my whole server again, as the initial setup screen appeared. I don’t know why this happened and I don’t know how to regain my setup.
If I go through the initial steps again, will it rebuild the data based on the old Docker volumes and the ncdata folder? Please help me understand what happened and how it can be solved without data loss.
The only thing I did 2 weeks ago was stop my physical node and upgrade the BIOS firmware, but after that, Proxmox, the Nextcloud VM, and then the Nextcloud AIO all started without any problem and worked as expected until this point.
Since then, regardless of the original issue, I have moved the ncdata folder to the new location, so there might be some permission-related entries in the logs due to that. However, the original problem already occurred before the move, I just didn’t save those earlier logs.]
Steps to replicate it (hint: details matter!):
- docker stop
- docker compose up -d
Log entries
Nextcloud
Trying to fix docker.sock permissions internally...
Adding internal www-data to group ping
Initial startup of Nextcloud All-in-One complete!
You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
E.g. https://internal.ip.of.this.server:8080
⚠️ Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later!
If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:
https://your-domain-that-points-to-this-server.tld:8443
[Sat May 10 05:27:20.773603 2025] [mpm_event:notice] [pid 149:tid 149] AH00489: Apache/2.4.62 (Unix) OpenSSL/3.3.3 configured -- resuming normal operations
[Sat May 10 05:27:20.774532 2025] [core:notice] [pid 149:tid 149] AH00094: Command line: 'httpd -D FOREGROUND'
[10-May-2025 05:27:20] NOTICE: fpm is running, pid 154
[10-May-2025 05:27:20] NOTICE: ready to handle connections
{"level":"info","ts":1746854840.806247,"msg":"using config from file","file":"/Caddyfile"}
{"level":"info","ts":1746854840.8081417,"msg":"adapted config to JSON","adapter":"caddyfile"}
Initial startup of Nextcloud All-in-One complete!
You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
E.g. https://internal.ip.of.this.server:8080
⚠️ Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later!
If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:
https://your-domain-that-points-to-this-server.tld:8443
[Sat May 10 06:29:57.234978 2025] [mpm_event:notice] [pid 137:tid 137] AH00489: Apache/2.4.62 (Unix) OpenSSL/3.3.3 configured -- resuming normal operations
[Sat May 10 06:29:57.235539 2025] [core:notice] [pid 137:tid 137] AH00094: Command line: 'httpd -D FOREGROUND'
[10-May-2025 06:29:57] NOTICE: fpm is running, pid 142
[10-May-2025 06:29:57] NOTICE: ready to handle connections
{"level":"info","ts":1746858597.2603776,"msg":"using config from file","file":"/Caddyfile"}
{"level":"info","ts":1746858597.2630486,"msg":"adapted config to JSON","adapter":"caddyfile"}
Deleting duplicate sessions
Configuration
Nextcloud
version: "3.8"
services:
nextcloud-aio-mastercontainer:
image: nextcloud/all-in-one:latest
init: true
restart: always
container_name: nextcloud-aio-mastercontainer
volumes:
- nextcloud_aio_mastercontainer:/mnt/docker-aio-config
- /var/run/docker.sock:/var/run/docker.sock:ro
network_mode: bridge
ports:
- 80:80
- 8080:8080
- 8443:8443
environment:
APACHE_PORT: 8081
APACHE_IP_BINDING: 0.0.0.0
APACHE_BODY_LIMIT: 0
NEXTCLOUD_DATADIR: /mnt/nextcloud-truenas/ncdata
NEXTCLOUD_ADDITIONAL_APKS: imagemagick perl
NEXTCLOUD_UPLOAD_LIMIT: 32G
SKIP_DOMAIN_VALIDATION: true
volumes:
nextcloud_aio_mastercontainer:
name: nextcloud_aio_mastercontainer