#4908 Reverse proxy: infinite internal redirect
phpMyAdmin 4.4.7 gets stuck in an infinite internal redirect and will not load whatsoever. I have the same results in IE and Firefox - using Windows 7 64 bit.
Here are the access logs (nothing shows in the error logs) :
22.33.44.55 - - [17/May/2015:09:17:53 -0700] "GET /phpmyadmin/?SID=&SID HTTP/1.0" 302 - "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko"
22.33.44.55 - - [17/May/2015:09:17:53 -0700] "GET /phpmyadmin/?SID=&SID HTTP/1.0" 302 - "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko"
22.33.44.55 - - [17/May/2015:09:17:53 -0700] "GET /phpmyadmin/?SID=&SID HTTP/1.0" 302 - "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko"
22.33.44.55 - - [17/May/2015:09:17:53 -0700] "GET /phpmyadmin/?SID=&SID HTTP/1.0" 302 - "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko"
22.33.44.55 - - [17/May/2015:09:17:53 -0700] "GET /phpmyadmin/?SID=&SID HTTP/1.0" 302 - "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko"
22.33.44.55 - - [17/May/2015:09:17:53 -0700] "GET /phpmyadmin/?SID=&SID HTTP/1.0" 302 - "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko"
22.33.44.55 - - [17/May/2015:09:17:53 -0700] "GET /phpmyadmin/?SID=&SID HTTP/1.0" 302 - "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko"
I just wanted to add that 4.3.13.1 ran without issues. This issue started after upgrading to the latest version this morning.
Last edit: Qcybb 2015-05-18
Did you install in a new directory, or over an existing one?
I'm using the FreeBSD ports system to update phpMyAdmin - which deletes everything (except my config file) and installs the new copy in the same directory.
Last edit: Qcybb 2015-05-17
I manually installed a fresh copy in a new directory, copied the config.inc.php file over to it, restarted Apache & Nginx and the issue still persists.
I reverted back to version 4.3.13.1 and everything is working again.
Last edit: Qcybb 2015-05-17
Hi Ken,
What are the values you have for configurations $cfg['PmaAbsoluteUri'], $cfg['ForceSSL'] in your configuration file?
$cfg['PmaAbsoluteUri'] = 'https://example.com/phpmyadmin/';
$cfg['ForceSSL'] = true;
Please attach here your config.inc.php, obfuscating sensitive details.
/ * $FreeBSD: ports/databases/phpmyadmin/files/config.inc.php.sample,v 1.3 2006/05/16 06:43:23
* Skeleton configuration file -- this file is empty on a fresh
* installaton of phpmyadmin.
*
* Copy any settings you want to override from
* libraries/config.default.php or use scripts/setup.php to generate a
* basic configuration file
* /
$i=0;
$i++;
$cfg['PmaAbsoluteUri'] = 'https://example.com/phpmyadmin/';
$cfg['Servers'][$i]['host'] = 'localhost';
$cfg['Servers'][$i]['auth_type'] = 'cookie';
$cfg['blowfish_secret'] = 'maskedforsecurityreasons';
$cfg['Servers'][$i]['user'] = 'admin';
$cfg['Servers'][$i]['password'] = 'somepassword';
$cfg['ForceSSL'] = true;
$cfg['NavigationTreeEnableGrouping'] = false;
I had the same problem upon upgrading from 4.4.6.1 to 4.4.7.
Ken,
cannot reproduce the problem with version 4.4.7 and your configuration file. I just changed the PmaAbsoluteUri to match my server's URL. Tested on Linux.
It appears Owen (the comment above you) is having this issue as well.
If it helps, I'm running on FreeBSD 10.1
Yes, but we cannot reproduce the problem (on a Linux server). Now, Owen, please describe your server (FreeBSD too?)
I have reproduced on CentOS 5.11.
$cfg['PmaAbsoluteUri'] = 'https://mydomain.com/database/';
$cfg['ForceSSL'] = true;
It is likely that https://github.com/madhuracj/phpmyadmin/commit/47b734473e964546c5ac6f5324324f8ebf7fc3d4 is the bad commit. Since this is just a single line commit, can any of you confirm whether reverting it fixes your issue?
That fixes the issue for me :)
Not yet. I hope to be able to get to it this afternoon or tomorrow.
I have confirmed that reverting that commit resolves the issue for me.
Ken and Owen, Thanks for testing. However, the commit https://github.com/madhuracj/phpmyadmin/commit/47b734473e964546c5ac6f5324324f8ebf7fc3d4 was used to properly enforce ForceSSL directive.
Now the problem is in PMA_Config::detectHttps() (https://github.com/phpmyadmin/phpmyadmin/blob/master/libraries/Config.class.php#L1611...L1659). This method has a comment saying that it ignores things like reverse proxies. Is this the case for you?
Yes, the detectHttps() function returns "false" when using Nginx as a Reverse Proxy for Apache (which is how my server is setup).
If anyone else would like to test it, you will need to grab the required "PMA_getenv" function from libraries/core.lib.php
Edit : I've attached the PHP script I used for testing.
Last edit: Qcybb 2015-05-27
Yes, I'm also using a reverse proxy in my setup. I'm using Apache instead of nginx though.
Just wondering: if you set ForceSSL to false and access phpMyAdmin with https, is everything all right?
Yes, that solves the issue.
I changed "ForceSSL" to 'false' and everything loads and works now (in HTTPS).
Adding warning in the doc:
https://github.com/phpmyadmin/phpmyadmin/commit/347dc70c18aa4d036821db3ea379068b338952d8