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):
- Nextcloud Hub 10 (31.0.10)
- Operating system and version (e.g., Ubuntu 24.04):
Ubuntu 24.04 LTS
- Web server and version (e.g, Apache 2.4.25):
Whatever AIO uses
- Reverse proxy and version _(e.g. nginx 1.27.2)
Traefik 3.3.3
- PHP version (e.g, 8.3):
Whatever AIO uses
- Is this the first time you’ve seen this error? (Yes / No):
Yes
- When did this problem seem to first start?
12.11.2025
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
AIO
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
Not Cloudflare, not sure what AIO uses
Summary of the issue you are facing:
After making my initial backup with borg I get the following log output on nightly backups:
2025-11-12T04:01:18.528754089Z Your public ssh key for borgbackup is: ssh-ed25519 <redacted> root@nextcloud-aio-borgbackup
2025-11-12T04:03:34.682600993Z Remote: ssh: connect to host 10.20.0.12 port 22: Operation timed out
2025-11-12T04:03:34.688958312Z Connection closed by remote host. Is borg working on the server?
2025-11-12T04:03:34.720094951Z Borg could not get info from the remote repo.
2025-11-12T04:03:34.720124856Z This might be a failure to connect to the remote server. See the above borg info output for details.
2025-11-12T04:03:34.720129273Z If you instead want to initialize a new backup repository, you may delete the 'borg.config' file that is stored in the mastercontainer volume manually, which will allow you to initialize a new borg repository in the chosen directory:
2025-11-12T04:03:34.720133970Z sudo docker exec nextcloud-aio-mastercontainer rm /mnt/docker-aio-config/data/borg.config
After looking into the borg.config I can see that it is empty. How can I recover from that?
Steps to replicate it (hint: details matter!):
-
Create an initial backup through Wireguard VPN
-
Enable nightly Backups
-
No Backup happening
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.