-
Notifications
You must be signed in to change notification settings - Fork 10
NetworkingError: Network Failure #15
Comments
That doesn't seem like a valid region to me. Can you try using the |
Having the same issue. I'm using 'us-west-1' so I'm guessing this issue isn't actually related to the region. |
@ahaurat Are you using the latest release or |
@CtrlC-Root using |
@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:
|
@CtrlC-Root Thanks for that! I had * for AllowedOrigin and thought that was enough but apparently I also needed the * for AllowedHeader. Cheers! |
@ahaurat So it works? Obviously, once you host this in production somewhere, you'll want to restrict the CORS policy for security. |
Yup, it works great. Will definitely restrict the policy for production. Thanks again! |
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. |
I think this bit about the CORS configuration for localhost development would make a nice addition to the README! |
You're right, I'm going to add it right now. |
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!
The text was updated successfully, but these errors were encountered: