Firewall was unsuccessful

  • Resolved rgentle

    (@rgentle)


    5 years, 8 months ago

    I have been getting this message on all my WP sites that use WordFence. Because the rules will not update, and I am annoyed about seeing the warning allthe time, I have disabled the firewall for WordFence on all my sites!

    “The last rules update for the Wordfence Web Application Firewall was unsuccessful. The last successful update check was 19th March 2019 8:32 am, so this site may be missing new rules added since then. You may wait for the next automatic attempt at 2nd April 2019 9:32 am or try to Manually Update by clicking the “Manually Refresh Rules” button below the Rules list.”

Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter rgentle

    (@rgentle)

    I don’t have time for plugins that cause problems that are not being sorted out.

    On Dreamhost?

    Another Dreamhost user airmanalabama9 talked with DH support, and reported back:
    12 hours, 58 minutes ago
    via dreamhost Support
    ” it seems as if our servers cannot reach WordFence’s cloud host as the connection dies at the boarder. A traceroute to noc4.wordfence.com dies at their boarder
    and a trace back to us dies as well. From what we have determined, the
    issue seems to be with WordFence and not us.”

    No solution yet that I’m aware of.

    Thread Starter rgentle

    (@rgentle)

    I’m not aware that I use Dreamhost. I wasn’t sure if this started with accepting the WordFence opt-in of offering to improve the firewall, but it’s only over the past 6 to 8 weeks that the firewall problems have started. Disabling the firewall seems to solve the problem. I’m sure the other WF securities are fine without an additional firewall, for most small websites with limited traffic.

    Same issues here.

    Same here, but has been going on for what seems at least a month or so.

    It has come to our attention that one of our servers where scan signatures and firewall rules come from is being blocked for some reason by a few hosting providers like Dreamhost. If you are not getting your rules updated and are hosted by Dreamhost (or any another hosting provider for that matter) please ask the provider to check and see if noc4.wordfence.com (69.46.36.20) is being blocked. If it is, ask them to unblock it for ports 80 and 443 and let us know if this was the case. If your hosting provider is blocking the IP then they are the only ones that can do anything to fix this.

    Tim

    Thread Starter rgentle

    (@rgentle)

    Thanks. I will pass that information on to my hoster.

    Thread Starter rgentle

    (@rgentle)

    I have asked my host company about noc4.wordfence.com (69.46.36.20) and they say there is no blocking. Some of my sites are on separate hosting with the same company, but I am presuming they are not blocking on those, either.

    Thread Starter rgentle

    (@rgentle)

    I have asked my hosting company about noc4.wordfence.com (69.46.36.20) and they do not block that.

    Update – Submitted a ticket with DH about this, yesterday. Today, it appears to work again.

    Thread Starter rgentle

    (@rgentle)

    I’ll see if my sites update in due course.

    Just a quick update from our side. Dreamhost’s team has identified some other possible blockages that we’re looking into. However, we’ve had reports of the rules now updating on Dreamhost’s servers. Please check your installation of Wordfence to see if you can now update the firewall rules.

    Tim

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