So Tom AI suggested posting on Demox. After fighting a damaged debian install on my 230gb ssd drive that failed to boot or repair grub after a power outage. i installed a new install of debian on a 2tb drive, reinstalled tomssparkbox to 2 tb drive. traying to run a restore from previous backup but it says it fails decryption. now toms AI says may not be restorable? AI response was "I;m not confident I can get you further without knowing whether this is the same install that made the backup or a fresh one. Click "Share to demox" below and give Tom the details — this smells like it could tie back to that plaintext-backup bug and he'll want to look at the actual file" .
4 replies
Chris wrote:
Good news — your backup is almost certainly fine, and this is fixable. Backups are locked with a key that lives on the install that MADE them, in the settings file called .env in your SparkBox folder. Your fresh Debian created a brand-new key, so the restore can't unlock the old backup — but the original key is still sitting on your old 230GB drive. Plug that drive in, open /opt/sparkbox/.env on it, and copy the line starting with SBBACKUPKEY (if there isn't one, SBSESSIONSECRET). Put that exact line into the same file on your new install, run sudo sparkbox up, then try the restore again. Flagged with Tom too — he'll want to hear how it goes.
Wolf21 wrote:
When you do a backup from the dashboard, there is a button you can press to show your backup key.: From Dashboard - Settings - Backup Look under backups, and click the button that says "Reveal Backup Key". Copy this to a safe spot. Then when you need to restore, you'll have the key without having to look at an old .env file stored somewhere. I believe this key would change if you install a new instance of TomsSparkBox. However, this key does work for the backup that was created. NOTE: if you are trying out the 'new' dashboard, this button seems to be missing.... or at least I couldn't find it.
Chris wrote:
Good eye - you're right, that button doesn't exist yet in the new dashboard, it's not just hidden somewhere. I've flagged it so the new dashboard gets the same 'reveal your backup key' option the classic one has. Until it does, the workaround marke's using (checking the old install's .env file) still works fine no matter which version you're on. Thanks for pointing out where to find it!
mirok188 wrote:
restore worked pretty good, loaded 16 modules, had all the info for indexers, subtitles, and vpn. Got an issue with passwords changing in qbit, sonarr and radarr but thats a different post.