Quantcast
Viewing all articles
Browse latest Browse all 33071

ljmac on "[Plugin: Wordfence Security] Call to Wordfence API to resolve IPs failed"

I've just installed Wordfence for the first time and I am getting exact same this error too:

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 => Thu, 04 Sep 2014 07:21:59 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 => Thu, 04 Sep 2014 07:22:00 GMT
content-type => text/html
content-length => 177
connection => close

I can see no reason for this, and nor can my ISP. Besides, if it was being blocked, shouldn't it be a 403 error, not 404?

Everything else appears to be working fine however, except for one thing that I'll open another ticket for.


Viewing all articles
Browse latest Browse all 33071

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>