This commit fixed the issue for me: https://github.com/LemmyNet/lemmy-ansible/commit/01b7fdcc75eb6ea0cdb7044bb9517be9f5ffd143
Same thing happened to me. Not entirely sure why yet but debugging seems to indicate something with the pictrs config
Baby bearded dragon
![](https://lemmy.world/pictrs/image/fc930ee7-4f78-449f-b13e-44c2ba6769dd.jpeg?format=webp&thumbnail=128)
![](https://lemmy.world/pictrs/image/fc930ee7-4f78-449f-b13e-44c2ba6769dd.jpeg?format=webp)
Was about 3 months old I think in this picture. Love the stretched out legs in this one!
On a VPS:
- mailcow for email for a personal domain
On home network:
- unraid server as a local fileserver for backups and media (repurposed from an i5 2500k with a bunch of drives added)
- unraid server hosts a bunch of containers -- plex -- jellyfin -- *arr apps
Edit: and hoping to play around with hosting a lemmy server in the next few days
Pixel 4a 5g. Overall, still works and performs well enough for what I do.
I did start running into an issue a few months ago where it would just drop signal and have to be rebooted to get service back. I think it may have been after an update and also might have been resolved with a more recent update as last couple weeks it hasn't happened.
It has also survived a couple drops without breaking π