Currently known problematic:

I’ll look into possible causes for the problem, as of right now the most likely culprit is the excessive server load on these two instances preventing the federation actions from completing.

    • NeshuraOPMA
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      Regarding federation, searching for !aobprepub@bookwormstory.social should work but currently doesn’t (reliably), please use the full url instead (in this case https://bookwormstory.social/c/aobprepub), federation might take some time so give it up to a minute before assuming it failed.

      If that doesn’t work please refer to my other comment

    • NeshuraOPMA
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 year ago

      Federation with lemmy.fmhy.ml worked in the past and the only thing that changed in between was me updating lemmy. I’ll see if I missed a step while upgrading and report back (1-2h)

      Edit: don’t seem to have missed anything, you could either wait for the admin of your instance to update lemmy or ask them to do so. It would likely resolve the issue as federation with 0.17.4 instances of lemmy still works and lemmy.fmhy.ml is on version 0.17.3

  • Yuki2501
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I’m trying to connect to here from a Mastodon instance, but when I type in the account in the search box, no results are found. A hypothesis that came up is that cloudflare is blocking some requests so federation can’t take place. Are we behind CF?

    • NeshuraOPMA
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      No I considered it but decided against it due to reports that cloudflare caused issues. It might be related to my proxy setup but I’ll have to investigate that.

    • NeshuraOPMA
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      Looked into it a bit and also cleaned up the proxy config.

      Result: Maybe Mastodon is confused because my public IP also has a Mastodon instance but other than that, no idea. Looking up Mastodon Instances from here works but for some reason not the reverse. Will investigate more tomorrow