If I had to guess, this is happening when the server fails to fetch the image. The image icon next to the title is there whenever piefed thinks the url is pointing to an image, but at a base level, remote image posts are just a special case of a link post. If this also happened to local image posts where somebody uploaded an image, that would be a sign of some kind of misconfiguration.
As for why the image fetching might be failing, it's hard to say. Sometimes sites just block any kind of cloud provider IP ranges as a blunt tool to stop scrapers.
feddit.online does not have the "Cache remote images locally" checkbox ticked at https://feddit.online/admin/misc so all images are served directly off their origin instances (or web sites in the case of normal news articles).
piefed.social does have that checkbox ticked and serves the same post with images from media.piefed.social, not from piefed.zip.
Because of this, feddit.online saves lots and lots of storage space and money but the cost is if any other instance or web site has problems the images will fail to load, as in this case. https://feddit.online/c/[email protected] looks fine to me but that's probably because 8 hours have passed and piefed.zip is working better now.
I just enabled the checkbox and will cache them locally, and I'll see the impact.
Where does it cache these files? Can I point it to an external drive, or does it have to cache on the server's local drive? Or does it go into the S3 bucket?
6 replies
I haven't changed anything other than having upgraded the server to the latest version.
Trying to bring the Devs into this conversation to see if it's something unique to this server:
@[email protected] @[email protected] @[email protected]
If I had to guess, this is happening when the server fails to fetch the image. The image icon next to the title is there whenever piefed thinks the url is pointing to an image, but at a base level, remote image posts are just a special case of a link post. If this also happened to local image posts where somebody uploaded an image, that would be a sign of some kind of misconfiguration.
As for why the image fetching might be failing, it's hard to say. Sometimes sites just block any kind of cloud provider IP ranges as a blunt tool to stop scrapers.
feddit.online does not have the "Cache remote images locally" checkbox ticked at https://feddit.online/admin/misc so all images are served directly off their origin instances (or web sites in the case of normal news articles).
piefed.social does have that checkbox ticked and serves the same post with images from media.piefed.social, not from piefed.zip.
Because of this, feddit.online saves lots and lots of storage space and money but the cost is if any other instance or web site has problems the images will fail to load, as in this case. https://feddit.online/c/[email protected] looks fine to me but that's probably because 8 hours have passed and piefed.zip is working better now.
I just enabled the checkbox and will cache them locally, and I'll see the impact.
Where does it cache these files? Can I point it to an external drive, or does it have to cache on the server's local drive? Or does it go into the S3 bucket?
S3, yep.
If S3, then absolutely no issue for me. It's turned on. I hope this improves the experience.