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

Amazon S3 setup quirks #2993

Closed
cyberduck opened this issue Feb 16, 2009 · 2 comments
Closed

Amazon S3 setup quirks #2993

cyberduck opened this issue Feb 16, 2009 · 2 comments
Assignees
Labels
bug s3 worksforme
Milestone

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Feb 16, 2009

18103bf created the issue

On computer 1, I launched CyberDuck 3.1.2, and started a new bookmark for an Amazon S3 login. I filled in nothing for the server, then used my accesskeyID for the username and the secretaccesskey for the password. CyberDuck gave me some warning about the connection being insecure, but connected, and allowed me to create a folder (bucket) and upload a file, but after quitting and relaunching CyberDuck, had the following problems:

  1. Server was listed as https://null and it wouldn't let me change it.
  2. It rejected my password (secretaccesskey).
  3. It wouldn't remember my password.

On a secondary computer, I tried the same thing, but this time I manually typed the server as s3.amazonaws.com, otherwise using the same info as before, and it works perfectly.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Feb 21, 2009

@dkocher commented

When S3 is selected for the protocol, editing the hostname should no longer be possible and always default to s3.amazonaws.com

@cyberduck
Copy link
Collaborator Author

cyberduck commented Mar 16, 2009

@dkocher commented

I cannot replicate this issue. Please provide the exact steps required. What localization were you using?

@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 worksforme
Projects
None yet
Development

No branches or pull requests

2 participants