Yes it does 
1 Like
Thanks again for your assistance. It seems like Docker was ignoring my volume mount in the docker compose due to the existance of a docker volume named “nextcloud_aio_mastercontainer“ which had already been created at some point, assumedly by the containers trying to map to the correct places. I removed that volume, and it resumed working just fine, without evne needing to restore from backup. Apologies for the goose chase. The error was in my machine, not in the AIO system.
1 Like
Sorry to bother you with the topic already marked as solved, but since I have a similar issue with the restoration of my backup restoration being stuck after updating to the latest AIO version I was wondering what I did wrong on my end. I have already deleted the docker volume for the mastercontainer multiple times to make sure that that wasn’t the issue.
The configuration.jsons from my backups are all the same and look like this:
{
"password": "...",
"secrets": {
"INSTANCE_ID": "...",
"NEXTCLOUD_PASSWORD": "...",
"BORGBACKUP_PASSWORD": "..."
},
"apache_port": "..."
}
Seeing that OP’s example of a proper configuration contains a lot more information, does that mean that all the configurations I have cannot be used to restore the backup?
Hi, unfortunately the same answer applies for you:
You will need to somehow recover a working configurarion.json from your old install.
FYI, I am working on a hardening in backupscript: improve detection of invalid configuration.json files by szaimen · Pull Request #7611 · nextcloud/all-in-one · GitHub to find these kind of issues and report them back earlier.
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.
This is now released with v12.8.0 Beta. Testing and feedback is welcome! See GitHub - nextcloud/all-in-one: 📦 The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance.