Skip to content
This repository has been archived by the owner on Oct 13, 2020. It is now read-only.

NetworkingError: Network Failure #15

Closed
mint5auce opened this issue Apr 12, 2018 · 11 comments
Closed

NetworkingError: Network Failure #15

mint5auce opened this issue Apr 12, 2018 · 11 comments

Comments

@mint5auce
Copy link

Running S3Commander locally, I get the above error when trying to connect to my bucket.

I can successfully connect with the same details using other methods (such as transmit.app). I am using the 's3-eu-west-2' region.

What is causing the error? Can I get any more detailed feedback?

Thanks!

@CtrlC-Root
Copy link
Contributor

That doesn't seem like a valid region to me. Can you try using the eu-west-2 region instead? Check out the AWS documentation for a complete list of regions. Does that fix it?

@ahaurat
Copy link

ahaurat commented May 31, 2018

Having the same issue. I'm using 'us-west-1' so I'm guessing this issue isn't actually related to the region.

@CtrlC-Root
Copy link
Contributor

@ahaurat Are you using the latest release or master? The latest release only works for the older AWS signing protocol (v2) and therefore in regions like GovCloud. We're in the middle of a rewrite which supports the newer signing protocol (v4) which should fix this issue. That's why I haven't closed it yet, I'm waiting for the next release.

@ahaurat
Copy link

ahaurat commented May 31, 2018

@CtrlC-Root using master branch

screen shot 2018-05-31 at 9 40 21 am

@CtrlC-Root
Copy link
Contributor

@ahaurat I see you're running this locally. Did you configure a CORS policy on the S3 bucket that would allow that? I use the following for testing purposes:

<?xml version="1.0" encoding="UTF-8"?>
<CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<CORSRule>
    <AllowedOrigin>*</AllowedOrigin>
    <AllowedMethod>GET</AllowedMethod>
    <AllowedMethod>PUT</AllowedMethod>
    <AllowedMethod>POST</AllowedMethod>
    <AllowedMethod>DELETE</AllowedMethod>
    <MaxAgeSeconds>3000</MaxAgeSeconds>
    <AllowedHeader>*</AllowedHeader>
</CORSRule>
</CORSConfiguration>

@ahaurat
Copy link

ahaurat commented May 31, 2018

@CtrlC-Root Thanks for that! I had * for AllowedOrigin and thought that was enough but apparently I also needed the * for AllowedHeader. Cheers!

@CtrlC-Root
Copy link
Contributor

@ahaurat So it works? Obviously, once you host this in production somewhere, you'll want to restrict the CORS policy for security.

@ahaurat
Copy link

ahaurat commented May 31, 2018

Yup, it works great. Will definitely restrict the policy for production. Thanks again!

@CtrlC-Root
Copy link
Contributor

Glad to hear. I'm going to close this issue for now. When we reach feature parity with our previous implementation we'll make another stable release. Until then, feel free to open another issue or make a pull request if you run into anything serious.

@blake-regalia
Copy link

I think this bit about the CORS configuration for localhost development would make a nice addition to the README!

@CtrlC-Root
Copy link
Contributor

You're right, I'm going to add it right now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants