I’ve been searching for communities using https://lemmyverse.net, but lately every time I click on a link I get the error shown above (I’ve edited out my username because it’s not really important). For instance the above error was shown when I clicked on the link https://slrpnk.net/c/imsa@lemmy.world

After I refresh the page I can see the content of the community, but I appear to be logged out. Then I hit refresh again and I log in, but sometimes the posts all disappear so the community appears to be empty.

Seems like something weird is going on here. I assume it’s a bug. I’m happy to give any extra details you might need to figure out the problem.

EDIT: Turns out I couldn’t see posts after logging in because my language wasn’t set properly, and the other errors have disappeared with time.

  • Blaze@sopuli.xyz
    4·
    11 months ago

    The first error message is standard if no one from your instance ever visited the community.

    The login issue I don’t know

      • poVoq@slrpnk.netM
        2·
        11 months ago

        Usually the best way is to take the full URL of the remote community and paste it into the search bar. After 1-2 seconds the remote community is fetched from the server and you can subscribe to it.

        The Lemmy devs are currently working on an improved method to subscribe to remote communities here: https://github.com/LemmyNet/lemmy-ui/pull/1875

        • Excrubulent@slrpnk.netOP
          1·
          11 months ago

          Okay, good to know. The issue is still happening. Also when you say the “full URL” and “search bar”, there are number of things that could mean:

          To use one community I’m having the issue with as an example, the full URL could be any of:

          https://slrpnk.net/c/iracing@sh.itjust.works
          !iracing@sh.itjust.works
          https://sh.itjust.works/c/iracing

          And by “search bar”, it seems you could mean my browser’s search bar, or the search bar on this webpage, which is effectively the slrpnk.net search bar.

          Putting any of the URLs into the slrpnk.net search bar yields nothing. Using the slrpnk.net URL yields the problem I’m experiencing, and the sh.itjust.works URL shows the posts that I can’t see using the other URL, but obviously I’m not logged in there.

          It seems as though after a little while the error stops popping up, but it took hours at least, not seconds.

          • poVoq@slrpnk.netM
            2·
            11 months ago

            Sh.itjust.works has been down for quite some time recently. Maybe you just happened to test it then?

            For me putting the original URL into the searchbar of slrpnk.net works everytime, so I don’t know how to answer your question otherwise.

            • Excrubulent@slrpnk.netOP
              1·
              11 months ago

              Hm, looks like we’re having different experiences then. I’m on Windows Firefox, not sure how else to describe all the myriad ways it could be different.

              Although testing it just now, I got the problem of seeing no posts via slrpnk and all the posts from the instance url directly.

              Also the slrpnk.net search seems to yield very little most of the time. I wonder if there’s an issue with my browser.

  • teft@lemmy.world
    2·
    11 months ago

    Clear your web cache and see if that helps. Might fix whatever is causing you to not see the posts while logged in.

    • Excrubulent@slrpnk.netOP
      1·
      11 months ago

      Thanks, I tried that and there was no difference. Also I already tried CTRL+F5 which to my knowledge fetches the whole webpage without relying on cache and that doesn’t work either.

  • Excrubulent@slrpnk.netOPEnglish
    2·
    11 months ago

    @Blaze@sopuli.xyz, @poVoq@slrpnk.net, @teft@lemmy.world, thanks for your help. I think the issue turns out to be that I didn’t set my language, it was still on undetermined, so as the settings page warns you, you won’t see most posts. Hopefully this is useful to other people that have the same issue at least.

    As for why I was getting those errors, I assume that was unrelated and it appears to have sorted itself out now.