Source

Its a gift link, so shouldn't be a paywall :)

As the title states, I have an issue where all images stored in pictrs are returning a 404 when trying to view them. You can see an example of this here https://lemmy.browntown.dev/post/27130.

If i check the pictrs docker volume, I can find the image manually and if I curl pictrs_ip:8080/image/original/[image.ext] i can view it in the browser. So I know for a fact that Lemmy is communicating with pictrs to upload the image, but there's something funky going on with viewing.

Hopefully someone here has an idea of where to go with this, I'm at my wits end lol. I've tried:

• Creating a different pictrs container and using that
• Pointing to an external ip for pictrs (i.e. 192.168.x.xxx instead of pictrs:8080)

Not sure what to do outside of this?

EDIT: Turns out the solution was to disable "cache assets" in nginx proxy manager! Not sure why that helped, but once I did that everything started working as expected.

As thr title states, has the community found a new home yet? Want get back to monitoring for those grail trackers!

I stood up my own instance, and it's federating (kind of?) but none of the posts are showing up with their comments. If I look on the main instance I can see the comments but not on mine.

This also applies to sticky posts not being stickied when i view from my own instance. Is this a bug, a misconfiguration on my end, or a result of servers being overloaded?

EDIT: In case anyone else has this, the issue was that I made the boneheaded mistake of just using the docker container for postgres i already had running without checking versions. Lemmy needs postgres15 and i gave it postgres11, causing comments not to be saved in the db and all sorts of funky issues.