20380: Session Timeout (We are sorry but your session has expired)

This issue affects 1 person(s).

ID	Project	Category	View Status	Date Submitted	Last Update
20380	Bug reports	Other	public	2025-12-04 06:11	2025-12-08 10:45

Reporter	sdsAdm1n	Assigned To	c_schmitz
Priority	none	Severity	crash
Status	closed	Resolution	no change required
Product Version	6.12.x

Summary	20380: Session Timeout (We are sorry but your session has expired)
Description	Hi, We are using LimeSurvey Community Edition Version 6.15.11+250909 with SQL server 2016, and IIS. Above message is showing for participants after click to access a token-based survey or click on next. Below are session settings in PHP on the server: session.cookie_httponly = session.cookie_samesite = session.gc_divisor = 1000 session.gc_maxlifetime = 1440 Regards,
Steps To Reproduce	Steps to reproduce (Replace this text with detailed step-by-step instructions on how to reproduce the issue) Expected result (Write here what you expected to happen) Actual result (Write here what happened instead)
Tags	No tags attached.
Attached Files	image.png (99,527 bytes) image.png (99,527 bytes) image-2.png (117,478 bytes)

Bug heat	2
Complete LimeSurvey version number (& build)	LimeSurvey Community Edition Version 6.15.11+250909
I will donate to the project if issue is resolved	No
Browser	Chrome
Database type & version	SQL Server
Server OS (if known)	Windows Server 2019
Webserver software & version (if known)
PHP Version	8.0.30

User List	There are no users monitoring this issue.

Date Modified	Username	Field	Change
2025-12-04 06:11	sdsAdm1n	New Issue
2025-12-04 06:11	sdsAdm1n	File Added: image.png
2025-12-04 06:11	sdsAdm1n	File Added: image-2.png
2025-12-08 10:45	c_schmitz	Assigned To	=> c_schmitz
2025-12-08 10:45	c_schmitz	Status	new => closed
2025-12-08 10:45	c_schmitz	Resolution	open => no change required
2025-12-08 10:45	c_schmitz	Note Added: 83990
2025-12-08 10:45	c_schmitz	Bug heat	0 => 2

c_schmitz 2025-12-08 10:45 administrator ~83990	Please use the forums for general support. This most most likely not a bug but a server configuration issue.