As you may have read in other threads, this version of Lemmy (0.19.1) seems to have bugs in outgoing federation on some instances.

As a temporary fix, we have added a scheduled restart of Lemmy every hour. It only takes a few seconds to restart, and the big advantage is that your comments and posts are only delayed up to 1 hour before they federate to other instances. You probably wont notice the restart even.

This will be in effect until a bug fix arrives from Lemmy developers, probably after new years sometime.

Thanks for reading and merry x-mas to everyone. :)

  • Allero@lemmy.today
    0·
    6 months ago

    Just this day caught lemmy.today down twice, and first time it was super very dead for much longer than a few seconds or minutes.

    Wonder if others had the same experience.

    But first, enjoy Christmas holidays! All that stuff can be sorted out later, if there even is a way to fix it on the server admin side.

    Thanks for keeping us informed!

    • mrmanager@lemmy.todayOPM
      0·
      6 months ago

      Yes, it seems the restart is not as reliable as I was hoping for.

      Its a docker compose restart of the entire stack but that has proven to work only sometimes, which is not good enough. This afternoon it failed once (as you noticed), then worked 4 times, then failed once more.

      We will figure out a more reliable way to restart, but for now, the restart has been removed again.

      Really sorry about all this. Just trying to find a way to make federation work again since its very frustrating when it doesnt.

      Anyway, merry Christmas and thanks for being understanding during all this.

      • waldenA
        1·
        6 months ago

        For what it’s worth, I set up a cronjob on my instance to restart just the lemmy container every 6 hours. It looks like 0 */6 * * * docker container restart lemmy-lemmy-1. Federation has been pretty good so far, but it has only been in practice for less than a day.