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):
32.0.4 -> 32.0.5
- Operating system and version (e.g., Ubuntu 24.04):
Docker version 29.2.1, build a5c7197, Ubuntu 24.04.3 LTS
- Web server and version (e.g, Apache 2.4.25):
NA
- Reverse proxy and version _(e.g. nginx 1.27.2)
NA
- PHP version (e.g, 8.3):
NA
- Is this the first time you’ve seen this error? (Yes / No):
Yes
- When did this problem seem to first start?
02/15/2026
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
AIO 12.5.1 -> AIO 12.6.1
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
It is served behind Cloudflared tunnel for myself, but the AIO console is not accessible except via wireguard IPv4.
Summary of the issue you are facing:
A week or so ago (02/7/2026) I set up nextcloud via AIO to test it out. After going through the installation instructions, I had AIO v12.5.1 up and running with NextCloud 32.0.4. Everything worked fine, and I followed the recommendations for having it behind a cloudflared tunnel. I set up a STUN/TURN server as specified, talk worked, mobile apps and webpages all worked.
When I checked the AIO console, it said there was a mastercontainer update, so I made a backup, then updated the container. This updated AIO to 12.6.1, and the NextCloud version associated with the new AIO is 32.0.5.
I ran into an error after updating that forced me to create a proper docker volume rather than just directly mounting the DATADIR and BACKUPDIR from local directories, but I got that fixed and added to my docker compose file. For reference, this is the docker compose file:
services:
nextcloud-aio-mastercontainer:
image: ghcr.io/nextcloud-releases/all-in-one:latest
container_name: nextcloud-aio-mastercontainer
restart: always
init: true
ports:
- "80:80"
- "8080:8080"
- "8443:8443"
volumes:
- nextcloud_aio_mastercontainer:/mnt/docker-aio-config
- /var/run/docker.sock:/var/run/docker.sock:ro
environment:
- TZ=Etc/UTC
- NEXTCLOUD_DATADIR=/mnt/nextcloud/nextcloud_data
- SKIP_DOMAIN_VALIDATION=true
- APACHE_PORT=11000
- APACHE_IP_BINDING=0.0.0.0
volumes:
nextcloud_aio_mastercontainer:
name: nextcloud_aio_mastercontainer
driver: local
driver_opts:
type: none
o: bind
device: /mnt/nextcloud/nextcloud_aio_mastercontainer
nextcloud_aio_backupdir:
name: nextcloud_aio_backupdir
driver: local
driver_opts:
type: none
o: bind
device: /mnt/nextcloud/backups
Not sure if it matters, but this mount (`/mnt/nextcloud`) is an NFS, not a local storage device.
However, after starting up the mastercontainer again, it requires a different AIO passphrase, which I got from the container via this command:
docker exec nextcloud-aio-mastercontainer grep password /mnt/docker-aio-config/data/configuration.json
Then when I logged in, it asked me to either create a new instance or to restore from backup. I tried to restore, it found the backups fine, and I had saved the password so it all worked. I verified the backup and then restored. But after it was done restoring, it just showed me the same “Restore Backup“ screen I previously filled out. I’ve tried restarting the container, the system, and just continuing to restore from backup. It doesn’t ever get past this. Maybe I am doing something wrong. The backup was made with AIO v12.5.1, and the update changed it to 12.6.1. I assumed I’d be able to restore just fine, but it seems like either I messed up the process or misconfigured something. I do have a snapshot of the VM from just before updating as well, so I can revert back to the old version, but I can’t actually start Nextcloud AIO v12.5.1, as the only button available for the services is the update button.
Steps to replicate it (hint: details matter!):
-
Create NextCloud instance with AIO v12.5.1
-
Do some configuration (e.g. Oauth, users, Talk, HPB, etc.)
-
Make a backup via AIO v12.5.1
-
Update from v12.5.1 to v12.6.1
-
Try to restore backup with saved backup key and local directory
Log entries
I don’t really have any logs. I can paste the logs somewhere (e.g. pastebin) from the backup process, but it is quite large and also contains the usernames of the users I made, which includes the personal details of me and some of my immediate family, so I’d prefer not to do that. If there are some other logs (e.g. container logs via docker … logs) I can get those, I’m just not sure which ones are relevant. I didn’t see any logs printed out to the console during or after the backup process.
Configuration
For clarity, I will describe my complete setup here.
Nextcloud is hosted via the AIO solution, with Docker. Docker is installed on an Ubuntu 24.04.3 LTS VM. This VM is hosted on Proxmox.
This Proxmox instance was recently reinstalled, but the snapshot of this VM was restored via Proxmox Backup Server, and multiple other VMs were restored like this (including a few which run Portainer and quite a few assorted containers), and they had no issues. The reason I saw the update button was because I was restarting all the services in my little homelab and instead of being able to start Nextcloud back up, I had to update first.
Apologies if I am in the wrong place or have the wrong tags. I looked around as best I could to see where this should go. I didn’t see anyone else having this issue.
