Liz
(@lizschneider)
Same is true for me, and also on Dreamhost
Same here. Has been broken for over a month now. Getting ready to delete the plugin and go with another as there has been ZERO progress or notification regarding this, aside from “Oh, we thought that was fixed.”
Same here. I’ve noticed it on 2 sites: one on Dreamhost and another on Siteground.
Wordfence is working to solve this issue?!?!?
should we remove the plugin and migration to a new plugin?!?
Please give us a answer!
Thanks.
I have 4 sites on DreamHost and all are experiencing the same issue.
I just chatted with DreamHost support and pointed them to this thread and another similar one. They said:
“Checking those forum messages seeing its happening to other people on Dreamhost, but is an issue with their plugin itself causing this. I’ll see if there’s any server side errors causing this, but for the unable to update rules unfortunately that would need to be troubleshooted by them.”
After checking for server side errors, he wrote:
“I’m not seeing any errors in the logs that reference anything to do with wordfence, checked the wordpress install as well and not giving out any errors.”
So WordFence Support — any response?
BTW: WordPress 5.1.1, WordFence 7.2.4, PHP 7.0
Given the complete lack of attention that this has received, I am left wondering if they have been compromised and simply have no idea what is going on. Since there has been zero response to this, in my opinion the only safe thing to do is to remove the plugin from an abundance of caution until we hear otherwise.
The problem is from Wordfence’s side Not related to the DreamHost
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
Update – Submitted a ticket with DH about this, yesterday. Today, it appears to work again.
Without any chat or submit a ticket to DreamHost, the issue is solved and rules have been updated successfully.
Thanks to those who tried to solve the problem.
Same here. I’ve had to update rules manually but it’s working now.
