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):
12.4.0
- Operating sysm and version (e.g., Ubuntu 24.04):
Ubuntu 24.04
- Web server and version (e.g, Apache 2.4.25):
Nginx Proxy Manager 2.13.5
- Reverse proxy and version _(e.g. nginx 1.27.2)
Nginx Proxy Manager 2.13.5
- PHP version (e.g, 8.3):
Nginx Proxy Manager 2.13.5
- Is this the first time you’ve seen this error? (Yes / No):
Yes
- When did this problem seem to first start?
Sunday 1/11
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
AIO
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
no
Summary of the issue you are facing:
I’m attempting to install Nextcloud AIO on a fresh Ubuntu VM, but after dealing with the docker socket being locked to the root user and group for several hours it is now at least attempting to run. I’ve never used docker before so I’m unsure of how to best troubleshoot this. The user running the container is a member of the docker group. docker ps -a returns:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
99ec89f45f90 ghcr.io/nextcloud-releases/all-in-one:latest "/start.sh" 5 hours ago Restarting (1) 58 seconds ago nextcloud-aio-mastercontainer
70a81ef0f890 hello-world "/hello" 6 hours ago Exited (0) 6 hours ago sad_hofstadter
It has been in the Restarting state the whole time. I am unable to go into the container by way of docker exec -it as it is not even starting.
This is on a fresh Ubuntu VM in Proxmox, with Docker installed per their documetation. The only other thing installed on this VM is the hello-world docker container I installed as a sanity check while troubleshooting a previous issue. Other than that I’ve mostly been following this guide with a few minor tweaks to troubleshoot errors. I’ve restarted the docker systemd service and the VM and the behavior has been consistent since Sunday.
Steps to replicate it (hint: details matter!):
-
Install Docker
-
Repair Docker installation so
/var/run/docker.sockgives thedockergrouprwpermissions instead of exclusiverootownership -
Attempt to run Nextcloud AIO via
docker compose up -d
Log entries
There are no logs as the docker container has yet to fully start