Backup to S3 setup

Support
1

I am trying to setup Duplicati to backup local files on my Win10 laptop to my Amazon S3 storage. When I have setup the new backup params and click Test Connection, the “Testing Connection” popup is displayed but nothing happens… no error or timeout.

I have been through the manual on setting this up and the forum guidance and I believe that I have done everything correctly. Is there anything obvious that I am doing/not doing on Duplicati setup or AWS ?

2

Hi @HQRQBQ welcome to the forum.

I vaguely recall someone saying that the Test button did not work in Edge, but I have not been able to reproduce. Can you try a different browser?

Or try Developer Tools and see if there is some error listed there.

If you think it is all set up correctly, you could also just try to run the backup?

3

Thanks Kenkendk. I have been playing around with this again. I’ve tried it on different browsers without success either.

I am getting a different error now though: “The request signature we calculated does not match the signature you provided. Check your key and signing method.”

any idea what this means?

4

In the latest canary build, I fixed one error that was causing the button to behave incorrectly. It would happen if the current user did not have permission to query its own account info. Duplicati only needed that permission to check that the account was not a root account, but since it was failing it was detected incorrectly.

That could mean a few things, but generally, it means that the data received by AWS is not accepted.

The AWS S3 scheme will calculate a signature of all the headers and the content locally, and then sign it with your account key. This ensures that it is not possible to change the contents, even if not using SSL/TLS encrypted transport.

The message says that the signature was incorrect, but it is not possible to know exactly why. It could be caused by data being altered (headers added or removed usually), the clock being incorrect, or even the password being incorrect.

5

Thanks. I have now got this working. I generated new S3 key and created a new policy. Not sure exactly why it wasn’t working before!