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):
- Operating system and version (e.g., Ubuntu 24.04):
Ubuntu 24.04
- Web server and version (e.g, Apache 2.4.25):
Apache 2.4.66
- Reverse proxy and version _(e.g. nginx 1.27.2)
- traefik v3.6.13
- 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?
at my most recent backup
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
nextcloud AIO using docker-compose.yml
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
Cloudflare, but this happens when I'm logged in locally
Summary of the issue you are facing:
Borgbackup hasn’t worked for me the last two times I tried to backup my nextcloud docker container. I inspected the config file and it exists and looks correct but I get this error:
It seems like the configuration.json setup was not done correctly. Something is wrong! (Most likely the provided configuration.json is invalid)
Steps to replicate it (hint: details matter!):
-
shut down all containers
-
run borg backup
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.
[16-Apr-2026 16:53:56] NOTICE: Terminating ...
[16-Apr-2026 16:53:56] NOTICE: exiting, bye-bye!
[Thu Apr 16 16:53:59.950454 2026] [mpm_event:notice] [pid 161:tid 161] AH00491: caught SIGTERM, shutting down
Initial startup of Nextcloud All-in-One complete!
You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
E.g. https://internal.ip.of.this.server:8080
⚠️ Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later!
If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:
https://your-domain-that-points-to-this-server.tld:8443
[Thu Apr 16 16:58:54.494637 2026] [mpm_event:notice] [pid 153:tid 153] AH00489: Apache/2.4.66 (Unix) OpenSSL/3.5.5 configured -- resuming normal operations
[Thu Apr 16 16:58:54.495147 2026] [core:notice] [pid 153:tid 153] AH00094: Command line: 'httpd -D FOREGROUND'
[16-Apr-2026 16:58:54] NOTICE: fpm is running, pid 160
[16-Apr-2026 16:58:54] NOTICE: ready to handle connections
Total reclaimed space: 0B
Total reclaimed space: 0B
Total reclaimed space: 0B
[19-Apr-2026 11:00:02] NOTICE: Terminating ...
[19-Apr-2026 11:00:02] NOTICE: exiting, bye-bye!
[Sun Apr 19 11:00:05.618864 2026] [mpm_event:notice] [pid 153:tid 153] AH00491: caught SIGTERM, shutting down
Initial startup of Nextcloud All-in-One complete!
You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
E.g. https://internal.ip.of.this.server:8080
⚠️ Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later!
If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:
https://your-domain-that-points-to-this-server.tld:8443
[Sun Apr 19 11:01:30.646494 2026] [mpm_event:notice] [pid 152:tid 152] AH00489: Apache/2.4.66 (Unix) OpenSSL/3.5.5 configured -- resuming normal operations
[Sun Apr 19 11:01:30.646541 2026] [core:notice] [pid 152:tid 152] AH00094: Command line: 'httpd -D FOREGROUND'
[19-Apr-2026 11:01:30] NOTICE: fpm is running, pid 157
[19-Apr-2026 11:01:30] NOTICE: ready to handle connections
Total reclaimed space: 0B
Deleting duplicate sessions
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!):
Here’s the /borg/config from my backup dir:
[repository]
version = 1
segments_per_dir = 1000
max_segment_size = 524288000
append_only = 0
storage_quota = 0
additional_free_space = 2G
id = {ID}
key = {KEY}
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.