Backup to Azure fails with code 403

Support
#1

Hi Gilbert and fellow Duplicacy fans

I am backing up 200gb from linux duplicacy version 2.10 (the downloaded binary) to an azure blob using the following command:

sudo duplicacy backup -threads 10

I randomly get the following message after an at least an hour of backing up.

storage: service returned error: StatusCode=403, ErrorCode=AuthenticationFailed, ErrorMessage= Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.

I hope you can help. This software looks amazing, I am very happy with your work.

Sincerely
Dennis

#2

This looks exactly like https://github.com/Azure/azure-sdk-for-go/issues/1005

So maybe the solution is to rewrite the backend using https://github.com/azure/azure-storage-blob-go.

#3

Backups have been fine for a while, and then I got an odd error during a roughly 30 minute backup (at the tail end):

01:17:10 Uploaded chunk 3591 size 12502342, 11.96MB/s 00:00:02 99.8%
01:17:11 Uploaded chunk 3592 size 11464397, 11.96MB/s 00:00:01 99.9%
01:37:46 Failed to upload the chunk e6966db2740ddce6f2cd183fe8a01c71701e776ff2eae39e6183a4a49d296e68: storage: service returned error: StatusCode=403, ErrorCode=AuthenticationFailed, ErrorMessage=Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.
01:37:46 RequestId:54085822-401e-0007-2971-08946e000000
01:37:46 Time:2018-06-20T08:37:46.2651577Z, RequestInitiated=Wed, 20 Jun 2018 08:37:45 GMT, RequestId=54085822-401e-0007-2971-08946e000000, API Version=, QueryParameterName=, QueryParameterValue=
01:37:46 Error executing command: exit status 100

This looks the same to me as what was originally reported. Maybe, before you change the entire backend, you should consider retrying this at least a few times?

Let me know your thoughts, thanks.

/Jeff

#4

@Dewoller - did you find a solution to above issue?

I am running into the same issue using Web-UI 1.4.1 (using CLI 2.7.1).

Investigating a bit - it looks like my issue was happening because my Mac (or the HDD) went to sleep as I didn’t have the power cord connected for some time and when i woke up the machine, the process retried and hit the failure.

Once I changed the power settings to not sleep - it has been going well so far.