phpmyadmin logs out after 1440 secs

MysqlDjangoPhpmyadminTimeoutLogout

Mysql Problem Overview


In my local development Ubuntu box I use MySQL and phpmyadmin to work with the database.

Whenever phpmyadmin is idle for 1440 secs (24min) the session expires. I lose my place and have to login and start over.

I tried changing the $cfg['LoginCookieValidity'] = 3600 * 9; inside config.inc.php but it still times out in 1440 seconds.

I have restarted everything and cleared the browser cache (Firefox history -> Clear recent history -> Cache -> Everything).

I'm not sure why the increased timeout does not take effect. What am I doing wrong?

Mysql Solutions


Solution 1 - Mysql

Go to PHPMyAdmin in your browser

> Settings > Features > Change the value of Login cookie validity > Saveenter image description here

NOTE: You will have to do this per session.

Solution 2 - Mysql

Add this line to /config.inc.php:

$cfg['LoginCookieValidity'] = 36000;

In /setup/lib/index.lib.php

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

If you don't already have a .htaccess file for your phpMyAdmin site, create one, and add the following line to override the default PHP session timeout:

php_value session.gc_maxlifetime 36000

I would not recommend altering this value in your main php.ini file, as it will allow a ridiculously long session timeout for all your PHP sites.

source: http://www.sitekickr.com/blog/increase-phpmyadmin-timeout/

Solution 3 - Mysql

We can change the cookie time session feature at:

Settings->Features->General->Login cookie validity

I found the answer in here.. No activity within 1440 seconds; please log in again

EDIT:

This solution will work only for the current session, to change permanently do:

open config.inc.php in the root phpMyAdmin directory .

wamp folder: wamp\apps\phpmyadmin{version}\config.inc.php

ubuntu: /etc/phpmyadmin

add this line

$cfg['LoginCookieValidity'] = <your_timeout>;

Example

$cfg['LoginCookieValidity'] = '144000';

Solution 4 - Mysql

You can change the cookie time session feature at phpmyadmin web interface

Settings->Features->General->Login cookie validity

OR

If you want to change the 'login cookie validity' in configuration file, then open the phpmMyAdmin configuration file, config.inc.php in the root directory of PHPMyAdmin.(root directory is usually /etc/phpmyadmin/)

After locating the config.inc.php , search for the line below and set it to the value of seconds you want phpmyadmin to timeout:

$cfg['LoginCookieValidity'] 

or

Add the following:

$cfg[ ' Servers'] [$i] [ ' LoginCookieValidity' ] = <your_new_timeout>;

For example:

$cfg[ ' Servers'] [$i] [ ' LoginCookieValidity' ] = <3600 * 3 >;

The Timeout is set to 3 Hours from the Example above.

session.gc_maxlifetime might limit session validity and if the session is lost, the login cookie is also invalidated. So, we may need to set the session.gc_maxlifetime in php.ini configuration file(file location is /etc/php5 /apache2/php.ini in ubuntu).

session.gc_maxlifetime = 3600 * 3


phpMyAdmin Documentation on LoginCookieValidity

$cfg['LoginCookieValidity']

Type: integer [number of seconds]
Default value: 1440

Define how long a login cookie is valid. Please note that php configuration option session.gc_maxlifetime might limit session validity and if the session is lost, the login cookie is also invalidated. So it is a good idea to set session.gc_maxlifetime at least to the same value of $cfg['LoginCookieValidity'].

NOTE:

  1. If your server crashed and cannot load your phpmyadmin page, check your apache log at /var/log/apache2/error.log. If you got PHP Fatal error: Call to a member function get() on a non-object in /path/to/phpmyadmin/libraries/Header.class.php on line 135, then do a chmod 644 config.inc.php. that should take care of the error.
  2. You will then get another warning: Your PHP parameter session.gc_maxlifetime is lower that cookie validity configured in phpMyAdmin, because of this, your login will expire sooner than configured in phpMyAdmin.. then change the session.gc_maxlifetime as mentioned above.

Solution 5 - Mysql

There seems to be UI for changing phpmyadmin configurations Start apache and click the following link

http://localhost/phpmyadmin/setup/index.php?page=form&formset=Features#tab_Security

Solution 6 - Mysql

