Do I need to make changes after switching from suPHP to PHP-FPM

Hi @chcw, thanks for reaching out to us about this.

The handler shouldn’t break things as Wordfence was successfully installed and functioning already on PHP and the server environment. I’ve seen evidence to suggest there could be a requirement to re-optimize the firewall, but if you notice no detrimental effects to your current installation (scans/updates) this doesn’t appear to be mandatory.

Let me know if you find anything as our development team could shed more light on things if required.

Thanks,

Peter.

Thank you. If I want to re-optimize the firewall, how to do so?

Hi,

If I want to re-optimize the firewall, how to do so?

Thank you very much.

Hi @chcw,

If everything is working OK after your change, it shouldn’t be necessary.

However, if you want to re-optimize the firewall, you can find a “remove extended protection” button by visiting Wordfence > Firewall > Manage WAF. You will need to follow instructions to remove your auto_prepend_file directive before this process can delete wordfence-waf.php. Make sure to take a backup of your .htaccess and .user.ini files before taking this step in case they need to be reinstated.

Extended protection is the facility offered when the firewall is optimized. After removal, you’ll be on basic protection until you select the optimize firewall option again from the Wordfence dashboard.

Please refer to our documentation for complete information and instructions: https://www.wordfence.com/help/firewall/optimizing-the-firewall/#removing-the-optimization

There are also instructions on the above page to help you optimize the firewall again.

Thanks,

Peter.

Thank you.

No worries @chcw, if you have any further Wordfence questions in future please don’t hesitate to start a new topic and we’ll be glad to help out any time!