Critical Error caused by Wordfence

  • Resolved sprockettechweb

    (@sprockettechweb)


    4 years, 12 months ago

    Critical site error caused by Wordfence after update. Disabled plugin and cannot reactivate due to fatal error. Warning: require_once(/home/../wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/init.php): failed to open stream: No such file or directory in /home/../wp-content/plugins/wordfence/wordfence.php on line 66

Viewing 3 replies - 1 through 3 (of 3 total)

  • Hey @sprockettechweb,

    This sounds like a WordPress plugin update that didn’t go well. Can you please try reinstalling Wordfence and let me know if it helps?

    https://www.wordfence.com/help/advanced/remove-or-reset/

    Please let me know how it goes.

    Thanks,

    Gerroald

    Hey @sprockettechweb,

    We haven’t heard back from you in a while, so I’ve gone ahead and marked this thread as resolved.

    Please feel free to open another thread if you’re still having issues with Wordfence.

    Thanks,

    Gerroald

    I have the same issue with a certain site. Anytime I update any plugins. I get a critical error. I then rename the plugins folder and then site loads, rename it back and activate all plugins. Everything works, except for the wordfence plugin. I then need to manually remove and reset the entire wordfence plugin and tables and then it activates wordfence.
    I dont know what the issue is.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Critical Error caused by Wordfence’ is closed to new replies.