Cyberduck Mountain Duck CLI

#2993 closed defect (worksforme)

Amazon S3 setup quirks

Reported by: Owned by: dkocher
Priority: normal Milestone: 3.2
Component: s3 Version: 3.1.2
Severity: major Keywords: amazon s3
Cc: Architecture:


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, otherwise using the same info as before, and it works perfectly.

Change History (2)

comment:1 Changed on Feb 21, 2009 at 4:49:04 PM by dkocher

  • Milestone set to 3.1.3
  • Status changed from new to assigned

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

comment:2 Changed on Mar 16, 2009 at 1:50:48 PM by dkocher

  • Resolution set to worksforme
  • Status changed from assigned to closed

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

Note: See TracTickets for help on using tickets.