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.

Sign up for GitHub

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

Jump to bottom

Cannot read container configuration for S3 bucket in server field #11896

Closed
cyberduck opened this issue Nov 4, 2021 · 2 comments
Closed

Cannot read container configuration for S3 bucket in server field #11896

cyberduck opened this issue Nov 4, 2021 · 2 comments
Assignees
@dkocher
Labels
bug s3 AWS S3 Protocol Implementation worksforme
Milestone
8.0.2

Comments

@cyberduck
Copy link
Collaborator

@AliveDevil created the issue

For S3 connections to bucket.s3.amazonaws.com navigating to any path results in a Cannot read container configuration.

This is due to:
S3VersioningFeature trying to get path container information, which cannot be retrieved, as the bucket (from containerService, which is a DirectoryDelimiterPathContainerService) is already supplied in the server hostname.

Fixing requires checking whether a bucket name has been set in the hostname to prevent subsequent checks for buckets in buckets.
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Make sure you only define the bucket name either as part of the hostname in the Server field or in Path but not both. Thus if you have set the Server to point to a single bucket like bucket.s3.amazonaws.com make sure the Path field is empty or points to a folder inside the bucket only.

@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.
Assignees

@dkocher dkocher

Labels
bug s3 AWS S3 Protocol Implementation worksforme
Projects
None yet
Milestone
8.0.2
Development

No branches or pull requests
2 participants
@dkocher @cyberduck