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

Will not connect to S3. Fails silently. #4456

Closed
cyberduck opened this issue May 7, 2010 · 5 comments
Closed

Will not connect to S3. Fails silently. #4456

cyberduck opened this issue May 7, 2010 · 5 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented May 7, 2010

fdaf86d created the issue

Immediately after updating to 3.4.2, I could no longer connect to S3. Double-clicking on my S3 bookmark results in no effect, except a quick flash of text in the status bar. No error message, no connection.

Downgrading to 3.4.1 resolves this issue, and I can connect as normal.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 13, 2010

anonymous commented

Same issue here, but it's not silent. Cannot authenticate to S3 using Cyberduck 3.4.2. "Downgrading" to 3.4.1 fixed the issue immediately for me.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 16, 2010

@dkocher commented

#4445 closed as duplicate.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 18, 2010

@ylangisc commented

Make sure that the server name in the bookmark is set to s3.amazonaws.com instead of aws.amazonaws.com. Then please try again.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 18, 2010

fdaf86d commented

Replying to [comment:4 yla]:

Make sure that the server name in the bookmark is set to s3.amazonaws.com instead of aws.amazonaws.com. Then please try again.

Confirmed. Using either s3 or aws, Cyberduck will not connect when I upgrade to 3.4.2. Thanks.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 5, 2010

@dkocher commented

I cannot replicate this issue. Please try the latest snapshot.

Loading

@cyberduck cyberduck closed this Jun 5, 2010
@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.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants