I would like to thank @TheDude for giving a reset a try. Hopefully the next lemmy version will fix the issue but at least for now “active” feed should be fresh again.
You must log in or # to comment.
Suddenly Lemmy is usable! Thanks, hoping for a more permanent solution… 🤞
An internal crash was identified in Lemmy and 0.18 should have fixed it. https://github.com/LemmyNet/lemmy/issues/3076
I just set up my instance yesterday and the day before, I saw some stuff that seemed dodgy so I just have a cron job to restart the software every so often.
Keep in mind that the outbound comment/post sending queue is in RAM only and will be lost in 0.17.4 with a restart
