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. ![]()
Hello,
I am trying to restore a borg backup on an AIO instance, but the restore fails with “Last restore failed! (link to Logs)”.
When opening the Logs link (in Chromium), the website starts to load and shows a large number of lines, but ultimately shows only an “error 5”-message, presumably from Chromium.
I would like to access the log in another way and can’t find any information where the borg backup log is located. I also searched the system and the docker container “nextcloud-aio-mastercontainer”. All other containers are stopped, so I guess the log can’t be in there?
I read that the logs should be in a container named “nextcloud_aio_backup”, but I can’t find that, only “nextcloud_aio_backup-cache“.
Also, FWIW, the borg backup location is on an external drive under /mnt/4tb-HDD-exfat/nextcloud-backup/ . I searched there too, but can’t find a log either.
Anyone have an idea how to access the last borg restore log, so that I can investigate what is going on?
Thanks for any help!
The Basics
- Nextcloud Server version (e.g., 29.x.x):
31.0.8
- Operating system and version (e.g., Ubuntu 24.04):
linux debian 12
- Web server and version (e.g, Apache 2.4.25):
Caddy
- Reverse proxy and version _(e.g. nginx 1.27.2)
Caddy
- PHP version (e.g, 8.3):
as in AIO
- Is this the first time you’ve seen this error? (Yes / No):
Yes
- When did this problem seem to first start?
A few days ago
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
replace me
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
replace me
Summary of the issue you are facing:
[…]
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.