After a system update my backup to Backblaze B2 stopped working and fails with “Failed to connect: Error: ConnectFailure (Connection timed out)” after a few minutes, and same thing happens if I manually test the connection in the backup configuration. The logs don’t say anything other than that the connection timed out as far as I can see.
The backup is just a standard B2 backup with no additional options set. I can access Backblaze fine via web browser, and e.g. api.backblazeb2.com sends me to the B2 start page as expected. csharp -e 'new System.Net.WebClient ().DownloadString ("https://api.backblazeb2.com")' also works just fine.
This started happening to me as well, starting yesterday.
Had to rebuild/recreate database… and clearly connections are happening when files are being uploaded and downloaded, so it seems odd that the connection would sometimes fail.
When I watch the failure, I see the “waiting for upload to finish” status taking a long time, FWIW.
After the database rebuild, I also opened the database in sqlbrowser and ran “ANALYZE” on it, since I’d found some threads here talking about slow sql query times causing slow backup completions… and this last time around I was able to complete a backup.
I’m on Fedora, currently using 2.0.6.1_beta_2021-05-03.
Suddenly everything is fine again, so I guess the problem solved itself somehow? It seems it wasn’t an issue with Duplicati at least since I didn’t change anything, maybe some issue on Backblaze’s end?