Users are reporting unusually short session lengths in Discourse, despite a configured maximum session age of 1440 hours (60 days). finn-matti initially reported the issue, noting frequent login requirements on a PikaPods hosted instance using a Bitnami image. PikaPods support directed them to seek assistance from the Discourse community, as they run the image unmodified. pfaffman suggests the issue might stem from the non-official installation method and points towards Redis as a possible cause. agungor confirms experiencing the same problem on an official Docker installation, with sessions expiring much sooner than the 1440-hour setting, requiring multiple logins per week.
We have a small discourse instance that experiences a weird problem: Even though our session length is 1440 hours (or 60 days) me and our users have to login very frequently, often more than once per day.
The forum is hosted on PikaPods which uses the bitnami image. PikaPods support said that they advice me to ask here for further assistance because they just run the image as is (unmodified).
Does anybody have an idea what’s going on? It seems like it should work as configured…
You’ll need to check with PikaPods or Bitnami. Only official installs are supported here. Sounds like a problem with Redis
We are having a similar problem, too. Max session age set to 1440, but sessions have lately become much shorter than that. We are often having to sign in multiple times a week. Our instance is using the official Docker install.
