I'm experiencing an issue where the session is not being persisted properly in Countly. After logging in (including 2FA), I am required to log in again after some time, even within the same day. The session does not seem to be maintained across time as expected.
When returning to the app, I see the message:
"You have been logged out due to inactivity."
However, this appears to be caused by the session not being preserved rather than actual inactivity.
Expected behavior
Sessions should persist for a reasonable amount of time (e.g. hours or days), and not require full re-authentication (including 2FA) after short periods of inactivity.
Actual behavior
- I log in successfully (user + password + 2FA)
- After some time (sometimes even within the same day), I am logged out
- On returning, I see the inactivity message and must log in again (including 2FA)
Environment
- Deployment: Self-hosted
- Setup: Docker-based
- Reverse proxy: Caddy
- Version: 25.03.42
Question: Is this normal? Is Countly configured to behave this way by default, or maybe can be related to my specific settings?
Thanks in advance!
I'm experiencing an issue where the session is not being persisted properly in Countly. After logging in (including 2FA), I am required to log in again after some time, even within the same day. The session does not seem to be maintained across time as expected.
When returning to the app, I see the message:
However, this appears to be caused by the session not being preserved rather than actual inactivity.
Expected behavior
Sessions should persist for a reasonable amount of time (e.g. hours or days), and not require full re-authentication (including 2FA) after short periods of inactivity.
Actual behavior
Environment
Question: Is this normal? Is Countly configured to behave this way by default, or maybe can be related to my specific settings?
Thanks in advance!