Hello Tim,
For starters, please read the B2 bucket naming rules BackBlaze publishes in https://www.backblaze.com/docs/cloud-storage-buckets
Moreover, there are a few things that they don't mention, but we have found out:
- Do not use uppercase or mixed-case names such as FOOBAR, Foobar, or FooBar.
- Enter your bucket name in the same all-lowercase name you created it.
- The bucket name MUST NOT start with numbers.
- It usually takes several minutes between creating a bucket and being able to use it. We recommend waiting for 1-2 hours.
Even though none of these should be a problem, we have observed that depending on which B2 server responds to the request the requests might sometimes fail if these additional rules are not followed. We have also observed that sometimes your B2 bucket is created on a storage pod with a misbehaving API which means that all upload requests from a specific location will fail, but using another server across the world to do the exact same request to the exact same bucket with the exact same authentication will work. There's a reason B2 is inexpensive; it's not as robust as S3, Swift, etc. It's somewhere between a consumer and an enterprise grade storage solution; that would make it "prosumer"-grade, I guess?
Try creating a new bucket named rochen20251208 (all lowercase, numbers after the letters) instead. Wait for about an hour, and you should be able to use it fine.
And yes, I know that you may have other buckets with numbers before the letters and mixed-case letters which work. As I said, it's a crapshoot. The big problem is that there's no single API server for B2 requests. The main API server simply tells us the domain name of the storage pod where your bucket is in, then we send API requests to that storage pod directly. You'd think that all storage pods have the same API functionality, and the documentation implies that. That has NOT been our observation at all. I stopped recommending B2 because of these observations. It will either work perfectly, or it will be absolute hell to make it work. Nothing in between. Amazon S3 is a bit more complicated to make it work (more configuration in a less user-friendly environment) but it's rock solid… and more than twice as expensive. So, yeah, you have a bit of a trade-off.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
