Wordfence version 7.11.7 causes 500 error

  • Resolved andrea.vallejo

    (@andreavallejo)


    3 months, 3 weeks ago

    Issues with wordfence 7.11.7 update

    We installed your update on the site https://www.iestheticcem.com today and it caused the site to log a fatal error.

    We have tried restoring backups from a week ago but it keeps taking the site offline. It is currently showing a 500 error.

    This is the response that the server allows

    PHP Fatal error: Failed opening required ‘/home2/iesthfcc/public_html/wordfence-waf.php’ (include_path=’.:/opt/cpanel/ea-php82/root/usr/share/pear’) in Unknown?on?line?0

    We would appreciate it if you could tell us what we can do about this.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @andreavallejo, sorry to see that’s happened for you.

    It’s quite unusual as an update shouldn’t change the location of (or delete) wordfence-waf.php to cause the probable issue here. This is suggesting that auto_prepend_file in the .htaccess or .user.ini files can’t find the path to wordfence-waf.php any more and causing an error when Wordfence tries to run before the site content is loaded. It could be down to an incompleted or failed update but I’m not certain.

    I’d try to remove the auto_prepend_file = ... line either manually by downloading those files or “live” using the file manager provided with your hosting control panel. The site should then load, requiring Wordfence’s firewall to return to “Basic Protection”. Once your site loads again instead of giving you 500 errors, you can re-optimize the firewall using our wizard, which will reflect the new path.

    Thanks,
    Peter.

    Thread Starter andrea.vallejo

    (@andreavallejo)

    Thanks for your help!

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.

Tags