Steps for doing this using phpMyAdmin settings without any problem or requirements to change configs in php my.ini or defining .htaccess file:
  1. Goto your phpMyAdmin install path (ex. /usr/share/phpMyAdmin/ on my centos7) and find create_tables.sql in one of its subfolders (phpMyAdmin/sql/create_tables.sql in my 4.4.9 version.) and execute whole file contents on your current phpMyAdmin site from your web browser. This will create a database named phpmyadmin which can keep all your phpMyAdmin options saved permanently.
  2. In phpMyAdmin's config.inc.php (located on /etc/phpMyAdmin/ in my centos7 server) find the commented line $cfg['Servers'][$i]['pmadb'] = 'phpmyadmin'; and uncomment it (Now phpMyAdmin will use that custom database we generated in previous step).
  3. Goto phpMyAdmin from web browser and goto Server >> Settings >> Features >> "Login Cookie Validity" as in picture described by Pavnish and set the desired value. It works now.

References: Niccolas Answer ,PhpMyAdmin Configuration Storage, flashMarks Answer

Solution 7 - Mysql

You will then get another warning: “Your PHP parameter session.gc_maxlifetime is lower that cookie validity configured in phpMyAdmin, because of this, your login will expire sooner than configured in phpMyAdmin.“. That makes sense because php’s session will time out first anyways. So we will need to change /etc/php.ini .

session.gc_maxlifetime = 43200
That’s 12 hours in seconds. 

Restart your apache server and you are done!

source: http://birdchan.com/home/2011/06/06/phpmyadmin-timeout-after-1440-seconds/

this works for me! :)

Solution 8 - Mysql

You should restart apache or httpd, not mysqld

sudo service httpd restart

or

sudo /etc/init.d/apache2 restart

Solution 9 - Mysql

You just Increase the phpMyAdmin Session Timeout, open config.inc.php in the root phpMyAdmin directory and add this line.

from the wamp folder path wamp\apps\phpmyadmin4.0.4\config.inc.php

$cfg['LoginCookieValidity'] = <your_timeout>;

Example

$cfg['LoginCookieValidity'] = '1440';

Note: short cookie lifetime is all well and good for the development server not for your production server.

Solution 10 - Mysql

  1. Login to phpMyAdmin
  2. From the home screen click on "More settings" (middle bottom of screen for me)
  3. Click the "Features" tab/button towards the top of the screen.
  4. For 20 days set the "Login cookie validity" setting to 1728000
  5. Apply.

#php xampp

Solution 11 - Mysql

To set permanently cookie you need to follow some steps

Goto->/etc/phpmyadmin/config.inc.php file

add this code

$cfg['LoginCookieValidity'] = <cookie expiration time in seconds > 

Solution 12 - Mysql

It is not working. The PHP session will expire anyway after 1440 seconds.

Change in PHP.ini this too:

session.gc_maxlifetime = 3600

http://www.phpmyadmin.net/documentation/Documentation.html#config

Also, from PHP.ini:

If you are using the subdirectory option for storing session files

; (see session.save_path above), then garbage collection does not

; happen automatically. You will need to do your own garbage

; collection through a shell script, cron entry, or some other method.

; For example, the following script would is the equivalent of

; setting session.gc_maxlifetime to 1440 (1440 seconds = 24 minutes):

; cd /path/to/sessions; find -cmin +24 | xargs rm

Solution 13 - Mysql

change in php.in file from wampicon/php/php

session.gc_maxlifetime = 1440

to

session.gc_maxlifetime = 43200

Solution 14 - Mysql

If the parameter $cfg['LoginCookieValidity'] is not taking effect in config.inc.php file, try disabling the session.gc_maxlifetime in the php.ini file by putting a semicolon to the left like this:

; 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 = 1440

Or try disabling both $cfg['LoginCookieValidity'] and session.gc_maxlifetime = 1440 by commenting both out.

Then phpMyAdmin should no longer log out when you idle. It works for me on Windows. Don't forget to clear your browser cache and restart your webserver.

Solution 15 - Mysql

steps to change cookie expiration

step 1:Go to settings of Phpmyadmin

step 2:General

step 3:Login cookie validity

step 4:Update 1440 seconds default cookie expiration time with your new value

Solution 16 - Mysql

If you have phpmyadmin configuration storage setup, the settings will be pulled out of your phpmyadmin.pma__userconfig table, and will override anything you have in config.inc.php. In this table, each MYSQL user can be assigned a different set of phpmyadmin settings.

