outroll / vesta

VESTA Control Panel
http://vestacp.com
GNU General Public License v3.0
2.93k stars 1.02k forks source link

phpmyadmin blank page #1852

Open kammi321 opened 5 years ago

kammi321 commented 5 years ago

Operating System (OS/VERSION):

CentOS 6 64 bit

VestaCP Version:

Latest

Installed Software (what you got with the installer):

php-fpm, nginx, mysql

Issue:

phpmyadmin blank page appearing

I tried this fix: https://github.com/skurudo/phpmyadmin-fixer

And I also tried almost all of the things I could find online but no solution yet.

when I run php /usr/share/phpMyAdmin/index.php from terminal I get https mismatch error and then below it I see html rendered. Kindly help me on this matter. Thanks

noogen commented 5 years ago

I default my system to php7.2 and broke phpMyAdmin too. I gave up, replace it with adminer and go on my happy way.

My problem was phpMyAdmin (4.5.4 - max available on xenial universe ppa - https://launchpad.net/ubuntu/+source/phpmyadmin) on ubuntu 16.04 (xenial) was not compatible with php7.2, example report even at 4.6.6: https://devanswers.co/problem-php-7-2-phpmyadmin-warning-in-librariessql-count/ - you have to go all the way to 4.8 or latest 4.8.5 to get it to work with php7.2

I was also running postgresql and phpPgAdmin hasn't been updated for years. Anyway, stop my rambling now...

To troubleshoot, do you have apache2? if you don't, like you've stated above, then the file you want to at is /etc/nginx/conf.d/phpmyadmin.inc

This file should say that it proxy to php-fpm on port 9000, example:

fastcgi_pass 127.0.0.1:9000;

So lets trace through the entire process:

  1. Your browser hit your-root-domain.com/phpmyadmin, your-root-domain.com nginx config file should have include /etc/nginx/conf.d/phpmyadmin.inc; somewhere.
  2. It then proxy pass to php-fpm port 9000 most likely your problem. This mean your php-fpm should be running and listening on port 9000, whichever version it is. Check /etc/php/{version}/fpm/pool.d/*.conf and weirdly, my www.conf for php7.2 say it listen to a socket listen = /run/php/php7.2-fpm.sock and not port 9000. But then my setup is apache2 so it make sense if Vesta didn't touch it.

Again, make sure your nginx is configured correctly and your php-fpm is running on the correct port or socket file configuration. Start php-fpm if it's not running.

kammi321 commented 5 years ago

I default my system to php7.2 and broke phpMyAdmin too. I gave up, replace it with adminer and go on my happy way.

My problem was phpMyAdmin (4.5.4 - max available on xenial universe ppa - https://launchpad.net/ubuntu/+source/phpmyadmin) on ubuntu 16.04 (xenial) was not compatible with php7.2, example report even at 4.6.6: https://devanswers.co/problem-php-7-2-phpmyadmin-warning-in-librariessql-count/ - you have to go all the way to 4.8 or latest 4.8.5 to get it to work with php7.2

I was also running postgresql and phpPgAdmin hasn't been updated for years. Anyway, stop my rambling now...

To troubleshoot, do you have apache2? if you don't, like you've stated above, then the file you want to at is /etc/nginx/conf.d/phpmyadmin.inc

This file should say that it proxy to php-fpm on port 9000, example:

fastcgi_pass 127.0.0.1:9000;

So lets trace through the entire process:

  1. Your browser hit your-root-domain.com/phpmyadmin, your-root-domain.com nginx config file should have include /etc/nginx/conf.d/phpmyadmin.inc; somewhere.
  2. It then proxy pass to port php-fpm port 9000 most likely your problem. This mean your php-fpm should be running and listening on port 9000, whichever version it is. Check /etc/php/{version}/fpm/pool.d/*.conf and weirdly, my www.conf for php7.2 say it listen to a socket listen = /run/php/php7.2-fpm.sock and not port 9000. But then my is apache2 so it make sense if Vesta didn't touch it.

Again, make sure your nginx is configured correctly and your php-fpm is running on the correct port or socket file configuration. Start php-fpm if it's not running.

Thanks for your reply :). Even I gave up on this and opted for manual command line manipulation instead of using GUI based. And keep in mind, the issue is on a default installation, without any modification from my end.