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

S3 Connection - Failed CERT check #5063

Closed
cyberduck opened this issue Jul 21, 2010 · 2 comments
Closed

S3 Connection - Failed CERT check #5063

cyberduck opened this issue Jul 21, 2010 · 2 comments
Assignees
Labels
bug s3 AWS S3 Protocol Implementation worksforme

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Jul 21, 2010

d6f3a5e created the issue

Hi Cyberduck amazing peoples!!!!

I can access my buckets anonymously (read-only! ARGH!), but when I try to sign in regularly, I get a certificate error that I can't bypass or (as I have right now) it won't sign in and I DON'T even get the certificate error.

Is there something I'm missing?

Port is 443
Username and password are correct
server is MYbucket.s3.amazonaws.com

Gah! Frustrating! :D

Fanks!

C

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jul 21, 2010

@dkocher commented

Just try to sign in using the default hostname without prepending the bucket name.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jul 21, 2010

d6f3a5e commented

Took out the prepend and it still didn't work, so I logged into Amazon S3 to double check my account details. The password I've been using for MONTHS had a character missing in the middle... Must've 'highlighted n' wiped' it away when I tried to use it this morning.

Everything is working now.

Many thanks for your time, an apologies for wasting it. :D

C

@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

2 participants