Chris wrote:
That address is fine — s3.us-east-005.backblazeb2.com is a real Backblaze endpoint, so the address itself isn't the problem. Two things catch most B2 setups: the endpoint's region has to match the region your bucket lives in (us-east-005 only works for a bucket actually in us-east-005 — check your Backblaze console and use that region's endpoint, like s3.us-west-004.backblazeb2.com), and the key has to be an S3-compatible one (create an application key with S3 access, or turn on S3 for your master key). Also keep the bucket name in its own field — the endpoint box holds just the hostname. If it still won't connect, hit Test connection and paste the exact error it shows.