Can Not Log Into PHPMyAdmin or Webmail after upgrading to PHP 7.1.24

[fearworks]

Hi Keith,

Off the top of my head, I can't remember the specifics of what wasn't working and at which point. I remember having various issues with 500 errors dependent on which plugins were activated in WP. I believe it was more something to do with WooCommerce and the lack of security in older PHP versions. Due to WooCommerce handling sensitive information, I suppose they wish to take all precautions.

Fortunately, I have IMAP setup and my mail is forwarding to a client I can access, but I would really like to get access to webmail back at this point. Is there a way for me to delete and reinstall/rebuild PHP Suhosin, returning it to 5.6? If so, it would really help me right now, I think!

Cheers,

Mike

This is a CentOS solution (no doubt different to what other OS users would need, but I see you're on CentOS):

First, downgrade PHP7.x to PHP5.6:

Code:

service httpd stop

yum install php56

yum --enablerepo=remi-php56 install php56-php php56-php-pear php56-php-bcmath php56-php-pecl-jsond-devel php56-php-mysqlnd php56-php-gd php56-php-common php56-php-intl php56-php-cli php56-php php56-php-xml php56-php-pecl-apcu php56-php-pecl-jsond php56-php-pdo php56-php-gmp php56-php-process php56-php-devel php56-php-mbstring

rm /usr/bin/php

press y

ln -s /usr/bin/php56 /usr/bin/php

service httpd restart

Now check PHP version is 5.6 by running:

Code:

php -v

Now add Suhosin back into PHP.

NOTE: When I tried the following code on my test server just now, I got a load of Zend-related errors when I ran the "make install" command. You might get this too, and I'm not sure what the problem is although I can guess it's related to upgrading to PHP 7 and then downgrading again to PHP 5.6 knocking something sideways in the configs or settings files. Try the commands below and see if you get these errors or not - it might just the way I have my PHP 7 test server set up, but let me know. If you get errors like me, the worst case is that you have Sentora running pn PHP 5.6 once again but without Suhosin. And from what you said at the top of this thread, I am pretty sure you had Sentora running on PHP 7.1 without Suhosin, so I don't think you'd be any worse off. But please keep in mind this is certainly not a recommended way of running Sentora, and anything that goes wrong with the security is your fault and no one else's! If it all works without a problem, even better:

Code:

wget -nv -O suhosin.zip https://github.com/sektioneins/suhosin/archive/0.9.38.zip

unzip -q suhosin.zip

cd suhosin-0.9.38

phpize &> /dev/null

./configure &> /dev/null

make &> /dev/null

make install

rm -rf ../suhosin*

reboot

Now see if PHP is running with Suhosin:

Code:

php -v

And remember, the cleanest way to get your server running with PHP 5 and Suhosin correctly installed is to start again from scratch. With all the upgrading you've done, there's no telling what you've re-engineered and that could come back to bite you sometime in the future.

My approach is:

1. Have production servers that run the software as intended, no upgrades done willy-nilly. All real sites and mail accounts etc. run here.

2. Have development/test servers that you can play about with to your heart's content with upgrades, etc. If you break something, you reinstall from an earlier snapshot (I use VMs), or you work out how to fix it and do what you were trying to do properly, then you go and implement ONLY the upgrades and patches and tweaks that you know worked properly on your production servers. No real sites or accounts run on my development/test servers.

In other words, if you're running live mail accounts or websites on your server, DON'T mess with it if you can't afford to lose access to those accounts and sites. Do your PHP upgrading away from your important server until you know EXACTLY what you are doing.

Just my opinion

Keith.