167
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 28 Jul 2023
167 points (100.0% liked)
/kbin meta
8 readers
2 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 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.