@joseph that did the trick! Solved and thank you!
gregwbrooks
Posts
-
Restoring from rsync'd Digital Ocean Spaces - seemingly no path works -
Restoring from rsync'd Digital Ocean Spaces - seemingly no path works@joseph there are no .tar.gz files or even .tar files -- not in /box and not in any of the app backup folders. Just ... files. SQL dumps, json files, etc.
I assumed this was because it was rsync rather than something else.
-
Restoring from rsync'd Digital Ocean Spaces - seemingly no path worksHi all -- hoping someone who's been down this road can help.
My current dedi server provider went out of business, so my existing Proxmox host is -- poof -- gone. Time to restore Cloudron from backups. My challenge:
-
On a new Cloudron install, when going to the UI initially and clicking the restore option, seemingly no combination of relative paths will be accepted by the form.
-
Leaving it blank doesn't work, obviously. But neither does /{bucket name} or /{bucket name}/{prefix} or {/{bucket name}/ {snapshots}
Clearly, the form wants a file name at the end of that path. But the examples in the doc all show restoring from a tarball rather than an incremental rsync. Within/snapshots, I have a lot of date-and-code folders and no indication of which file I should point to.
Any help, much appreciated!
EDIT/UPDATE: Saw some success pointing it at the box folder in snapshots; it complained about a lack of version info and wouldn't restore. Turns out the entire contents of fsmetadata.json is:
{ "emptyDirs": [], "execFiles": [], "symlinks": [] }
-
-
I managed to migrate ok following a post...@scooke Replying solely to say thank you (I had 1,200 Wallabag entries to bring over and was losing my mind) and to report that, in mid-2025, this still works beautifully.