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

Images added to S3 but not completing upload #18

Closed
jkentjnr opened this issue May 25, 2015 · 5 comments
Closed

Images added to S3 but not completing upload #18

jkentjnr opened this issue May 25, 2015 · 5 comments

Comments

@jkentjnr
Copy link

Getting an issue when I upload a blog cover or logo where the image is uploaded to Amazon S3 but the UI never completes. It simply displays the wiggly cat indefinitely. Is there anyway to view the logs for ghost-on-heroku or does this issue sound familiar?

Cheers,
James

@jkentjnr jkentjnr changed the title Images Added to S3 but completing upload Images added to S3 but not completing upload May 25, 2015
@cobyism
Copy link
Owner

cobyism commented May 25, 2015

Sounds like you haven’t got the S3 bucket policy configured to allow read-access for anonymous clients. If that’s the case, then you’ll want to head to your AWS console, find the bucket in S3, and make sure you have an appropriate policy set up.

2015-05-25 at 9 43 am

Then put a policy in place along these lines:

2015-05-25 at 9 48 am

E.g. if your bucket name is mybucket, then the policy might look like:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "MakeEverythingPublic",
            "Effect": "Allow",
            "Principal": "*",
            "Action": "s3:GetObject",
            "Resource": "arn:aws:s3:::mybucket/*"
        }
    ]
}

Feel free to reopen if this turns out to be something different 👍

@cobyism cobyism closed this as completed May 25, 2015
@farschmessivo
Copy link

Hi @cobyism I'm still having issues after tweaking the bucket policy

screenshot 2015-06-15 14 08 52

@cobyism
Copy link
Owner

cobyism commented Jun 16, 2015

@farschmessivo Is this the same issue as you’ve opened in #20? or are you seeing that error when public users attempt to read images stored in S3?

@jonathanconway
Copy link

Having this issue still, even after adding a policy as suggested above. @farschmessivo did you manage to fix this?

@jonathanconway
Copy link

Never mind, fixed it by fixing the region to be correct. 👍

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

4 participants