forked from cobyism/ghost-on-heroku
-
Notifications
You must be signed in to change notification settings - Fork 251
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
Internal Server Error on Image upload to S3 #22
Comments
I am getting Access Denied in Logs for uploading, I have given AMAZONS3FULLACCESS permission. When S3 is removed, works fine. Must be a problem in my access credentials. Will check. |
what was the solution in this case? |
Faced a similar issue. The fix was to make bucket publicly accessible in AWS bucket settings. |
Is there a solution to this problem that uses IAM rather than bucket settings? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @SNathJr
Nice work with maintaining this package.
I just deployed it to Heroku with S3. Initially I was getting Resource Not Found as I named the bucket incorrectly in config var, but now I am getting 'Internal Server Error, cannot upload image'
What can be the issue? I have double checked all vars.
Also, until you figure out #9 , Perhaps add steps for people on how to add (paid) theme to themes folder and then commit & deploy.
Thanks.
The text was updated successfully, but these errors were encountered: