Wordfence Web Application Firewall was unsuccessful

  • duodigital

    (@duodigital)


    4 months, 2 weeks ago

    All my websites that are on a cPanel server now show this error message as an alert. There is no point in updating manually, as the message does not disappear. I saw that other users warned about the same thing, but unfortunately I still couldn’t understand the solution.

    “The last rules update for the Wordfence Web Application Firewall was unsuccessful. The last successful update check was Dec 18, 2023 12:07, so this site may be missing new rules added since then. You may wait for the next automatic attempt at Sep 19, 2024 22:24 or try to Manually Update by clicking the “Manually Refresh Rules” button below the Rules list.”

    In “Diagnostics” the only information that appears in red is this:

    “Connecting back to this site via IPv6 (not required; failure to connect may not be an issue on some sites)
    This diagnostic requires cURL”

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

    (@wfpeter)

    4 months, 2 weeks ago

    Hi @duodigital, sorry to see you’re having an issue with rules updates.

    If the reported last successful retrieval of rules was 9 months ago then it would seem likely a communication issue is occurring between your site and our servers but the IPv6 message isn’t a problem in most cases and just a sign that your host doesn’t assign an IPv6 address to your site. If all the other connectivity is green on your Diagnostics page then that is a positive sign.

    If the manually refresh button isn’t suppressing the message, in your FTP or cPanel file manager, navigate to your wp-content/wflogs folder and check for rules.php. This should show you the last modified date on this file. If it’s 0kb in size or the last updated time matches what Wordfence is saying, you should be able to delete the wflogs folder or its contents entirely, and Wordfence should try to repopulate it within 30 minutes.

    It’s also worth checking that permissions on your WordPress site’s directories are 755, and that the process owner is www-data.

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

    Many thanks,
    Peter.

    Thread Starter duodigital

    (@duodigital)

    4 months, 2 weeks ago

    Thanks, Peter

    I did as you suggested, I deleted the “wflogs” folders and checked the permissions and they were like “755“.

    I will monitor if the alert message appears again

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