versionz is experiencing a permission issue with images on their Digital Ocean droplet instance after updating to 2.9.0.beta1. IAmGav notes that the issue is due to the images being hosted on AWS, which is a Discourse setting. versionz is unaware of this and disappointed, suspecting the thumbnail plugin.
IAmGav suggests checking the S3 fields in the admin settings, while pfaffman explains that the issue might be due to the site’s migration from Discourse.org hosting, where the uploads were stored in an Amazon bucket.
versionz resolves the issue by re-uploading the logo and category images, but questions whether Discourse will continue to endorse AWS. IAmGav replies that it’s up to the user’s preference, but versionz expresses concerns about AWS’s environmental impact. pfaffman notes that stopping the use of AWS would be challenging and that it’s a relative issue compared to other companies.
Anyone else experiencing this?
Digital Ocean droplet instance is failing to load images after recently updating 2.9.0.beta1 Side note: I was unaware that DO uses AWS for image hosting - not a fan of Amazon so kinda disappointed
Response from DO
The error when accessing the images in the browser is Access denied. It looks like you have a permission issue with your remote server. You will need to check the permission and set the right permission.
When you moved your site from Discourse.org hosting you didn’t get your uploads and they are still on their Amazon bucket. You didn’t notice and they only just now removed them.
You need to email team@discourse.org and ask if they can restore them. If they can you’ll need to move them to your local storage.
Well, they stopped using cloudflare. Stopping aws will be a bit harder. I’m afraid that if you don’t want to usevaws or companies as bad as aws you’ll need to stop using the internet.
