View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 18
IDProjectCategoryView StatusDate SubmittedLast Update
17668Bug reportsAccessibilitypublic2021-10-19 12:522024-10-17 09:58
ReportersdsAdm1n Assigned Toollehar  
PrioritynoneSeveritycrash 
Status closedResolutionno change required 
Product Version5.x 
Summary17668: We are sorry but your session has expired
Description

Above message is showing for some participants after click to access a token-based survey.

Steps To Reproduce

Steps to reproduce

Randomly happening for some surveys and for some participants.

Expected result

Displaying the survey form

Actual result

Attached error message

TagsNo tags attached.
Attached Files
session timeout.png (27,596 bytes)   
session timeout.png (27,596 bytes)   
Bug heat18
Complete LimeSurvey version number (& build)Version 5.0.5+210621
I will donate to the project if issue is resolvedNo
BrowserChrome
Database type & versionMS SQL Server 2016
Server OS (if known)Win Server 2019
Webserver software & version (if known)IIS 10
PHP Version7.4

Users monitoring this issue

DenisChenu, medhat

Activities

medhat

medhat

2021-10-20 07:29

reporter   ~66875

Same error appears for us randomly in all browsers: Chrome, firefox & edge.
Sometimes it appears on the first page and other times when clicking "Next" to move to 2nd or 3rd page.
ollehar

ollehar

2021-10-20 10:44

administrator   ~66877

What are you session settings in PHP on the server? How many session files are used at once?
ollehar

ollehar

2021-11-17 13:05

administrator   ~67399

Last edited: 2021-11-17 13:19

You could increase the gc_lifetime to something higher than 24 minutes (1440 seconds).

Some more info:

https://forums.limesurvey.org/forum/can-i-do-this-with-limesurvey/72945-limesurvey-timing-out-can-timeout-setting-be-adjusted

https://stackoverflow.com/questions/36604382/session-expired

https://manual.limesurvey.org/Troubleshooting/en#Error_.22Session_has_expired.22
ollehar

ollehar

2021-11-17 13:20

administrator   ~67400

See links posted.
c_schmitz

c_schmitz

2021-11-17 14:10

administrator   ~67402

Another possibility is that another application on the same webspace is shortening the session timeout.

Anyway, this is not a bug of LimeSurvey but a web server configuration issue, and should be discussed int the forums, instead.
sachin.yadav

sachin.yadav

2023-08-24 07:18

reporter   ~76691

Is the session time out issue also there in the version no. 3.26.5
r0bis

r0bis

2024-10-16 21:57

reporter   ~81256

I am sorry, but such an error is very frustrating for end-users. It diminishes trust in LS and hinders wider adoption. A statement like "this is not a bug of LS but a web configuration issue" helps very little if there is no reference what the "ideal" LS specific configuration should be. I am saying this because in 2018 the timeout message by LS was in fact a problem related to php session file name clashes. Now it may be something else. How could the end users take this issue up with their web hosting admins if there is no clear description of the process. For example the LS manual link that ollehar posted only talks about possibility that Suhosin is running. Nothing about the session mechanism and where the culprits could be.
DenisChenu

DenisChenu

2024-10-17 09:58

developer   ~81257

A statement like "this is not a bug of LS but a web configuration issue" helps very little if there is no reference what the "ideal" LS specific configuration

BUT ! It's because we can not know all condition, there are no ideals !!!

Just session are managed on server, we already have a solution : move session to DB for hard to manage server. There are a bunch of potential issue for session issue.

Use stackoverflow for example : https://stackoverflow.com/search?q=PHP+session+time+out

Issue History

Date Modified Username Field Change
2021-10-19 12:52 sdsAdm1n New Issue
2021-10-19 12:52 sdsAdm1n File Added: session timeout.png
2021-10-20 07:27 medhat Issue Monitored: medhat
2021-10-20 07:27 medhat Bug heat 0 => 2
2021-10-20 07:29 medhat Note Added: 66875
2021-10-20 07:29 medhat Bug heat 2 => 4
2021-10-20 10:44 ollehar Note Added: 66877
2021-10-20 10:44 ollehar Bug heat 4 => 6
2021-10-20 13:21 ollehar Assigned To => ollehar
2021-10-20 13:21 ollehar Status new => feedback
2021-10-21 16:45 sdsAdm1n Bug heat 6 => 8
2021-10-21 16:45 sdsAdm1n Status feedback => assigned
2021-10-25 16:47 DenisChenu Issue Monitored: DenisChenu
2021-10-25 16:47 DenisChenu Bug heat 8 => 10
2021-11-17 13:05 ollehar Note Added: 67399
2021-11-17 13:08 ollehar Note Edited: 67399
2021-11-17 13:19 ollehar Note Edited: 67399
2021-11-17 13:20 ollehar Status assigned => feedback
2021-11-17 13:20 ollehar Note Added: 67400
2021-11-17 14:10 c_schmitz Status feedback => closed
2021-11-17 14:10 c_schmitz Resolution open => no change required
2021-11-17 14:10 c_schmitz Note Added: 67402
2021-11-17 14:10 c_schmitz Bug heat 10 => 12
2023-08-24 07:18 sachin.yadav Note Added: 76691
2023-08-24 07:18 sachin.yadav Bug heat 12 => 14
2024-10-16 21:57 r0bis Note Added: 81256
2024-10-16 21:57 r0bis Bug heat 14 => 16
2024-10-17 09:58 DenisChenu Note Added: 81257
2024-10-17 09:58 DenisChenu Bug heat 16 => 18