Nextcloud cannot write into data directory /srv/nextcloud/data

Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

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).

I followed this tutorial HowTo: Ubuntu + Docker + Nextcloud + Talk + Collabora - #105 by szaimen by KarlF12. It is very good and informative. I cannot figure out which user cannot access /srv/nextcloud/data. I guess it is www-data. But the problem persists and the permissions are fine.

The tutorial tells me to look for a new version. I couldn’t find that unfortunately but at least I looked out for it.

Something is wrong: data, nextcloud and mariadb went into a user home directory. It shouldn’t be there and I should change that which I tried to

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 32
  • Operating system and version (e.g., Ubuntu 24.04):
    • ubuntu 24
  • Web server and version (e.g, Apache 2.4.25):
    • apache
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • not sure
  • PHP version (e.g, 8.3):
    • 8.3
  • Is this the first time you’ve seen this error? (Yes / No):
    • on initialisation of Nextcloud
  • When did this problem seem to first start?
    • on initialisation of Nextcloud
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • guide, docker
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • own domain name

Summary of the issue you are facing:

[…] I have changed owner and group to www-data and permissions look al right

Steps to replicate it (hint: details matter!):

  1. initialisation of Nextcloud - first run

Log entries

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

/var/log/apache2/nextcloud-error.log - the last entry

[Wed Jan 28 03:16:16.448322 2026] [authz_core:error] [pid 2884505:tid 129017244014272] [client 185.177.72.23:19088] AH01
630: client denied by server configuration: proxy:http://127.0.0.1:8080/server-status/


Web Browser

If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

PASTE

Web server / Reverse Proxy

The output of your Apache/nginx/system log in /var/log/____:

PASTE HERE

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

PASTE HERE

Apps

The output of occ app:list (if possible).

Tips for increasing the likelihood of a response

  • Use the preformatted text formatting option in the editor for all log entries and configuration output.
  • If screenshots are useful, feel free to include them.
    • If possible, also include key error output in text form so it can be searched for.
  • Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.

What you can try:

  1. chmod 777 /srv/nextcloud/data
  2. Create a folder and file in Nextcloud
  3. Check which user was used for this inside /srv/nextcloud/data
  4. Adjust the permissions for /srv/nextcloud/data so that the user which was identified in step 3 is the owner and the folder is not world writeable any longer.

Dear aweizel!

It seems to work now. What I did:

docker rm -vf $(docker ps -aq)

/srv/ had root as user, this was changed

chown root /srv

Then I ran

docker-compose up -d

again.

As far as I know it works now. And I don’t know really if the root ownership was the problem.

Thanks a lot for reaching out!

Yours sincerely

Claus Ladekjær Wilson