Possible to retrieve password for encrypted storage

[kazzaw]

Hi,
I’m just wondering if there is a method to retrieve the password used for encrypted storage?

I am running Duplicacy in unraid (docker essentially). I’ve had an issue where I’ve needed to re-add the storage on one of my less critical buckets, but I couldn’t do it without the password. I wasn’t sure of what the password was, and what I had documented was incorrect apparently.

So now I need to confirm I know the password for the critical storage buckets, so if the need arises that I need to add the storage from a clean slate (say critical hardware failure etc) and restore the data from the backups.

Is there a method to test/confirm the password used for the password protection placed on backups? Or should I create new critical buckets and ensure that documentation is completed properly

[saspus]

Yes, open shell into the container, and launch duplicacy_web with -print-credentials command line argument and keep terminal open.

Now connect to that session, run backup, and watch the credentials printed in the console

Copy from local to offsite SFTP, difficulty with encryption list/restore on offsite

The error message cipher: message authentication failed means you entered the wrong storage password. To retrieve the correct storage password, run the web GUI with the -print-credentials option. The storage password will be printed out to stdout before a job is running.

Alternatively, you can use tools like process explorer to inspect environment of the duplicacy_cli process. Web UI passes storage credentials to CLI via environment variables.

[kazzaw]

Thanks - You’ll have to forgive me for further questions as I’m a bit of a rookie when it comes to playing with things outside of a GUI.

I’ve attempted to run it, but its obviously not launching because its already running and it can’t open the port.

I assume I need to kill the web process within the container and then run the command with the arguments which will restart it? Can you help with a command for this?

/usr/local/bin # /usr/local/bin/duplicacy_web -print-credentials
Duplicacy Web Edition 1.8.3 (5A554A)
Can't start the web server at 127.0.0.1:3875: listen tcp 127.0.0.1:3875: bind: address already in use

[saspus]

Which container are you using?

[kazzaw]

saspus/duplicacy-web though the community apps store

[saspus]

You can add the flag at the end of the /usr/local/bin/launch.sh and restart container

[kazzaw]

That’s it - Beauty. Thanks for the help