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).
Iâve made all the newbie mistakes known to man when it comes to permissions. Iâve tried to retroactively fix the issue but to no avail.
The Basics
- Operating system and version (e.g., Ubuntu 24.04):
- Description: Ubuntu 24.04.4 LTS
- Is this the first time youâve seen this error? (Yes / No):
Yes
- When did this problem seem to first start?
- I was getting a folder permissions error in my server. I basically have a user folder that I seemed to have lost permissions to overnight. Everything was working fine. In an attempt to fix that I believe I changed permissions for my folders and consequently broke everything else.
- nstallation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
Nextcloud aio using docker containers
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
Using Cloudflare to tunnel the nc.website.net
Summary of the issue you are facing:
Like I said, Iâve changed permission and havenât been able to run the program since. Itâs a rookie mistake and I even considered completely re-installing Ubuntu to try to fix it, but I already have data in the server and a mounted drive that took me quite some time to get set up. I will follow any and all instructions to provide logs, but please keep in mind I am fairly green when it comes to linux. I appreciate any and all help in advance. Iâll post the errors Iâm getting and any supplemental information I can get.
The INITIAL problem I was dealing with was a folder permission issue encountered on the server. I googled the issue and I believe my first mistake was running this:
# Set ownership to www-data (UID 33) and group 0
sudo chown -R 33:0 /path/to/your/folder
# Set permissions to 750 (owner rwx, group r-x, others none)
sudo chmod -R 750 /path/to/your/folder
I didnât encounter any initial issue here. However, the next time I tried to run:
docker compose up
OR:
sudo docker run --sig-proxy=false --name nextcloud-aio-mastercontainer --restart always --publish 80:80 --publish 8080:8080 --publish 8443:8443 --volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config --volume /var/run/docker.sock:/var/run/docker.sock:ro nextcloud/all-in-one:latest
It returned:
nextcloud-aio-mastercontainer | sudo: /etc/sudo.conf is owned by uid 1000, should be 0
nextcloud-aio-mastercontainer | sudo: /etc/sudo.conf is owned by uid 1000, should be 0
nextcloud-aio-mastercontainer | sudo: /etc/sudoers is owned by uid 1000, should be 0
nextcloud-aio-mastercontainer | sudo: error initializing audit plugin sudoers_audit
nextcloud-aio-mastercontainer | Trying to fix docker.sock permissions internallyâŚ
nextcloud-aio-mastercontainer | Adding internal www-data to group www-data
nextcloud-aio-mastercontainer | sudo: /etc/sudo.conf is owned by uid 1000, should be 0
nextcloud-aio-mastercontainer | sudo: /etc/sudo.conf is owned by uid 1000, should be 0
nextcloud-aio-mastercontainer | sudo: /etc/sudoers is owned by uid 1000, should be 0
nextcloud-aio-mastercontainer | sudo: error initializing audit plugin sudoers_audit
nextcloud-aio-mastercontainer | Docker socket is not readable by the www-data user. Cannot continue.
This is where youâre going to get mad at me. I have since run a myriad of commands and permissions.
Now, the folders I have messed with:
/var/run/docker.sock
srwxr-xâ 1 root docker 0 May 3 15:55 /var/run/docker.sock
Relevant groups and their permissions:
getent group ashrite
ashrite:x:1000:www-data
##
getent group www-data
www-data:x:998:ashrite
##
getent group docker
docker:x:33:ashrite,www-data
I have probably borked this beyond repair but am posting in hopes someone can guide me to the light. I appreciate your taking time to read this.
Configuration
Nextcloud compose.yaml : NOTE: I have not made any changes to my compose.yaml. Issues are just stemming from permission changes.
name: nextcloud-aio # Add the container to the same compose project like all the sibling containers are added to automatically.
services:
nextcloud-aio-mastercontainer:
image: ghcr.io/nextcloud-releases/all-in-one:latest # This is the container image used. You can switch to ghcr.io/nextcloud-releases/all-in-one:beta if you want to help testing ne>
init: true # This setting makes sure that signals from main process inside the container are correctly forwarded to children. See https://docs.docker.com/reference/compose-file/se>
restart: always # This makes sure that the container starts always together with the host OS. See https://docs.docker.com/reference/compose-file/services/#restart
container_name: nextcloud-aio-mastercontainer # This line is not allowed to be changed as otherwise AIO will not work correctly
volumes:
- nextcloud_aio_mastercontainer:/mnt/docker-aio-config # This line is not allowed to be changed as otherwise the built-in backup solution will not work
- /var/run/docker.sock:/var/run/docker.sock:ro # May be changed on macOS, Windows or docker rootless. See the applicable documentation. If adjusting, don't forget to also set 'W>
- /media/ExternalStorageWD:/nextcloud_aio_mastercontainer
# devices: ["/dev/dri"] # Uncomment to enable hardware acceleration. â ď¸â ď¸â ď¸ Warning: this only works if the '/dev/dri' device is present on the host! If it should not exist on your host,>
network_mode: bridge # This adds the container to the same network as docker run would do. Comment this line and uncomment the line below and the networks section at the end of th>
# networks: ["nextcloud-aio"]
ports:
- 80:80 # Can be removed when running behind a web server or reverse proxy (like Apache, Nginx, Caddy, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-in-one/b>
- 8080:8080 # This is the AIO interface, served via https and self-signed certificate. See https://github.com/nextcloud/all-in-one#explanation-of-used-ports
# - 11000:11000
# - "8443:8443" # Can be removed when running behind a web server or reverse proxy (like Apache, Nginx, Caddy, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-in-o>
# security_opt: ["label:disable"] # Is needed when using SELinux. See https://github.com/nextcloud/all-in-one#are-there-known-problems-when-selinux-is-enabled
environment: # Is needed when using any of the options below
# AIO_DISABLE_BACKUP_SECTION: false # Setting this to true allows to hide the backup section in the AIO interface. See https://github.com/nextcloud/all-in-one#how-to-disable-the>
APACHE_PORT: 11000 # Is needed when running behind a web server or reverse proxy (like Apache, Nginx, Caddy, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-i>
APACHE_IP_BINDING: 0.0.0.0 # Should be set when running behind a web server or reverse proxy (like Apache, Nginx, Caddy, Cloudflare Tunnel and else) that is running on the same>
# APACHE_ADDITIONAL_NETWORK: frontend_net # (Optional) Connect the apache container to an additional docker network. Needed when behind a web server or reverse proxy (like Apach>
# BORG_RETENTION_POLICY: --keep-within=7d --keep-weekly=4 --keep-monthly=6 # Allows to adjust borgs retention policy. See https://github.com/nextcloud/all-in-one#how-to-adjust-b>
# AIO_LOG_LEVEL: warn # Allows to globally adjust the log level of the included AIO components. Supported values: debug, info, warn, error. See https://github.com/nextcloud/all->
# COLLABORA_SECCOMP_DISABLED: false # Setting this to true allows to disable Collabora's Seccomp feature. See https://github.com/nextcloud/all-in-one#how-to-disable-collaboras-s>
# DOCKER_API_VERSION: 1.44 # You can adjust the internally used docker api version with this variable. â ď¸â ď¸â ď¸ Warning: please note that only the default api version (unset this var>
# FULLTEXTSEARCH_JAVA_OPTIONS: "-Xms1024M -Xmx1024M" # Allows to adjust the fulltextsearch java options. See https://github.com/nextcloud/all-in-one#how-to-adjust-the-fulltextse>
# NEXTCLOUD_DATADIR: /mnt/ncdata # Allows to set the host directory for Nextcloud's datadir. â ď¸â ď¸â ď¸ Warning: do not set or adjust this value after the initial Nextcloud installatio>
NEXTCLOUD_MOUNT: /media/ExternalStorageWD/
SKIP_DOMAIN_VALIDATION: true
