I followed my communities from my Mastodon account on die-partei.social to stay up to date. Now I noticed that nothing showed up in my timeline for quite a long time.

Apparently the following has been locked. Communities on lemmy.ml I can still follow without any problems, on lemmy.ca communities I get a notice that a follower request was made - which of course never arrived. The same applies to the attempt to follow my own lemmy.ca account from Mastodon.

Was this option intentionally blocked, is there a problem here?

  • @nutomicA
    link
    311 months ago

    The way follows work in this case is that Mastodon sends a Follow activity to the Lemmy inbox, and Lemmy responds with Accept to the Mastodon inbox. If the follow action is stuck as pending, then one of those didnt get delivered properly.

    To debug this, grep the logs for the Mastodon domain name while sending a follow. You should have RUST_LOG=...,lemmy_apub=debug,activitypub_federation=debug in docker-compose.yml. If it works correctly, you should see the incoming Follow and outgoing Accept activities being logged. It might also help to get logs from the Mastodon side.

    • @smorks@lemmy.caM
      link
      fedilink
      2
      edit-2
      11 months ago

      thanks for the info! i will try this when i have some free time, and hopefully be able to get to the bottom of this.

      edit:
      just tried it. similar to what i found above, i see the Follow and Accept activities being logged when sending a follow request from mtdn.ca, but not my main account social.linuz.pizza. it could be it’s getting blocked along the way, for whatever reason. will contact the admin for social.linuz.pizza to see if they can help get this figured out, or if they can provide any more info.

      • @smorks@lemmy.caM
        link
        fedilink
        211 months ago

        ok, after talking with the admin of social.linux.pizza, it was because ipv6 wasn’t working. once I got that fixed, everything started working again normally.

        @oliver@lemmy.ca, @n7gifmdn@lemmy.ca you may have to contact your mastodon admins and get them to check to make sure lemmy.ca is active or something.

        • @smorks@lemmy.caM
          link
          fedilink
          211 months ago

          ok, i don’t think this issue is fully resolved yet. it seems that ipv6 seems to stop working every once in a while, and just doing a reboot of it appears to fix it. i’m going to contact my vps support to see if they can help.

          • OliverOP
            link
            fedilink
            211 months ago

            Thanks for the commitment and success that it works soon. Can hardly wait. 😉

            • @smorks@lemmy.caM
              link
              fedilink
              111 months ago

              ok, i’ve made some changes this morning that will hopefully resolve the ipv6 issues. i will continue to monitor it for the next few days to make sure everything is working correctly.

              • @smorks@lemmy.caM
                link
                fedilink
                211 months ago

                it’s been over two days and the ipv6 connection appears to be holding. i will continue to monitor it but i believe the issue has been resolved. 🎉

                  • @smorks@lemmy.caM
                    link
                    fedilink
                    English
                    211 months ago

                    you will probably need to contact the admin of your instance (or I can if you let me know which instance you’re on) so they can re-enable communication with lemmy.ca. from what I understand, since the ipv6 hasn’t been working since late January, mastodon will eventually just give up. so the instance admin I contacted said they just pressed a “Start Deliver” button and things started working again on that instance.