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
Proxy connection failure #5239
Comments
It looks like you have set |
I haven't set that in the Path setting of the bookmark. It's in the 'Web URL' setting, but I can't change it, I presume it's been placed there by the fact of selecting S3 as the connection type. I've included a screenshot which shows the bookmark edit window open to the bookmark which is failing to load. I've redacted the bits of the image that contained AWS user data, hence the cutout bars. The bookmark visible "Development-S3-OSX" has a path of "/medidata-osx". That doesn't work either, and fails in the same manner with the same attempted connections and errors. It looks like it's ignoring the path, or something like that. I'll try to get a screenshot of that: |
This is strange and I can't reproduce. Can you try if you still have the issue when using the latest snapshot build from (http://update.cyberduck.ch/nightly/). |
Downloaded build 7154 and tried. Exact same behavior. None of the requests in the transcript have anything other than the base path in them: GET https://s3.amazonaws.com/ HTTP/1.1 ...no matter what path the bookmark (or manual connection window) has. The 'URL' field in the connection window reports: https://@s3.amazonaws.com:443/ (or whatever path I have in the 'path' field) ...but that doesn't seem to be what's being requested. One add'l point - I am behind a Bluecoat proxy (although I think they've configured it to allow direct access to S3). I'm not sure that's relevant, since as I said it seems to work fine with 3.5.1. Hm, I realized I should probably include a transcript of a successful 3.5.1 connection. Here it is: ---cut---
---cut--- |
Replying to [comment:8 https://www.google.com/accounts/o8/id?id=aitoawnuslsj0omptnilptbjmoouhffiiyi1z-u]:
Thanks for the additional information. I can replicate the issue now with a proxy setup. |
As a workaround you can use a HTTP connection without SSL until this issue is resolved. |
Just to confirm: works for me now in build 7192. Many thanks. |
I have been using 3.5.1 with no issues to connect to S3. When I upgraded to 3.6.1, none of my S3 bookmarks would work, nor could I manually connect. When I try to connect, all attempts fail with an error message that reads: "I/O Error: Connection failed - Request Error." The log window shows many GET requests, but all to: "URL http://s3.amazonaws.com/ HTTP/1.1", not to the full URL of my account.
All connections were made as type 'Amazon S3', using Access Key ID for username and Secret Access Key for password. The path attempted doesn't seem to make a difference ('/' or sub paths).
Downgrading to CyberDuck 3.5.1 fixed the problem with no change to any pref files or bookmarks - all connections open and behave normally.
Transcript of log drawer from a single 3.6.1 connection attempt (auth info redacted, naturally):
The text was updated successfully, but these errors were encountered: