The discussion revolves around an issue with uploading custom avatars in Discourse version 2.5.0.beta2. fb9572a reports that the image uploads successfully to an S3 bucket but fails to save after clicking the save button. The user provides screenshots and details of the issue, including the fact that the image can be accessed directly via the S3 CDN URL.
fb9572a shares admin logs showing the issue and has two questions about asset handling. sam suggests checking if the issue is reproducible on meta.discourse.org, which also uses S3 for uploads. fb9572a reports that the issue is not present on meta.discourse.org, but notes a difference in CDN setup (Cloudflare vs S3 CDN).
sam suggests that the CDN setup might not be the cause of the issue and recommends configuring an S3 CDN. fb9572a clarifies that they are already using an S3 CDN, which works fine for topic images, but not for saving profile pictures. fb9572a shares a link to a similar issue on meta.discourse.org and requests sam to take a look.
I got this problem when uploading a custom image as avator. it is uploaded successfully and can be seen in the popup modal. It’s been upload to s3 bucket and can been seen. However after I click save button, it’s not been saved i guess. Please check the screenshots.
Yes we are already uploading images to s3 bucket and have s3 cdn pointing to it. This works fine in the topics. Just don’t know why during saving it can’t fetch the image.