Wordfence causing error after server updates?
-
Tonight, I decided to take the time to update to EasyApache 4 on one of our cPanel servers. In doing so, I was greeted with an error stating MySQL wasn’t installed all of a sudden, meaning WordPress could not run. I was eventually able to find that this block of code from when activating the Wordfence firewall was blocking access:
<IfModule mod_suphp.c> suPHP_ConfigPath '/home/xxxxxxx/public_html' </IfModule>
Commenting out the middle line would bring the site back online. Unfortunately, this means I would have to do this on every site on the server. I reverted since I did not anticipate that scope of work to be needed, however I was wondering if there is a way to prevent this (only a couple of the sites have a custom php.ini where the error would make sense, the others do not) and if I can expect this same behavior on new installations following.
- The topic ‘Wordfence causing error after server updates?’ is closed to new replies.