Issue with Backblaze B2 Connection Profile

[itswzyss]

I've been pulling my hair out trying to get Cyberduck to recognize my B2 credentials. After generating new keys, I noticed Cyberduck was still not authorizing. After much closer inspection, I noticed that the default profile uses the following hostname: s3.us-west-001.backblazeb2.com. In my case, this is not correct for my buckets. I also noted that you cannot change this default value.

Attempting to use this hostname results in this error:

After editing the connection profile located in %appdata%\Cyberduck\Profiles and allowing the Hostname Configurable field to be changed, I am then able to use the proper hostname which is s3.us-west-002.backblazeb2.com. Now my key works.

Shouldn't the hostname just be left as a configurable option to avoid issues like this?

[dkocher]

This is referring to the S3 API compatible connection profile for Backblaze B2 ¹. Curently the connection profile made available ² is restricted to the US West region s3.us-west-001.backblazeb2.com. We should add support for other account regions for which I have opened iterate-ch/profiles#80 ².

Footnotes

1. https://docs.cyberduck.io/protocols/b2/#using-s3-compatible-api ↩

2. Add Backblaze B2 profiles for additional account regions for S3 compatible API  profiles#80 ↩ ↩²