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

Handshake failure. Unable to negotiate an acceptable set of security parameters #11110

Closed
cyberduck opened this issue Jul 13, 2020 · 4 comments
Closed
Labels
bug high priority s3 AWS S3 Protocol Implementation thirdparty Issue caused by third party

Comments

@cyberduck
Copy link
Collaborator

6d512a6 created the issue

Cyberduck is unable to connect on a S3 bucket if the bucket name contains a dot. For example bucket-name.domain.org

When trying to connect / list theses bucket, we get this error:
Handshake failure. Unable to negotiate an acceptable set of security parameters.

However, on the same s3 hosting, Cyberduck is working properly on any other bucket that doesn't have a "." dot characters in their name.

@cyberduck
Copy link
Collaborator Author

6d512a6 commented

Tested on several other S3 clients, and it's working well. So it's seems to be a Cyberduck issue.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I cannot reproduce this error with Amazon S3. Try to set the bucket as a default path instead of providing it in the Hostname when configuring your bookmark as a workaround.

@cyberduck
Copy link
Collaborator Author

6d512a6 commented

I'm still able to reproduce it.
I'm not using Amazon S3, but another S3 provider (using Ceph), this is why I'm providing a Hostname.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:4 emagnier]:

I'm still able to reproduce it.
I'm not using Amazon S3, but another S3 provider (using Ceph), this is why I'm providing a Hostname.

Double check the SSL certificate installed on the server.

@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 high priority s3 AWS S3 Protocol Implementation thirdparty Issue caused by third party
Projects
None yet
Development

No branches or pull requests

1 participant