PHP session timeout problem
Hi:
I use a (LAMP based) CMS on one of my sites running off cpanel 31, and it always has problems with session time-outs.
This is a big pain - you can be editing a content item for 10 minutes or more and then when you go to submit it, instead of it being successfully entered, you are greeted with the login screen for the app again - meaning the changes you submitted never made it into the database, and you have to start all over again. And sometimes those timeouts can come 5 minutes after logging on, sometimes 20 minutes.
It seems to have started happening on cpanel 31 a while ago. I've just been living with it - and always rushing when I do my content updates to ensure I get in under the timeout - but I thought I would see if there was a server-side issue with the PHP or Apache config on cpanel 31 that could be changed to boost this timeout period.
On my internal development server, running Apache, PHP, MySQL etc, I can have an admin session of that same CMS open for an hour or more without being logged out, but on cpanel 31, I'd be booted off and forced to login again probably 3 times within an average hour.
This doesn't seem to be something I can alter from within the CMS or the server settings I have access to via cPanel or WHM.
Is there something at the server end on cpanel31 that can be changed to alter this annoying behaviour? My guess is it is a PHP configuration variable that has been set quite restrictively.
I use a (LAMP based) CMS on one of my sites running off cpanel 31, and it always has problems with session time-outs.
This is a big pain - you can be editing a content item for 10 minutes or more and then when you go to submit it, instead of it being successfully entered, you are greeted with the login screen for the app again - meaning the changes you submitted never made it into the database, and you have to start all over again. And sometimes those timeouts can come 5 minutes after logging on, sometimes 20 minutes.
It seems to have started happening on cpanel 31 a while ago. I've just been living with it - and always rushing when I do my content updates to ensure I get in under the timeout - but I thought I would see if there was a server-side issue with the PHP or Apache config on cpanel 31 that could be changed to boost this timeout period.
On my internal development server, running Apache, PHP, MySQL etc, I can have an admin session of that same CMS open for an hour or more without being logged out, but on cpanel 31, I'd be booted off and forced to login again probably 3 times within an average hour.
This doesn't seem to be something I can alter from within the CMS or the server settings I have access to via cPanel or WHM.
Is there something at the server end on cpanel31 that can be changed to alter this annoying behaviour? My guess is it is a PHP configuration variable that has been set quite restrictively.
Comment