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 doesn't work for non-Amazon accounts #4370

cyberduck opened this issue Apr 6, 2010 · 1 comment

S3 doesn't work for non-Amazon accounts #4370

cyberduck opened this issue Apr 6, 2010 · 1 comment


Copy link

@cyberduck cyberduck commented Apr 6, 2010

ea46cd0 created the issue

My company is building an open-source filesystem ( that has an S3 emulator gateway, and we'd like to get at least a partial list of S3 clients that will work with it. Unfortunately, best I can tell Cyberduck assumes that all S3 users are connecting to Amazon hosts.

This is something I can look into myself a little bit, but thought I'd check if there was a quick fix available from somebody who had more experience with the Cyberduck code, perhaps by replacing some hardcoded address links with a variable that is read out of the server address? :)

To reproduce:

  1. Set up some non-Amazon S3 interface service.
  2. Run Cyberduck
  3. Click "Open Connection"
  4. Fill in your S3 service's address and port in the "Server:" and "Port:" boxes.
  5. Fill your given key and secret key into the "Username:" and "Password:" boxes.
  6. Click "Connect."
  7. Wait until it fails, and notice a lot of references to "" in the transcript. ;)
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 10, 2010

@dkocher commented

Also refer to #4158. Please try the just released 3.4.2.


@cyberduck cyberduck closed this Apr 10, 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.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants