[BUG] Session timeout every 30min or so

[ghost]

Describe the bug
I get disconnected from the site every half an hour or so, event though the sessionn timeout is set to 8h
public $sessionExpiration = 28800; //How many seconds after inactivity should we logout? 28800seconds = 8hours

To Reproduce
Steps to reproduce the behavior:

1. Have a page open and go grab a coffee
2. Come back
3. You're now disconnected but it doesnt show it. So if you try stopping a timer, it will stop it, showing the login page over the notification, but it wont actually register the change in DB.

Leantime Version
2.1.8

Server
Apache2

PHP / MySQL Version
PHP 7.4
MariaDB10

Additional context
Firefox, no adblock on the domain

[nickian]

I'm noticing the same behavior. The app does not seem to respect the session expiration setting in the configuration.

[ghost]

The most disturbing part was that it showed the entire "login" page into the notification block. I dont have a screenshot unfortunatly as i didnt keep using it afterward.

[marcelfolaron]

I have a hard time reproducing this. I stay logged in and the cookie seems to be fine.
Can you take a look and check if the cookie expiration date/time is correct? I noticed that only Firefox users encountered that problem, so I am wondering if there is a php setting or so that needs to be set.

[martin-korf]

You can try change the session.gc_maxlifetime in the php.ini . It seems that this solved it for me

; After this number of seconds, stored data will be seen as 'garbage' and
; cleaned up by the garbage collection process.
; http://php.net/session.gc-maxlifetime
session.gc_maxlifetime = 86400

[marcelfolaron]

Thank you for the pointer. I didn’t realize the default was set to 1440 which is 24 min. I’ll add that to the list of ini_sets we are executing. Keep in mind the docs though: - Note: If different scripts have different values of session.gc_maxlifetime but share the same place for storing the session data then the script with the minimum value will be cleaning the data. In this case, use this directive together with session.save_path.

…

On Thu, May 5, 2022 at 6:20 AM martin-korf ***@***.***> wrote: You can try change the session.gc_maxlifetime in the php.ini . It seems that this solved it for me ; After this number of seconds, stored data will be seen as 'garbage' and ; cleaned up by the garbage collection process. ; http://php.net/session.gc-maxlifetime session.gc_maxlifetime = 86400 — Reply to this email directly, view it on GitHub <#557 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALG4EFRFIHXYQHA76DHOHM3VIOOFLANCNFSM5LMXFW2Q> . You are receiving this because you commented.Message ID: ***@***.***>