My wild guess is that the Wordfence server was overloaded and couldn’t respond to your request.
Is this happening all the time?
The server is not overloaded – it happens every time.
Do you have any other sites with Wordfence?
I think if you turn on debugging, you see the curl command. I’d try to manually run that curl command from the command line on your server to see what happens.
500 errors are pretty vague, so it’s just guesswork for me. Maybe Wordfence knows the reason.
Your not the only one.. .I’ve been seeing this as well for several weeks now. It appears they have not SCALED for the amount of traffic or are under attack.
demoman2k10, it’s been happening on several of my sites for several weeks too.
Hi
We’re sorry you have been experiencing issues with the plugin. Can you check and see if it has been resolved yet? There was a major upgrade this weekend.
(see http://wordpress.org/support/topic/major-wordfence-upgrade-completed-tuesday-sept-2nd)
Thanks!
tim
I have version 5.2.1 and there do not appear to be any upgrades. The problem continues and the error message is completely different than the one you mentioned in your post.
Right but the point I was trying to make was that because of the load on the servers, which was addressed in the update, you might have been getting the error you received. Specifically this part:
We received an error response when trying to contact the Wordfence scanning servers.
I’ll check with Mark to see if there’s anything going on on our side. In the meantime, could you check the server’s error logs for anything specific to Wordfence? I want to be sure there’s not something local blocking the calls. Is everything else working right, except this part on live traffic view (eg: logging blocked login attempts, emailing alerts, etc)?
Thanks!
tim
Ron
(@donniepeters)
I also am experiencing this as posted on my thread about Wordfence Whois
Hi all,
As Tim mentioned we did a major upgrade last night to our infrastructure, so you’re going to have to re-check any issues reported before last night because they are very likely resolved. So @aperson please try a scan, verify that’s working, then view your live traffic page and you should not see that message again.
More info on the upgrade here:
http://www.wordfence.com/blog/2014/09/major-infrastructure-upgrade-completed-and-other-news/
Regards,
Mark.
I continue to have exactly the same problem – it has never gone away. I’ve also made sure I have all of the latest WP updates.
It certainly appears as if others are having exactly the same problem:
http://wordpress.org/support/topic/call-to-wordfence-api-to-resolve-ips-failed-3?replies=24
Just adding my two cents.
“Live Traffic” hasn’t displayed any information at all since the last update.
Just checked. Neither “scan” nor “ip blocking” display any information either.
@apostlepoe Can you post a new thread so we can address your specific issue? Make sure and let me know who your hosting provider and versions of wordfence/wordpress. Thanks!
@aperson Can you run the connectivity check (options page at bottom marked “Click to test connectivity to the Wordfence API servers”
Thanks!
tim
WF Support, this is what happens when I checked connectivity:
Wordfence connectivity tester
DNS lookup for noc1.wordfence.com returns: 69.46.36.8
STARTING CURL http CONNECTION TEST….
Curl connectivity test passed.
STARTING CURL https CONNECTION TEST….
Curl connectivity test passed.
Starting wp_remote_post() test
wp_remote_post() test to noc1.wordfence.com failed! Response was: 404 Not Found
This likely means that your hosting provider is blocking requests to noc1.wordfence.com or has set up a proxy that is not behaving itself.
This additional info may help you diagnose the issue. The response headers we received were:
server => nginx/1.4.6 (Ubuntu)
date => Sun, 07 Sep 2014 17:06:53 GMT
content-type => text/html
content-length => 177
connection => close
Starting wp_remote_post() test
wp_remote_post() test to noc1.wordfence.com failed! Response was: 404 Not Found
This likely means that your hosting provider is blocking requests to noc1.wordfence.com or has set up a proxy that is not behaving itself.
This additional info may help you diagnose the issue. The response headers we received were:
server => nginx/1.4.6 (Ubuntu)
date => Sun, 07 Sep 2014 17:06:53 GMT
content-type => text/html
content-length => 177
connection => close
