Viewing 13 replies - 1 through 13 (of 13 total)
  • Same here on dreamhost.

    Contact Dreamhost Support. I had the same problem. After submitting a ticket to support I received an email from them saying that they cleared any blocks to the noc4.wordfence.com servers. Pretty cryptic reply, but the error message went away and the rules.php file is updating normally.

    Hi @mattf10 and @ido1990,

    Can you confirm that the rules can be updated now?

    Thanks!

    Dave

    Still doesn’t work.
    I contacted Dreamhost and still waiting for reply.

    @wfdave Just tried again w/ current version of WF. Here’s the error from a site on Dreamhost:

    Rule Update Failed
    No rules were updated. Please verify your website can reach the Wordfence servers.

    • This reply was modified 5 years, 8 months ago by dncreative.

    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 Dreamhost is blocking the IP then they are the only ones that can do anything to fix this.

    Tim

    That’s funny.
    I just got this email back from Dreamhost:

    Sorry to hear of the trouble.

    After looking over the situation, we don’t have any block to remove from
    this side. A traceroute from your server to noc4.wordfence.com shows
    upstream issue with ntt.net. Accordingly, it will be best to contact
    ntt.net for assistance.

    I hope this helps, but let us know if there’s another question or
    problem.

    Thanks!

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    @wfsupport I’ve made sure DreamHost’s security team is aware of this. We’re not blocking it at the moment and I saw that we’ve whitelisted you, however it looks like other places are catching you too.

    traceroute from an affected died at 206.81.80.160 / seattleix.net.

    If you want to email me at [email protected] I can see what we can do on this end, but it looks like more than one place caught you on their automated lists.

    I’m a dreamhost user @wfsupport @ipstenu Mika Epstein and I’m still being blocked as of 4/3/19 7:47 PM
    screenshot

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    It’s not blocked on DreamHost’s end. Something between us and WordFence is dropping the connection. It looks like one of ntt’s paths is breaking, and we can’t really fix that.

    Think of it like ntt being the freeway we drive to get data to and from WordFence. The road we take had a massive traffic jam or accident, and nothing and no one gets through. The problem is that no matter which way we go, we have to pass that one bit.

    I think Ram is working with your team on it now. Hopefully, between the two teams, we’ll be able to sort it out. Thanks, as always Mika, for excellent support.

    Tim

    My site is also on Dreamhost. I was not previously getting the rules update. As of this morning (5th April, 2019) updates are now working again. Whatever was done seems to have fixed the issue.

    Thread Starter mattf10

    (@mattf10)

    Rules are now updating as normally on both my Dreamhost sites. Thanks!

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Firewall rules fail to update Dreamhost’ is closed to new replies.