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

cannot read container configuration #11883

Closed
cyberduck opened this issue Oct 24, 2021 · 5 comments
Closed

cannot read container configuration #11883

cyberduck opened this issue Oct 24, 2021 · 5 comments
Assignees
Labels
bug s3 AWS S3 Protocol Implementation worksforme

Comments

@cyberduck
Copy link
Collaborator

8033905 created the issue

The specified bucket does not exist. Please see attached printscreen.


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Can you please share your bookmark configuration. You may need to migrate to IBM Cloud Object Storage (COS).

@cyberduck
Copy link
Collaborator Author

49ec1a5 commented

I am also seeing this issue since upgrading to 8.0.0. I can connect to the S3 bucket and see the top level prefixes, but if I try to drill down I get the above error. I have tried the same bucket configuration with 7.10.0, 7.10.1 and 7.10.2 and they all work.
The credentials I am using are for a user with limited access to my S3 account. This user only has permissions on this bucket, not ListAllBuckets.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:2 jarrett]:

I am also seeing this issue since upgrading to 8.0.0. I can connect to the S3 bucket and see the top level prefixes, but if I try to drill down I get the above error. I have tried the same bucket configuration with 7.10.0, 7.10.1 and 7.10.2 and they all work.
The credentials I am using are for a user with limited access to my S3 account. This user only has permissions on this bucket, not ListAllBuckets.

Make sure you either set the bucket name in the default path or with the virtual hostname notation as in bucketname.s3.amazonaws.com.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please attach the Debug log if this continues to be an issue. You can find it in Preferences → Connection → Log.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
@dkocher
Copy link
Contributor

dkocher commented Dec 22, 2021

Duplicate for #12596.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug s3 AWS S3 Protocol Implementation worksforme
Projects
None yet
Development

No branches or pull requests

2 participants