Skip Navigation

Getting an error when attempting to visit communities from outside links

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.

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

    The login issue I don't know

    • Okay, thanks for the info. I'll wait a day or so and see if anything changes.

      • 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

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

    • 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.

  • @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.

  • Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn't work well for people on different instances. Try fixing it like this: !imsa@lemmy.world

18 comments