-
-
Notifications
You must be signed in to change notification settings - Fork 292
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to connect to Cloudflare R2 owing to lack of ability to change region #16377
Comments
I cannot reproduce. What region is the bucket in you are testing with? |
@dkocher I am also getting this exact issue when creating a new connection profile using the "Cloudflare R2 Storage (S3)" profile with mac version 9.0.4, 9.0.2, 9.0.1 Cloudflare R2 uses the following regions
But Cyberduck is defaulting to the AWS S3 region specified here instead: If I change the default bucket location from "US West Oregon" to "US West (Northern California)" , the error appears with "us-west-1" not being a valid region. I cannot set the default bucket location to WNAM which is where my bucket is. Also worth nothing, I had previous Cloudflare connection setup some months ago using the "Cloudflare R2 Storage (S3)" profile, that old connection setting can connect just fine to cloudflare R2 and I can even duplicate that connection and use that as a template for any new buckets I want to connect to and it works. |
I can confirm this issue. When you have previously successfully connected to a single bucket with the default region in Preferences → S3 set to The issue here occurs because the Cloudflare R2 profile is missing a
Footnotes |
Describe the bug
I'm trying to connect to an R2 bucket with Cyberduck using the Cloudflare R2 profile. However, I'm greeted with the following error:
When I open the Cyberduck's settings (Settings > S3 > Default Bucket Location), I can change the region, and I can confirm the change is reflected, however the options
enam, weur, eeur, apac, auto
are not available.To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Desktop (please complete the following information):
Additional context
When connecting using boto3, the same error is shown when using "auto", "ap-southeast", or any other regions other than
enam, weur, eeur, apac, auto
. In my case, when I usedapac
instead ofap-southeast
, the error disappeared. So I believe the ability to change the region in the client will fix the issue.The text was updated successfully, but these errors were encountered: