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

Access to CloudFront gives "ERROR: [Errno 61] Connection refused" #454

Closed
nidi3 opened this issue Dec 30, 2014 · 6 comments
Closed

Access to CloudFront gives "ERROR: [Errno 61] Connection refused" #454

nidi3 opened this issue Dec 30, 2014 · 6 comments

Comments

@nidi3
Copy link

nidi3 commented Dec 30, 2014

All commands that access CloudFront fail with the message "ERROR: [Errno 61] Connection refused".
Has this something to do with #402 ?

@nidi3
Copy link
Author

nidi3 commented Dec 30, 2014

I found the problem. Https must be used (use_https = True in .s3cfg).
It's not a bug, but it could be helpful to issue a warning if one tries to access CF without https.

Btw. I have a working prototype for v4-authentication with CF. If you are interested, I can make a pull request.

@mdomsch
Copy link
Contributor

mdomsch commented Dec 31, 2014

Did you try master branch? Does CF not work there with v4 sigs?
On Dec 30, 2014 2:17 AM, "Stefan Niederhauser" notifications@github.com
wrote:

I found the problem. Https must be used (use_https = True in .s3cfg).
It's not a bug, but it could be helpful to issue a warning if one tries to
access CF without https.

Btw. I have a working prototype for v4-authentication with CF. If you are
interested, I can make a pull request.


Reply to this email directly or view it on GitHub
#454 (comment).

@nidi3
Copy link
Author

nidi3 commented Jan 2, 2015

https://github.com/s3tools/s3cmd/blob/master/S3/CloudFront.py#L547
This does not look like v4 sign.

@mdomsch
Copy link
Contributor

mdomsch commented Jan 9, 2015

CloudFront support in s3cmd is using API version 2010-11-01. API versions 2013-05-12 and above (including current 2014-11-06) require Signature v4. Clearly this is in need of some love, and I'd appreciate any help with it. @nidi3 I would love to see your patch.

@mdomsch
Copy link
Contributor

mdomsch commented Jan 9, 2015

To solve the immediate problem though, we can force CF calls to use HTTPS. Please see
https://github.com/mdomsch/s3cmd/tree/bug/cf-ssl
which now does this. If it works for you, I'll merge this to master.
Thanks,
Matt

@mdomsch
Copy link
Contributor

mdomsch commented Jan 10, 2015

I merged the above into master. Closing this bug. Please open a new pull request with your CF v4 signature patch.

@mdomsch mdomsch closed this as completed Jan 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants