After switching (back) to S3, avatars are not pointing to S3

(Travis) #1

I may be doing something wrong. After switching back to S3 uploads, custom avatars are broken.

The image file uploads correctly and appears in the S3 bucket but the image tag is:

<img alt="" width="120" height="120" src="/user_avatar/[forum.hostname]/vocino/120/5155.png" class="avatar">

This is on v1.3.0.beta10 +22.

Image uploads seem to be displaying correctly when uploading an image in a post.

(RĂ©gis Hanol) #2

Is the issue that avatars aren’t pointing to S3 (which is intended for now) or that they don’t work?

(Travis) #3

Upon further investigation, it looks like Discourse is redirecting that link but it’s not loading the image. If I go to the URL directly it still doesn’t work.

However, if I upload an image directly to S3 myself it doesn’t indeed load from the url. The bucket policy seems to check out, as well as the permissions, not sure why it wouldn’t be loading from Discourse-uploaded images.

(RĂ©gis Hanol) #4

That’s intended for the transition period.

So. the image isn’t on S3?

(Travis) #5

Yup, looks like it’s not uploading.

EDIT: Scratch that, it is uploading. The issue is that for some reason the URL is not actually working. I’m looking further.

I don’t know, I’m at a loss, it’s almost sporadic. It’s like it’s just choosing to half ignore the S3 setting. It points to it but doesn’t upload.

All the permissions check out and the same permission set works perfectly with backup uploads.

EDIT: Ok, sorry for all the edits. Looks like Discourse is uploading the /original/ but isn’t uploading the file that’s getting referenced by the post.

So /512773671fde4c557592493db7b8e77d1a0b4b1c4f17.jpg does not exist but /original/a/a/aa4c1105445c3565bc8f1b8011da4f1e8ad93517.jpg does.