I have so many pending subscriptions for communities in other instances and I have no idea how to fix it. Is there something that I can do, or do I just have to wait? I’m still a bit unsure about how a lot of this stuff works lol

  • RuudMA
    link
    71 year ago

    First refresh the page , sometimes that helps. Then try cancel and re-subscribe

    If that doesn’t work probably the remote server is too busy.

    • @deadcyclo
      link
      2
      edit-2
      1 year ago

      Or simply just wait. Subscription pending seems to go away after a while. And federation seems mostly to work, even though subs are listed as subscription pending.

  • @Oxff
    link
    61 year ago

    I had this too, I found if I cancelled and then re-applied it worked after waiting 30 seconds.

  • @[email protected]
    link
    fedilink
    41 year ago

    Me too, But I did found some common ground for me. They were all communities from the same instance(lemmy.ml).

    Does anyone know if there are any issue’s with lemmy.ml? cause I don’t believe my instance is defederated from them.

    • @Roman0
      link
      51 year ago

      TBH federation from large instances like lemmy.world or lemmy.ml seems kind of sluggish. Posts, comments and upvote counts are way off on my private instance, as well as many lemmy.ml subscriptions hanging “Pending” forever. No such issues from smaller instances. I’ve seen lemmy.world set its federation worker count to something crazy like 10000, so I don’t know what else they could possibly do to improve things, or what I could do for that matter.

  • 🇺🇦 seirim
    link
    fedilink
    21 year ago

    Can try at Lemmy.pro and I’ll approve you. Sometimes the applications don’t go through to admins or expire, ours seems to be working now.

    • @LaunchesKayaksOP
      link
      11 year ago

      Subscription is now listed as pending in the cybersecurity group

  • Awhiskeydrunker
    link
    fedilink
    1
    edit-2
    1 year ago

    I’ve seen that message come up for some instances but everything still subscribed, just went back and checked. On kbin.social instance though so could be a Lemmy to other Lemmy instance specific issue?