Solution 17 - Mysql

===method 1 with http login===

[php.ini]
session.gc_maxlifetime = 86400

[config.inc.php]

$cfg['Servers'][$i]['auth_type']     = 'http';

===method 2 with cookie login===

[php.ini]

session.gc_maxlifetime = 86400

[config.inc.php]

$cfg['Servers'][$i]['auth_type']     = 'cookie';

$cfg['Servers'][$i]['LoginCookieValidity'] = 86400;

$cfg['Servers'][$i]['pmadb']         = 'phpmyadmin';

$cfg['Servers'][$i]['controluser']   = 'phpmyadmin_pma';

$cfg['Servers'][$i]['controlpass']   = 'nigookike';

$cfg['Servers'][$i]['userconfig'] = 'pma__userconfig'; // there's a lot of other table required for full functionality,
                                                                         // all others can be left out unconfig except this one

[mysql]
-import phpMyAdmin/sql/create_tables.sql

-grant PRIVILEGES to phpmyadmin_pma as below

db/table

phpmyadmin	ALL PRIVILEGES 

mysql/db 	SELECT

mysql/host 	SELECT

mysql/tables_priv 	USAGE

mysql/user 	USAGE


-clear all entries should old one exists

phpmyadmin/pma__userconfig

[webUI]

-clear broswer cookie

-as normal mysql user, access http://mysql/phpmyadmin , at the bottom of page:

	The phpMyAdmin configuration storage is not completely configured, some extended features have been deactivated. [Find out why.]

-near top of the page

	[Create missing phpMyAdmin configuration storage tables.]

-access http://mysql/phpmyadmin > settings > features > Login cookie validity > 86400 > [apply]

-check phpmyadmin/pma__userconfig contain new entries of aforemention mysql user

N.B.

  1. every user has independent setting and [webUI] procedure has to be repeated for each user

  2. if "The phpMyAdmin configuration storage is not completely configured, some extended features have been deactivated. [Find out why.]"

link does not appears on frontpage, go settings > features > warnings > Missing phpMyAdmin configuration storage tables > [refresh] a few times will make it appears

Solution 18 - Mysql

After I tried all suggested methods here and still kept getting logged out, I turned to writing a small usercsript for Tampermonkey as I already have that extension. It is very simple and just sends a request to one of low footprint scripts of PHPMyAdmin once every minute. Here is the code:

// ==UserScript==
// @name         PHPMyAdmin Keep Session Alive
// @namespace    https://www.bitwizeor.io/
// @version      0.1
// @description  No more nasty PHPMyAdmin session expiries
// @match        http://localhost/phpmyadmin/*
// ==/UserScript==

(function() {
    'use strict';
    console.log('PHPMyAdmin Keep Session Alive activated');
    var url;
    window.setInterval(function(){
        url = $("#serverinfo a:eq(1)").prop("href");
        url += '&ajax_request=true&ajax_page_request=true';
        $.getJSON(url);
        console.log('pinging ...');
    }, 60000);
})();

Solution 19 - Mysql

Follow below steps to increase session timeout for phpmyadmin:

Method 1:

  • Login to phpMyAdmin with your root credentials
  • Select Settings from the top in navigation bar
  • Tap on Features
  • Search for Login cookie validity field in General tab
  • Change the value for this field to something greater than 1440 like 36000 or anything higher.

> Make sure whatever value you are entering in Login cookie validity is in seconds

phpmyadmin increase session timeout

Method 2:

Locate your config.inc.php file

For CentOS, Fedora servers:
/etc/phpMyAdmin/config.inc.php

For Ubuntu, Debian servers:
/etc/phpmyadmin/config.inc.php

Search LoginCookieValidity in config.inc.php and increase its value

$cfg['Servers'] [$i] ['LoginCookieValidity'] = 1440;

//change to 
$cfg['Servers'] [$i] ['LoginCookieValidity'] = 36000;

Save the changes to the config.inc.php file and restart your server.

> Increase session.gc_maxlifetime in php.ini to be greater than or equal to the value that you entered in config.inc.php.

Solution 20 - Mysql

I have found the solution and using it successfully for sometime now.

Just install this Addon to your FF browser.

Solution 21 - Mysql

