/kbin meta

639 readers

1 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 2 years ago

181

Kbin's "Log in" bug is discouraging me from participating (kbin.social)

submitted 1 year ago by [email protected] to c/[email protected]

52 comments fedilink hide all child comments

Every time I try to upvote or boost something, there's a solid 20% chance it'll link to an Error page titled "Log in". That percentage seems to increase the longer I've had my Kbin tab open without refreshing it.

Even more annoyingly, it regularily logs me off completely, forcing me to input my information again. It's especially annoying on mobile since it won't even remember my password for some reason, which was randomly generated, meaning it's a pain to re-enter it every time.

The effect is that it's making me interact with Kbin less and less, I end up just scrolling without upvoting or commenting or anything, and ultimately I also just use the site less overall.

I like it here otherwise, but this one bug is making Kbin a real chore to use, and I know a lot more people have been experiencing it for a while now.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 8 points 1 year ago

How are you managing sessions and load balancing your cluster? From my experience this ‘error after having the tab open a while’ can be caused one of these things

The cookie used for load balancing has expired before the users session cookie, so the user now gets load balanced again, potentially to a node where their session doesn’t exit.
The load balancing is fine, but the server hosting the session has expired the session for some reason (capacity, differently configured expiration time etc….)

Alternatively if you’re using a JWT style access/refresh token pattern, rather than server side sessions, then it’s possible the access token is not being refreshed often enough which results in an expired token being sent to the backend.