PHP 7.2 Keeps getting re-enabled
I have woken up to High Importance alerts everyday for a week now. Every time, one of the issues is PHP 7.2 is enabled. I have deleted every single profile in EasyApache that contains any PHP reference below 8.0. And before doing this, I had a lot of code to change in old WP Themes and non-WordPress code that had to be tested. It was a big chore and I did it. But even more so, I have saved the profile and provisioned it repeatedly (NO PHP below 8.0). I have multiple profiles (some with profane names) that have been enabled.
I have checked every single domain and nothing in WHM references PHP below 8.0. What's worse, is that I had moved to nothign less than PHP 7.4 months ago (maybe a year). Has anyone else had this kind of middle-of-the-night PHP reversion in EasyApache?
At this point, it is beyond annoying. Is this something where I need to open a support ticket or has anyone else faced this and corrected the issue? One of the biggest reasons I have WHM is make server maintenance easier and I am now at the point of spending more time on this EasyApache reversion than I did getting ready for that awesome Elevate script that moved from CentOS 7 to Alma.
Any help, advise or experience with this would be very much appreciated.
-
Did you remove PHP7.2 in EasyApache? 0 -
Hey there! Can you run this command on the server and share the output? rpm -qa | grep ea-php720 -
Did you remove PHP7.2 in EasyApache?
Yes. Multiple times.0 -
Hey there! Can you run this command on the server and share the output?
rpm -qa | grep ea-php72
Whether I run it with sudo or as my normal user, it comes back with nothing. To be sure it wasn't an error I ran it likerpm -qa | grep ea-php
and got all the various php80 and php81 packages. So it would seem there is no php72 to be installed.0 -
Back again this morning! If no one else has experience this or has any fixes I'll open a support ticket. 0 -
Hey there! Can you run this command on the server and share the output?
rpm -qa | grep ea-php72
SO... This morning, I re-run the rpm command above that you had and 72 is back! YESTERDAY: sudo rpm -qa | grep ea-php72 produces nothing TODAY: ea-php72-php-xml-7.2.34-7.9.39.cpanel.x86_64 ea-php72-php-ftp-7.2.34-7.9.39.cpanel.x86_64 ea-php72-php-pdo-7.2.34-7.9.39.cpanel.x86_64 ea-php72-php-mbstring-7.2.34-7.9.39.cpanel.x86_64 ea-php72-php-litespeed-7.2.34-7.9.39.cpanel.x86_64 ea-php72-php-posix-7.2.34-7.9.39.cpanel.x86_64 ea-php72-php-common-7.2.34-7.9.39.cpanel.x86_64 ea-php72-php-mysqlnd-7.2.34-7.9.39.cpanel.x86_64 ea-php72-php-devel-7.2.34-7.9.39.cpanel.x86_64 ea-php72-pear-1.10.12-6.15.4.cpanel.noarch ea-php72-php-cli-7.2.34-7.9.39.cpanel.x86_64 ea-php72-php-iconv-7.2.34-7.9.39.cpanel.x86_64 ea-php72-7.2.34-2.2.43.cpanel.x86_64 ea-php72-runtime-7.2.34-2.2.43.cpanel.x86_640 -
I have the same issue. I run Easy Apache to remove PHP 7.2 then overnight it's back again with a recommendation that PHP 7.2 should be removed. This has been happening for a couple of weeks. 0 -
I have the same issue. I run Easy Apache to remove PHP 7.2 then overnight it's back again with a recommendation that PHP 7.2 should be removed. This has been happening for a couple of weeks.
Did you have PHP7.2 turned on purposefully before now? What's most curious to me is that I had whittled all the PHP down to 7.4 several months ago (maybe a year ago) and haven't had 7.2 on for any site for any reason. I also double-checked and not a single domain / site has anything but PHP 8.0 or 8.1 turned on. Well, if no one has any ideas for how to help, I'll open a support ticket. I'm running AlmaLinux " 8.7 WHM/CPanel " 106.0.13 I ran the CPanel Elevate script to move off of CentOS 7 a few weeks ago.0 -
It's definitely time to make a ticket so our team can check this out. Can you post the ticket number here once you've created that so I can follow along? 0 -
It's definitely time to make a ticket so our team can check this out. Can you post the ticket number here once you've created that so I can follow along?
94522857 " submitted. Granted them access so we'll see what happens.0 -
Thanks for that - I'm following along with that ticket on my end now as well. 0 -
I am please to report PHP 7.2 DID NOT get re-installed last night! 0 -
I uninstalled WordPress Manager and no longer have the problem. Thank you. 0 -
I'm glad that's all it was! 0 -
Oh god thank you for this! - I've been trying to investigate why this was happening for a week! 0 -
Now *this* is the kind of thing that should be a nag banner on the WHM main screen or sent via a daily advisor email. Not linked above, but if you stumble across this thread later on (like I did) this is how you remove the offending software: One thing to note, after you uncheck the entries for Wordpress and click "Update cPAddon Config" make sure you GO BACK and then click "COMPLETELY REMOVE" to, you know, I guess, actually remove it =) 0 -
Surprisingly this is happening still and it 'appears' Wordpress Manager has been long since removed.
Easy to remove 7.2 but it just pops right back up a day or so later. Any new/fresh ideas?
0 -
Lance Hastie - I'm not sure I have a good explanation for this on a modern system. Can you let me know what cPanel version and OS you're using so I can do some testing?
0 -
Thank you and just as I was about to collect the info, I see it was back:
[2025-12-02 14:34:48 +1300] info [xml-api] ---> Package ea-php72.x86_64 7.2.34-3.3.15.cpanel will be erased
cPanel version 130.0.16
OS is AlmaLinux v8.10.0 STANDARD kvm
0 -
Might have stumbled on something. In the cPanel account under 'Applications' is the Wordpress Manager. Clicking on it returns a 404 error.
Under Install CPAddons Site Software was the ticked line:
cPanel, L.L.C. Blogs WordPress 5.4.1
After some time it ended with:
Removed:
wordpress-cpaddon-5.4.1-4.47.noarch
Complete!0 -
So that machine did still have an older WordPress addon running?
0 -
Yes - in a deep dark corner. Overnight result is good - no return of the past issue. Will advise if it changes.
0
Please sign in to leave a comment.
Comments
24 comments