It seems I have to leave it alone for a day or two to allow for what I suspect is some type of token expiration before it will work again.Īnyone have any similar problems backing up to Backblaze B2 Cloud Storage from a Windows 10 computer? Any ideas as to how to go about troubleshooting this? Any help would be appreciated. If shortly after the backup is successful I try to manually run a different backup task (also to backblaze, seperate bucket) I get the bad auth token error.

If I leave it alone for a few days and then initiate a manual run of a particular backup, it often works. I don’t have any detailed knowledge of how the handshake/authentication process works between Duplicati and Backblaze B2 Cloud Storage, but it seems (based off the error) that an incorrect auth token is being offered and subsequently rejected.

A Backblaze knowledge base article found here: b2_get_upload_url talks about a 24 hour period that the auth token lives before expiring. My understanding through reading the documentation, is that Duplicati tries to use any existing, open connection to Backblaze B2 each time it runs. Each of my backups are scheduled to run 4 hours apart from one another every evening. All data is being backed up to Backblaze B2 Cloud Storage, but to different buckets. I use Duplicati to perform 3 separate backup tasks running from a single desktop computer to backup different data sources. I’m still trying to narrow down the circumstances as to when/why this is happening. For the most part, it works great, but sometimes I get failed backups with the error “401 Invalid authorization token” being given. I’m running Duplicati 2.0.3.3_beta_ on Windows 10 to manage my backups to Backblaze B2 Cloud Storage.

B2 cloud