I am currently getting signed out every minute from lemmy.world. This is not a client side cache issue. I tested making API calls from the command line (with curl) with no cache and the issue still occurs. One call I get the correct response, the next I get a 400 telling me im not signed in.

I’m primarily testing with the https://lemmy.world/api/v3/user/unread_count api endpoint. I’m not sure if this issue occurs with all endpoints.

Reproduction steps:

  1. Get a lemmy.world JWT token for your account using your desired method (eg. postman).
  2. curl https://lemmy.world/api/v3/user/unread_count?auth={JWT_TOKEN_HERE}
  3. Note the 400 error. If you do not get an error repeat step 2.

Edit

This issue only seems to affect lemmy.world so a temporary workaround is to use a different instance for the time being.

  • @[email protected]
    1•2 years ago

    Ah damn. Was wondering what was happening. My lemmy.world account is unusable atm due to the bug. I’m gonna have to figure out what all of my subs were.

    • @[email protected]English
      2•2 years ago

      There are tools that can help! https://lemmy.ml/post/1875767

      I made LASIM - it’s takes 2 API calls to fetch your subscriptions (1 login, 1 profile), so with lemmy.world being 50/50 on those calls, you might have to try a few time, but once you have em, it will be easy to push them to a new instance.

  • @[email protected]
    4•2 years ago

    Ahhh thanks for that! I took could not stay logged in, annoyingly id find out when I attempted a post/reply, “not logged in”. Using Connect or website.

    I installed jerboa, logged in ok and here I am. If it goes bad too then I dunno…

  • @[email protected]English
    1•2 years ago

    I was running into this across both my accounts on lemmy.world. Changing my password seems to have resolved it both on the web and in Mlem.

  • Xæris
    2•2 years ago

    Same here. All Edge, Firefox and Safari keep logging me off. Same with Memmy iOS app.

    • idunnololz_testOP
      2•2 years ago

      The issue is server sided so it will not matter what you use unfortunately. Technically a temp but terrible fix is to keep retrying on 400s (not signed in) until a 200 (success) is returned. This is terrible because you pretty much never want to retry for 400 errors because 400 errors are client side errors (except in this case).

      • Xæris
        3•2 years ago

        Thx for elaborating. Not the answer one wants to hear, but at least I won’t continue foolishly to restart browser and clear cache / cookies.

  • @[email protected]
    10•2 years ago

    Yeah. Lemmy.world is currently unusable on the desktop. I don’t have that problem in Memmy. Growing pains but I hope the problem will be fixed soon. Do anyone know if one of the mods in North America are aware of the problem?

    • @[email protected]
      0•2 years ago

      Hey! you actually gave useful information. Some people are just grunting or snapping at people hoping someone figures it out lol.

    • @[email protected]
      4•2 years ago

      I was having trouble in liftoff and the browser. Cleared data and cache from liftoff thinking maybe something got messed up there and now I can’t even log back into my .world account 🤷‍♂️ I’ll hang here for a bit I guess.

      • @[email protected]English
        2•2 years ago

        I’m choking in desktop browser and in liftoff. Jerboa seems ok. It’s weird to me how different clients react differently, I’m not sure how they interact differently.

  • @[email protected]
    32•2 years ago

    Sounds like lemmy.world runs on 2 instances and the requests are being loadbalanced between those two. That and that the jwt secret is different between those two instances causing one to accept and the other to reject

  • xaon_rider92
    3•2 years ago

    I’m having the same issue… might switch to an alt or something for now.

  • @[email protected]
    4•2 years ago

    Making a new post is a nightmare. I wish the submit button would time out in these instances so you can try again. Right now I’m having to copy and paste into a new tab and hope for the best (but fail, 5 times and counting).

  • @[email protected]English
    5•2 years ago

    At least when you can’t log in on one instance you can just login on another. Downtime doesn’t mean you have to go do something else anymore!

    I’m seeing the same issues on my app, calling login, then immediately using that jwt to fetch the site details and it doesn’t give my_user half of the time, and if my app loads far enough to check the unread count I get not_logged_in

  • @[email protected]
    27•2 years ago

    Same problem for me it seems, dunno if I’ll even be able to comment. Refuses to stay logged in.

    • idunnololz_testOP
      11•2 years ago

      From my tests, it’s almost perfectly a 50/50 whether any API requests you make will yield a 200 (success) or a 400 (not signed in). If you perform an action that takes 3 API requests, your chances of succeeding is (1/2)^3 or 1/8 because only 1 request needs to fail in the chain for the entire action to fail. So, as long as you make single API actions you can maximize your success rate :D

        • idunnololz_testOP
          4•2 years ago

          Signing in. Most websites/apps will probably also grab your unread count, and maybe even your subscription feeds.

          Another example is checking your inbox. Lemmy actually has 3 inboxes: mentions, replies and PMs. A lot of websites/apps bundle these three so they will need to check all 3 inboxes via 3 API calls.

      • @[email protected]
        5•2 years ago

        Seems like spamming actions also gets it to work eventually. It’s a pain in the arse though lol. I made some alt accounts on other instances, but I’m lazy and don’t wanna rebuild my subscription feed if I don’t have to, so hopefully it gets fixed at some point.