phpMyAdmin 1440 Session Timeout error occurs if you are not active or browsing for more than 1440 seconds.

Here at Bobcares, we have seen several such phpMyAdmin related issues as part of our Server Management Services for web hosts and online service providers.

Today we’ll take a look at the cause for this error and how to fix it.

What causes the phpMyAdmin 1440 Session Timeout error to occur

phpMyAdmin has a default security policy that if you are not active for 1440 seconds then it will throw an error.

This is done for security reasons so that no one will access your computer and make any changes with the databases when you are not around but still have kept the computer on.

However, we can increase the timeout value so that the phpMyAdmin won’t keep on timing out.

For instance, the error appears as below.

How we fix the phpMyAdmin 1440 Session Timeout error

Now, let’s see how our Support Engineers tackle this error for our customers. Here is how we extend the session timeout to a longer period.

Changing cookie time session for the current session

We can do this in phpMyAdmin itself.

For that, we access Settings tab >> click on Features >> General >> Login cookie validity

Changing cookie time session permanently.

Here are the steps to change the session time permanently.

1. Initially, we edit the config.inc.php file in the phpMyAdmin directory.

2. Then we add the below line anywhere in config.inc.php file

$cfg['LoginCookieValidity'] = ;

Here, we replace with the number of seconds that we want to extend.

Also, we can add the below line in /setup/lib/index.lib.php file.

$cf->getValue('LoginCookieValidity') > ;

In case, if there is no .htaccess file for the phpMyAdmin site then we create one and add the following line to override the default PHP session timeout.

php_value session.gc_maxlifetime 

This will increase the timeout session value.

[Need any assistance in fixing phpMyAdmin errors? – We’ll help you]

Conclusion

In short, this error occurs if you are not active or browsing in phpMyAdmin for 1440 seconds. Today, we saw how our Support Engineers provide a solution to this error.