It worked for me after I

  • changed the $cfg['LoginCookieValidity'] in (phpmyadmin folder)/libraries/config.default.php to 999999999.

  • checked the php.ini used by the phpmyadmin by php5 -i | grep php.ini.

  • went to the php.ini file whose path I got from the grep command output and changed the session.gc_maxlifetime value to 999999999.

  • restarted the server. In my case it was sudo service apache2 restart.

Done. Logged in phpmyadmin and checked the cookie validity in Settings -> Features -> General -> Login cookie validity. It was 999999999. Also there was no warning "Your PHP parameter session.gc_maxlifetime is lower that cookie validity ...". The warning showed after I logged in phpmyadmin before I changed the php.ini file.

Check the version of php used by the phpmyadmin. You should change the ini file of the php that is used by the phpmyadmin. I have php5 and php(i.e 7) both installed. But my phpmyadmin uses php5. So I had to search for ini file of php5.

Solution 22 - Mysql

I know this is an old post but I tried every solution I read, including those on this page to no avail, and then I got lucky so I'm posting it here.

I'm running Ubuntu 17.10.

I archived /etc/phpmyadmin/config.inc.php and replaced its content with the content of /usr/share/phpmyadmin/config.sample.inc.php.

I then

 1) Enabled (uncommented) all the options under "Storage database and tables"; 
 2) Included "ini_set('session.gc_maxlifetime', 86400);" underneath the uncommented items; and 
 3) Provided a 32 character sequence for the $cfg['blowfish_secret'] = ''; /* YOU MUST FILL IN THIS FOR COOKIE AUTH! */, which is above the uncommented items.

I saved the file and restarted phpMyAdmin.

I selected Server: localhost -> Settings -> Features and changed the value of "Login cookie validity" to 86400 (24 hours). Note any non default value you specify will cause the background color of this option to become yellow so don't be alarmed by it. The value should be less than or equal to the value you used in config.inc.php.

I saved the settings, exited, and restarted phpMyAdmin.

Finally, all of the messages disappeared. My session stays active as per the settings (all day in this case), and my settings are remembered.

I surely hope this helps someone. It was frustrating for me to deal with and resolve.

Solution 23 - Mysql

drive here your wamp installed then go to wamp then apps then your phpmyadmin version folder then go to libraries then edit config.default.php file e.g

> E:\wamp\apps\phpmyadmin4.6.4\libraries\config.default.php

here you have to change

> $cfg['LoginCookieRecall'] = true;

to

> $cfg['LoginCookieRecall'] = false;

also you can change time of cookie instead to disable cookie recall

> $cfg['LoginCookieValidity'] = 1440;

to

$cfg['LoginCookieValidity'] = anthing grater then 1440 

mine is

 $cfg['LoginCookieValidity'] = 199000;

after changing restart your server enter image description here

also there is another method but it reset when ever we restart our wamp server and here is that method also

login to your phpmyadmin dashbord then go to setting then click on features and in general tab you will see Login cookie validity put anything greater then 14400 but this is valid until next restart of your server.

enter image description here

Solution 24 - Mysql

For Ubuntu 18.04 I just edited the file /usr/share/phpmyadmin/libraries/config.default.php

Change: $cfg['LoginCookieValidity'] = 1440

Solution 25 - Mysql


If you're using phpMyAdmin in a DOCKER container:


  1. Go to your TERMINAL and list your docker containers in order to find out the phpmyadmin one:
$ docker ps

# EXAMPLE OF OUTPUT: 

CONTAINER ID   IMAGE                   COMMAND                  CREATED       STATUS       PORTS                                      NAMES
93dfa1f49775   php:7.4.1-fpm           "docker-php-entrypoi…"   2 weeks ago   Up 2 weeks   9000/tcp                                   docker_localhost_app
36299ca6ce83   nginx:alpine            "/docker-entrypoint.…"   2 weeks ago   Up 2 weeks   0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp   docker_localhost_nginx
c1d8e6ffd28c   phpmyadmin/phpmyadmin   "/docker-entrypoint.…"   2 weeks ago   Up 2 weeks   0.0.0.0:8080->80/tcp                       docker_localhost_myadmin
d75778f88cc6   mysql:5.6               "docker-entrypoint.s…"   2 weeks ago   Up 2 weeks   0.0.0.0:3306->3306/tcp                     docker_localhost_db


  1. Execute bash in the chosen container:
$ docker exec -it docker_localhost_myadmin bash

root@c1d8e6ffd28c:/var/www/html#

