Skip to content
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 cn-north-1 (no region known for bucket) #11197

Closed
cyberduck opened this issue Oct 9, 2020 · 8 comments
Closed

Unable to connect to cn-north-1 (no region known for bucket) #11197

cyberduck opened this issue Oct 9, 2020 · 8 comments
Assignees
Labels
bug fixed s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Oct 9, 2020

2cefc47 created the issue

Used provided connection profile, was working fine until some newer version broke it, so reverted to older version and got it working again.

Now neither older or latest version could work. Error: "Login failed: access id not found blah blah".

Turned on debug logging and "no region known for bucket" pops up. This is strange as region should already be provided via URL.

Also tried the CLI credentials connection profile hoping that region set in ~/.aws/config can shed some light on this issue but no prevail.

Loves this tool. Please help. Thanks!

@cyberduck
Copy link
Collaborator Author

cyberduck commented Oct 9, 2020

@dkocher commented

This is possibly a regression caused by a refactor of the region lookup for buckets. Could you provide temporary access credentials to a bucket in cn-north-1 to test this. Unfortunately we are unable to open an account in AWS China.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Oct 9, 2020

2cefc47 commented

When I tried to create AKSK for you I found a way to connect:

  • Select S3 HTTPS instead of China profile
  • Enter .s3.cn-north-1.amazonaws.com.cn as domain name
  • Connect

However, I could only view the files but not able to download. Strange.

Here for you test, read only:

AKIAYOVLZZHW7MC3XQFI
6aAX3kTjMPApWYyvsECXjTQCPBm2twoHWkeH+U39

s3://test-duck

@cyberduck
Copy link
Collaborator Author

cyberduck commented Oct 10, 2020

@dkocher commented

Thanks for the test credentials. I can reproduce and we are working on a fix.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Oct 10, 2020

@dkocher commented

In 908d12f.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Oct 12, 2020

@dkocher commented

#11203 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 2, 2020

@dkocher commented

Milestone renamed

2 similar comments
@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 2, 2020

@dkocher commented

Milestone renamed

@cyberduck
Copy link
Collaborator Author

cyberduck commented Dec 30, 2020

@dkocher commented

Milestone renamed

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug fixed s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants