Restore from Backup fails

So, the reason I was restoring in the first place was due to a broken install. I updated it and now it’s working, so this can be disregarded.

Old Post

Ok, so I’m not sure what I’ve done wrong here and I’m confused. I followed the directions on the moving to a new box section of the guide, but once I got it all set up and ready to restore, I ran the commands and got an error from Duplicity that has since rendered the new install useless (nginx fails to start). Here’s what I’ve done

root@box:~# export PASSPHRASE=$(cat /root/restore/secret_key.txt)
root@box:~# sudo -E duplicity restore --force file:///root/restore/encrypted /home/user-data/
Synchronizing remote metadata to local cache...
Copying duplicity-full-signatures.20190315T070002Z.sigtar.gpg to local cache.
Copying duplicity-full.20190315T070002Z.manifest.gpg to local cache.
Copying duplicity-inc.20190315T070002Z.to.20190316T070002Z.manifest.gpg to local cache.
Copying duplicity-inc.20190316T070002Z.to.20190317T070002Z.manifest.gpg to local cache.
Copying duplicity-inc.20190317T070002Z.to.20190318T070002Z.manifest.gpg to local cache.
Copying duplicity-inc.20190318T070002Z.to.20190319T070002Z.manifest.gpg to local cache.
Copying duplicity-inc.20190319T070002Z.to.20190320T070002Z.manifest.gpg to local cache.
Copying duplicity-inc.20190320T070002Z.to.20190321T070002Z.manifest.gpg to local cache.
Copying duplicity-inc.20190321T070002Z.to.20190322T070002Z.manifest.gpg to local cache.
Copying duplicity-inc.20190322T070002Z.to.20190323T040506Z.manifest.gpg to local cache.
Copying duplicity-inc.20190323T040506Z.to.20190323T070002Z.manifest.gpg to local cache.
Copying duplicity-inc.20190323T070002Z.to.20190323T212139Z.manifest.gpg to local cache.
Copying duplicity-new-signatures.20190315T070002Z.to.20190316T070002Z.sigtar.gpg to local cache.
Copying duplicity-new-signatures.20190316T070002Z.to.20190317T070002Z.sigtar.gpg to local cache.
Copying duplicity-new-signatures.20190317T070002Z.to.20190318T070002Z.sigtar.gpg to local cache.
Copying duplicity-new-signatures.20190318T070002Z.to.20190319T070002Z.sigtar.gpg to local cache.
Copying duplicity-new-signatures.20190319T070002Z.to.20190320T070002Z.sigtar.gpg to local cache.
Copying duplicity-new-signatures.20190320T070002Z.to.20190321T070002Z.sigtar.gpg to local cache.
Copying duplicity-new-signatures.20190321T070002Z.to.20190322T070002Z.sigtar.gpg to local cache.
Copying duplicity-new-signatures.20190322T070002Z.to.20190323T040506Z.sigtar.gpg to local cache.
Copying duplicity-new-signatures.20190323T040506Z.to.20190323T070002Z.sigtar.gpg to local cache.
Copying duplicity-new-signatures.20190323T070002Z.to.20190323T212139Z.sigtar.gpg to local cache.
Last full backup date: Fri Mar 15 01:00:02 2019
Error '[Errno 17] File exists' processing ssl/ssl_certificate.pem

I then ran the reconfigure command as specified, and got this:

FAILED: service nginx restart
-----------------------------------------
Job for nginx.service failed because the control process exited with error code.
See "systemctl status nginx.service" and "journalctl -xe" for details.
-----------------------------------------

The error log from nginx:

2019/03/23 15:38:51 [warn] 22344#22344: "ssl_stapling" ignored, issuer certificate not found for certificate "/home/user-data/ssl/ssl_certificate.pem"
2019/03/23 15:38:51 [warn] 22344#22344: "ssl_stapling" ignored, issuer certificate not found for certificate "/home/user-data/ssl/ssl_certificate.pem"
2019/03/23 15:38:51 [notice] 22344#22344: signal process started
2019/03/23 15:40:23 [warn] 23147#23147: "ssl_stapling" ignored, issuer certificate not found for certificate "/home/user-data/ssl/ssl_certificate.pem"
2019/03/23 15:40:23 [warn] 23147#23147: "ssl_stapling" ignored, issuer certificate not found for certificate "/home/user-data/ssl/ssl_certificate.pem"
2019/03/23 15:40:23 [warn] 23147#23147: "ssl_stapling" ignored, issuer certificate not found for certificate "/home/user-data/ssl/ssl_certificate.pem"
2019/03/23 15:40:23 [notice] 23147#23147: signal process started
2019/03/23 15:46:03 [emerg] 26359#26359: SSL_CTX_use_PrivateKey_file("/home/user-data/ssl/ssl_private_key.pem") failed (SSL: error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch)

What this looks like to me is a SSL error, but how do I go about fixing that? Or, is this something completely different?

It tells you right there. it can’t overwrite that file, so you should move it.(Not delete it)

Full file path for you: /home/user-data/ssl/ssl_private_key.pem

I getting the same error, tried to move it to a new file location like @murgero suggested, but then

Error ‘[Errno 17] File exists’ processing mail/sieve/prioritykids.org/info.sieve

Error ‘[Errno 17] File exists’ processing ssl/ssl_certificate.pem

even though I moved ssl/ssl_certificate.pem to temp folder

nginx: [emerg] SSL_CTX_use_PrivateKey_file("/home/user-data/ssl/ssl_private_key.pem") failed (SSL: error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatc

1 Like

Can you reinstall and restore?

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.