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

Always getting FAILED (StatusCode 400) #53

Closed
aaronczichon opened this issue Nov 3, 2015 · 7 comments
Closed

Always getting FAILED (StatusCode 400) #53

aaronczichon opened this issue Nov 3, 2015 · 7 comments

Comments

@aaronczichon
Copy link

I'm always getting an FAILED error. If I take a look into the index.js I can see an status code of 400.
Anyone else having this issue and/or a solution?

@j-norwood-young
Copy link

Also having this issue.

@rgcunha
Copy link

rgcunha commented Nov 13, 2015

same here. any thoughts? Just tried different user/bucket policy combinations. Nothing worked out so far.

@rgcunha
Copy link

rgcunha commented Nov 15, 2015

In my case the error was related with the region where the bucket was being hosted ( Frankfurt ). Changed it to Ireland and it's already working.

@cruzlutor
Copy link

Hi, in my case my Mac clock was ahead, You only have to adjust the time in your machine and it work again

Here more information
http://www.bucketexplorer.com/documentation/amazon-s3--difference-between-requesttime-currenttime-too-large.html

@subinsebastien
Copy link
Contributor

subinsebastien commented Jul 3, 2016

This could also be the reason --> #62

@lucasdavila
Copy link

It may be a problem with your credentials, or with the bucket and/or region.

Take a looks here http://docs.aws.amazon.com/general/latest/gr/rande.html if you aren't sure about the region you should use).

Also, as a contribution suggestion, printing the error details would make the problem solution easier, if possible.

@nitaigao
Copy link
Owner

Ive updated the error output with the status code and error object returned from AWS.

As this is a year old, if it comes up again we can open a new issue.

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

7 participants