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):
30.0.2
- Operating system and version (e.g., Ubuntu 24.04):
- Linux ae888 5.10.0-39-amd64 #1 SMP Debian 5.10.251-1 (2026-03-09) x86_64 GNU/Linux
- Web server and version (e.g, Apache 2.4.25):
nginx
- Reverse proxy and version _(e.g. nginx 1.27.2)
replace me
- PHP version (e.g, 8.3):
8.3
- Is this the first time youâve seen this error? (Yes / No):
yes
- When did this problem seem to first start?
trying to install update
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
auto + manual
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
no
Summary of the issue you are facing:
Ich hatte bis heute eine funktionierende NC-Installation auf einem gemanagten Webserver (netcup). Nachdem das Auto-Update nicht ging. Habe ich das alte nextcloud-Verzeichnis httpdoc kopiert, den nextcloud-zip runtergeladen und entpackt. Danach in httpdoc umbenannt und die wichtigen Dateien config/config.php, data/ und ein paar einzelne apps aus dem alten in den euen ordner kopiert. Ich habe auch die Rechte vom httpdoc und von data auf lese/schreibbar fĂŒr den webserver gesetzt. Trotzdem erscheint die Meldung
âKann das âdataâ-Verzeichnis nicht erstellen.
Dies kann zumeist behoben werden, indem dem Webserver Schreibzugriff auf das Wurzel-Verzeichnis eingerĂ€umt wird.â
Das verstehe ich nicht. Ich hab schon alles möglische probiert. Vor allem hat es ja bisher geklappt. Und selbst bei umbennen der Ordner und RĂŒckbenennung des Bakcups in httpdoc bekomme ich jetzt die gleiche Meldung. Das kann ich ĂŒberhaupt nicht nachvollziehen und ergibt auch gar keinen Sinn. Alle Rechte sind gegeben, der Ordner existiert (inkl. .ncdata). Der Zustand ist aus meiner Sicht 1:1 wie vorher. Aber es geht nicht mehr. Woran kann das liegen?
Vielen Dank fĂŒr Hilfe (hatte schon hier im Forum gesucht, aber nichts brauchbares gefunden, was helfen könnte).
Norbert
Steps to replicate it (hint: details matter!):
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.
PASTE HERE
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 textformatting 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.