• Resolved cassel

    (@cassel)


    I see a warning on my dashboard that says this:

    “The last rules update for the Wordfence Web Application Firewall was unsuccessful. The last successful update check was October 27, 2023 10:55 pm, so this site may be missing new rules added since then. You may wait for the next automatic attempt at November 10, 2023 9:55 pm or try to?Manually Update?by clicking the “Manually Refresh Rules” button below the Rules list.”

    I have tried to follow those instructions, but the notification always comes back. I have Version 7.10.7.

    What can I do? What does it mean?

    The page I need help with: [log in to see the link]

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

    (@wfpeter)

    Hi @cassel, thanks for getting in touch about this.

    If the automatic and manual updates from within the plugin aren’t working, I would first try deleting the wp-content/wflogs folder or its contents via FTP or file manager.

    If that hasn’t helped, ensure you have 755 permissions on your WordPress site’s directories with a process owner of www-data.

    Finally, if you experience persistent problems with the rules.php file, you can bypass this entirely by setting Wordfence to write to the MySQLi storage engine instead of a file: https://www.wordfence.com/help/firewall/mysqli-storage-engine/

    Let me know if you continue to experience issues after trying those, because the connectivity to our servers in your Wordfence > Tools > Diagnostics page may point to a different cause than the rules themselves.

    Thanks,
    Peter.

    Thread Starter cassel

    (@cassel)

    Thanks. Deleting the wp-content/wflogs?folder seems to have done the trick.

    Plugin Support wfpeter

    (@wfpeter)

    Great stuff! Thanks for letting me know. If you have further Wordfence questions in future by all means start up a new topic and we’ll be happy to help out any time.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Wordfence Web Application Firewall was unsuccessful’ is closed to new replies.