Error restoring from backup (tampered file)

[murgero]

@3246 I would try another backup and see if it fails there too

Maybe wrong password or the password was mistyped?

[jdaviescoates]

@3246 it's things like this that make me avoid using encryption for most things. I tend to think the the risk of someone accessing my data is lower than something going wrong with encryption (or me forgetting the pw or whatever)

I don't really have much/ any sensitive data anyway

[3246]

OK, maybe you guys are right. I appear to have two very similar entries in my password safe darn it...

Now I got this error:

Already activated. Restore with a fresh Cloudron installation.

Does that mean I have to start from scratch?!

[3246]

What the deuce! I hit refresh on that restore page and now the DNS update dialogue popped up followed by ... disappointment and dread as the SSL certs haven't been generated yet, so I am greeted by an HSTS error message instead of my Cloudron dashboard.

I assume it worked out OK in the end after I entered the, presumably, correct password but threw an error in my face instead?!

[3246]

@jdaviescoates said in Error restoring from backup (tampered file):

@3246 it's things like this that make me avoid using encryption for most things. I tend to think the the risk of someone accessing my data is lower than something going wrong with encryption (or me forgetting the pw or whatever)

I don't really have much/ any sensitive data anyway

#EncryptAllTheThings

Even if you don't have anything to hide or use it for business, in which case you /really/ should use it, you should use it anyway because it's good for you and a great way to stay in shape

[jdaviescoates]

@3246 said in Error restoring from backup (tampered file):

a great way to stay in shape

I recommended the Scientific 7 minute workout, see eg https://archive.nytimes.com/well.blogs.nytimes.com/2013/05/09/the-scientific-7-minute-workout/

I use this wonderful app:
https://f-droid.org/en/packages/com.enjoyingfoss.feeel/
https://play.google.com/store/apps/details?id=com.enjoyingfoss.feeel&gl=us

Although recently it reduced the last two side planks to 15 seconds (instead of 30) and the gap between them be 5 seconds (instead of 10) so I had to duplicate and edit it to get back to the original I know and love.

A while ago I did it every day without fail for 100 days straight. Then I did Joe Wicks full body 20 min workout

for 56 days straight (I copied the routine into the great Just Another Workout Timer app https://f-droid.org/packages/com.blockbasti.justanotherworkouttimer/ so as to not have to watch the video to do it)

Then I got tennis and golf elbow from too many press-ups

So now, after slowly building up my running ability with the Couch to 5k program (I used this app https://play.google.com/store/apps/details?id=com.phe.couchto5K&gl=US ) I alternate workout days with run days 4ish days a week.

[3246]

Quick update: the SSL errors persist, the apps are stuck 'restoring' and that's despite rebooting and leaving it for a night.

Looks like I need to wipe it and start again.

[nebulon]

@3246 to get over the HSTS issue, in most browsers you have to "forget about this page" in the browser history.

[3246]

Got it working after starting from scratch. Looks like one of the backups files got corrupted

Is there a way to run a consistency check or is a test restore the best way?

[jdaviescoates]

@3246 said in Error restoring from backup (tampered file):

Is there a way to run a consistency check or is a test restore the best way?

I think consistency check is coming in next version, for now I think test restore best way

[girish]

@3246 @jdaviescoates Yes, the consistency check will come in next version. Also, a bit of fail early for password failures will help. Have to investigate how this can be done.

[3246]

@girish awesome! I think what would be helpful is to test the parameters before pressing 'restore', just to validate that both the connection and decryption keys are OK.

I found the error messages we have right where more confusing than helpful. I don't really know what I did wrong because to resolve it, I just took a fresh backup and restored it using the same details.

All good now though.