Is anyone having issues uploading to Backblaze currently?

[xvfp]

I'm currently using unRaid with BPWC v1.11. It worked consistently for over a year. Recently I found that it hasn't connected to Backblaze since 8/28/2025. Also, when I try to force a backup, it doesn't do anything. I've switched it to manual backup, and the button does an internal scan, however it never connects out to Backblaze.

I don't think this is related to my nextdns.io blocking, as i haven't changed that in a very long time and i was previously able to backup to backblaze.

I also have tried the 'latest' and 'v1.10' builds, but had no success either.

Thanks in advance!

[echoblag]

I noticed I am having the same issue, last full back up was 27/07/2025 and no files have been uploaded since the 14/09/2025.

I'm running tessypowder/backblaze-personal-wine:ubuntu22

I'm trying to test a fresh install at the moment, but now it think it's running Windows XP. I'll report back when I make some progress.

Edit: I switched back to my previous config bind mount, restarted, paused backups, and resumed. This worked for me and it's now transferring files again.

[shvartj]

I noticed I am having the same issue, last full back up was 27/07/2025 and no files have been uploaded since the 14/09/2025.

I'm running tessypowder/backblaze-personal-wine:ubuntu22

I'm trying to test a fresh install at the moment, but now it think it's running Windows XP. I'll report back when I make some progress.

Edit: I switched back to my previous config bind mount, restarted, paused backups, and resumed. This worked for me and it's now transferring files again.

Are you using ubuntu22 tag? what do you mean my going back to the previous config bind mount?

[echoblag]

• I am using the ubuntu22 tag.
• The container runs on Unraid
• The bind mount refers to the directory mapping for /config/ to /mnt/user/appdata/backblaze_personal_backup/ since Unraid doesn't use Docker volumes.

The switch to a new one meant that I wanted to test initializing the Backblaze container with a fresh config and inheriting the back. However I reverted back after encountering the Windows XP unsupported OS error as I didn't have time or appetite to troubleshoot that.

Triggering backup now managed to get past the building file lists status that it was stuck on. Bandwidth usage and Backblaze status confirms files were being uploaded.