Cyberduck Mountain Duck CLI

#9582 closed defect (duplicate)

Need bookmark specific proxy support

Reported by: skellish Owned by:
Priority: normal Milestone:
Component: core Version: 5.0
Severity: normal Keywords:
Cc: Architecture:


In our environment, we operate behind a corporate firewall and all traffic goes through a corporate proxy server which requires authentication for non-80/443 traffic. Simply pointing cyberduck at our proxy server does not work because I guess cyberduck is user some other protocol when accessing S3 and in that case, the proxy expect NTLMv4 authentication. To work around issues like this, I run cntlm locally. When using S3Brower, I can explicitly tell S3Browser to use my local cntlm without touching the "system proxy" info used by my browsers. I would need cyberduck to support this in order to be able to use it instead of S3Browser.

Attachments (2)

6-3-2016 4-12-20 PM.png (24.7 KB) - added by skellish on Jun 3, 2016 at 8:13:57 PM.
6-3-2016 4-19-26 PM.png (50.4 KB) - added by skellish on Jun 3, 2016 at 8:20:11 PM.
S3Browser Proxy Screen

Download all attachments as: .zip

Change History (6)

comment:1 Changed on Jun 3, 2016 at 8:08:59 PM by dkocher

Connecting to S3 just requires HTTPS on port 443 therefore your default proxy settings should just work here as well.

Changed on Jun 3, 2016 at 8:13:57 PM by skellish

Changed on Jun 3, 2016 at 8:20:11 PM by skellish

S3Browser Proxy Screen

comment:2 Changed on Jun 3, 2016 at 8:22:34 PM by skellish

ok... here is the error I get when opening a connection to S3.

I get the same error regardless of whether "Use system proxy" is checked or not

S3Browser does not have a problem connecting:

comment:3 Changed on Jun 6, 2016 at 8:21:44 AM by dkocher

Can you please post your system proxy settings.

comment:4 Changed on Jun 7, 2016 at 11:08:11 AM by dkocher

  • Resolution set to duplicate
  • Status changed from new to closed

Duplicate for #5815.

Note: See TracTickets for help on using tickets.
swiss made software