this post was submitted on 11 Jul 2023
174 points (97.8% liked)

Lemmy.world Support

0 readers
53 users here now

Lemmy.world Support

Welcome to the official Lemmy.world Support communitiy! Post your issues or questions about Lemmy.world here.

This community is for issues related to the Lemmy World instance only. For Lemmy software requests or bug reports, please go to the Lemmy github page.

This community is subject to the rules defined here for lemmy.world.

Support tickets can be created by sending an email to info@mastodon.world



founded 1 year ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] idunnololz_test@lemmy.ml 10 points 1 year ago* (last edited 1 year ago) (1 children)

Login in likely always succeeding. The issue is that whatever app/website you use will make additional API calls afterwards (eg. fetch posts or fetch unread count). Each of those calls have a 1-in-2 chance to succeed and if any of them fail, they all fail and you will be booted out.

Lemmy is now an RNG game. We must prayge to rngesus before making any actions.

[–] generalpotato@lemmy.world 1 points 1 year ago

Schroedinger’s API call.