>In this case docker_localhost_myadmin is the name of my container.


  1. Install vim editor in order to change the file that have the timeout variable. Execute that:
$ apt update
$ apt upgrade
$ apt install vim


  1. Edit the file config.default.php:
$ vim /var/www/html/libraries/config.default.php


  1. Find out and change the variable $cfg['LoginCookieValidity'] from 1440 to 28800(8 hours):

To find out the variable on vim, press / and type LoginCookieValidity

Before:

  $cfg['LoginCookieValidity'] = 1440 

After:

  $cfg['LoginCookieValidity'] = 28800; 

> NOTE 1: DO NOT set 0(zero) as it will make your phpMyAdmin logout immediately.

> NOTE 2: You may face a message on your phpMyAdmin like: > > Your PHP parameter session.gc_maxlifetime is lower than cookie validity configured in phpMyAdmin, because of this, your login might expire sooner than configured in phpMyAdmin. > >In this case, change the environment variable session.gc_maxlifetime on your docker-compose.yml to - session.gc_maxlifetime=28800 or bigger.


  1. Restart your container:
$ /etc/init.d/apache2 reload


  1. Logout and Login your phpMyAdmin to see the results.

Solution 26 - Mysql

DOCKER containers

PHPMYADMIN NO EXIT (Prevent Docker container phpMyAdmin to automatically logout if no interaction for 1440 seconds)
  1. Run this command in CMD or Git Bash "containers" project folder (with or without 'winpty' at beginning) winpty docker-compose exec phpmyadmin bash

  2. Copy with rename the following file in the current (phpmyadmin container) directory (/var/www/html) --(syntax: 'cp oldfile newfile'):
    cp config.sample.inc.php config.inc.php

  3. Install (if no text editor installed) VIM with:
    apt-get update
    apt-get install vim -y

  4. Edit the file we copied above with vim:
    vim config.inc.php

  5. Add the line bellow by press Insert key in a NEW LINE:
    (86400 = one day, 2500000 = one month)

$cfg['LoginCookieValidity'] = 86400;
  1. Press Esc key
  2. Type :wq then Enter

NOTE: Another instruction from a user above:
--instead of putting the first line in phpmyadmin/config.inc.php put it in a new file in the directory phpmyadmin/conf.d so that it won't be overwritten on an upgrade

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionsandeepView Question on Stackoverflow
Solution 1 - MysqlPavnish YadavView Answer on Stackoverflow
Solution 2 - MysqlPhil LaNasaView Answer on Stackoverflow
Solution 3 - MysqlflashMarkView Answer on Stackoverflow
Solution 4 - MysqlForeeverView Answer on Stackoverflow
Solution 5 - MysqlSmithView Answer on Stackoverflow
Solution 6 - MysqlMojtaba RezaeianView Answer on Stackoverflow
Solution 7 - Mysqlapis17View Answer on Stackoverflow
Solution 8 - Mysql0xmtnView Answer on Stackoverflow
Solution 9 - MysqlRavi DelixanView Answer on Stackoverflow
Solution 10 - Mysqlekta chauhanView Answer on Stackoverflow
Solution 11 - Mysqluser4898825View Answer on Stackoverflow
Solution 12 - Mysqlintec infosysView Answer on Stackoverflow
Solution 13 - Mysqluser3244260View Answer on Stackoverflow
Solution 14 - MysqlAlexView Answer on Stackoverflow
Solution 15 - MysqlNaresh DudhatView Answer on Stackoverflow
Solution 16 - MysqlNicolas ConnaultView Answer on Stackoverflow
Solution 17 - MysqlDil LeeView Answer on Stackoverflow
Solution 18 - MysqlMajid FouladpourView Answer on Stackoverflow
Solution 19 - MysqlAnkit JindalView Answer on Stackoverflow
Solution 20 - MysqlsandeepView Answer on Stackoverflow
Solution 21 - MysqlRakesh Ranjan DasView Answer on Stackoverflow
Solution 22 - MysqlNickView Answer on Stackoverflow
Solution 23 - MysqlDarkcoderView Answer on Stackoverflow
Solution 24 - MysqlAhmed IsmailView Answer on Stackoverflow
Solution 25 - MysqlClaudio GuirunasView Answer on Stackoverflow
Solution 26 - MysqlLucianDexView Answer on Stackoverflow