So, I run my own instance (dandroid.app), and as of about 10 days ago, all outgoing federation stopped working. Incoming federation still seems to work fine. I’m not sure exactly what changed. It was around the time that I set up pihole on my network, but I have since shut down pihole and federation has not resumed. I have tried restarting all the services with docker-compose down and then up. I also tried restarting my server completely.

What debugging steps can I take to figure out where the failure is occuring?

  • seahorse [Ohio]A
    link
    fedilink
    English
    arrow-up
    2
    ·
    10 months ago

    Try select * from instance where domain = 'popular.instance'; and see the last time it was updated via the updated column. I’ve been having to update that column with update instance set updated = now(); because once that timestamp becomes older than 3 days your instance assumes it’s “dead”.

    • Dandroid@sh.itjust.worksOP
      link
      fedilink
      arrow-up
      1
      ·
      10 months ago

      I checked a few instances and they were all last updated on November 18th. I ran that query and updated the updated field to now for all rows, but they aren’t continuing to update after that, and no traffic is coming through.

      • seahorse [Ohio]A
        link
        fedilink
        English
        arrow-up
        2
        ·
        10 months ago

        I believe anything prior to that timestamp will not federate. New stuff should.

          • seahorse [Ohio]A
            link
            fedilink
            English
            arrow-up
            2
            ·
            10 months ago

            No problem! I had the same issue and was losing my mind trying to fix it. It still doesn’t update the timestamp like it should automatically so I’ve been doing it myself.

            • Dandroid@dandroid.app
              link
              fedilink
              arrow-up
              2
              ·
              10 months ago

              I might just write a script to do it if mine does the same. Hopefully this gets fixed in 0.19.0