Firewall Rules updating failed- Dreamhost

Hi @airmanalabama9,

I thought the newest update would have fixed this, but it appears to have not worked.

Can you open a premium ticket over on https://support.wordfence.com ?

Dave

just did

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.”

Thank you for that update! I wasn’t really sure what I needed to ask Dreamhost regarding it, so that’s super appreciated.

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

these denials from both sides is ridiculous, I thought Wordfence and Dreamhost were working it out as stated in a wordfence support ticket reply, The customers can’t control the back-end of either dreamhost or wordfence servers.

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

saw this posted on another like this one;
Ipstenu (Mika Epstein) (@ipstenu)
?????? Plugin Review Team Rep

4 hours, 20 minutes ago
@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.

We are working on it. Unfortunately, changes don’t happen in the blink of an eye. A member of our team is working with the team at DH.

Tim

Hi, I work for DreamHost. I understand it’s confusing, but we absolutely ARE NOT blaming WordFence, nor are they blaming us.

I personally have verified that DreamHost IS NOT blocking WordFence. And I know WF isn’t blocking us. The connect dies midway, which means something BETWEEN us is the problem, that’s incredibly hard to fix because it’s not under either of our control.

Just a quick update from our side. We’ve had reports of the rules now updating on Dreamhost’s servers. Please check your installation of Wordfence to se if you can now update the firewall rules.

Tim