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.

  • sheodoxEnglish
    5·
    1 year 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