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

Bucket name is not DNS compatible when trying to create new bucket #10909

Closed
cyberduck opened this issue Dec 17, 2019 · 5 comments
Closed

Bucket name is not DNS compatible when trying to create new bucket #10909

cyberduck opened this issue Dec 17, 2019 · 5 comments
Labels
bug s3 AWS S3 Protocol Implementation worksforme

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Dec 17, 2019

109c56d created the issue

We've got S3 compatible service based on Dell ECS and we've got errors after upgrade from 7.1.X version to 7.2.X (current version is 7.2.2 (32045)):
Settings of connection :

Server : s3.ourdomain.ru
Port: 443

Access Key ID: demo
Secret Access Key: SuperSecretKey

Path: empty
All another options is set to default.

Creating new folder:
http://prntscr.com/qbw9hl

Error :
http://prntscr.com/qbwasz

Screenshot of connection properties:
http://prntscr.com/qbwg2y

Also when we change connection settings in option of path (for example we set it to name of created bucket with name /123 or 123) we've got error of certificate : "The certificate for this server is invalid. You might be connections to a server that is pretending to be s3.ourdomain.ru which could put your confidentional information at risk." But our certificate is wildcard and valid to 07.05.2021 and was issued by Thawte RSA CA:
http://prntscr.com/qbwe89
http://prntscr.com/qbwehl

Properties of connection:
http://prntscr.com/qbwfb3

Error of listing directory:
http://prntscr.com/qbwfgb

Thanks!

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jan 8, 2020

@dkocher commented

Make sure you choose a bucket name that is a valid DNS name.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jan 15, 2020

109c56d commented

"Make sure you choose a bucket name that is a valid DNS name."
I am sure that i choose all data correct. We still cant use latest version of Cyberduck with Dell ECS.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jan 31, 2020

109c56d commented

Is there any news regarding this ticket?

@cyberduck
Copy link
Collaborator Author

cyberduck commented Feb 19, 2020

109c56d commented

David, can you check this issue one more time? We've got this error after bugfix in 7.2.0 version (Default to use virtual hosted style to access bucket contents for third party S3 providers) in all clients CyberDuck applications? We are recommending to our clients use version 7.1.2 that was last in 7.1 branch where this issue is not reproducing.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Apr 15, 2020

@dkocher commented

Please make sure the bucket name is lowercase only.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
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

1 participant