Call to Wordfence API to resolve IPs failed

  • Resolved micsu

    (@micsu)


    10 years, 2 months ago

    Hi!

    I am having a problem with the connection to Wordfence API with the newest Wordfence Security 5.2.1 plugin.
    I’m using free version of Wordfence and tried to find matching topic here but didn’t get the exact match so I made a new one.

    The connectivity tester returns 404 on both wp_remote_post() tests.

    The Wordfence Whois Lookup returns “Sorry, but no data for that IP or domain was found.” for both wordfence.com and noc1.wordfence.com even though I can connect to both of them from the server on port 80. Is the whois lookup using some different port? Most of the ports are blocked from our firewall.

    On Live Traffic page I get “Wordfence Live Activity: Call to Wordfence API to resolve IPs failed: We received an empty data response from the Wordfence scanning servers when calling the ‘resolve_ips’ function.”

    Are these connection errors due to the free version or is there some problems somewhere else?

    I also have Limit Login Attempts plugin installed because I hadn’t activated wordfence till today and there’s been brute force attacks for some 18 hours now, so I don’t want to disable it if there’s some problems with wordfence.

    Wordfence scan was also failing previously today but it’s working now. The last scan alerted me: * Your DNS records have changed
    I told it that’s fine while I might have done some testing with Wordfence on previous wordpress server and the domain’s IP’s changed after that. Could that be the cause of these issues?

    https://www.ads-software.com/plugins/wordfence/

Viewing 15 replies - 16 through 30 (of 33 total)

  • Tried a different site with a different local cache… the error still exists. I’ll let someone else attempt to assist as I sit back and wait for the fix.

    And it is now working except the error still shows up (even though it is working).

    Thread Starter micsu

    (@micsu)

    Updated the plugin to 5.2.2 a few hours ago and the error doesn’t seem to be occurring anymore.
    It only tells me about scan memory usage and server memory peak now on the Live Traffic page.

    Connectivity tester’s still getting 404 error on wp_remote_post() tests:

    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

    EDIT: While trying to ping noc1.wordfence.com I get host unreachable

    Just want to add my 2 cents, Also getting host unreachable!!

    $ ping noc1.wordfence.com
    PING noc1.wordfence.com (69.46.36.8): 56 data bytes
    92 bytes from 69.46.36.8: Destination Host Unreachable
    Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
    4 5 00 5400 858d 0 0000 36 01 cfde 192.168.5.95 69.46.36.8

    Request timeout for icmp_seq 0
    92 bytes from 69.46.36.8: Destination Host Unreachable
    Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
    4 5 00 5400 54ab 0 0000 36 01 00c1 192.168.5.95 69.46.36.8

    Request timeout for icmp_seq 1
    92 bytes from 69.46.36.8: Destination Host Unreachable
    Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
    4 5 00 5400 d58f 0 0000 36 01 7fdc 192.168.5.95 69.46.36.8

    Request timeout for icmp_seq 2

    — noc1.wordfence.com ping statistics —
    4 packets transmitted, 0 packets received, 100.0% packet loss

    @brad Need your version of Wordfence and host provider. It would be easier if you entered this in a new post so we can track it easier.

    Thanks!

    tim

    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.

    I forgot to mention: I can ping noc1.wordfence.com without any problems.

    Ping should work to that now.

    @ljmac Please enter a separate issue with your details and versions so we can track things.

    Thanks!

    tim

    Hi,

    Also started getting this just today.

    `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 => Mon, 08 Sep 2014 02:16:28 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 => Mon, 08 Sep 2014 02:16:28 GMT
    content-type => text/html
    content-length => 177
    connection => close’

    And also this:

    ‘Scan Engine Error: Wordfence could not start a scan because the cron key does not match the saved key. Saved: b979b5eb61fb154ae08dbb Sent: 218ee8e56737a81244f7478c Current unexploded: 1410131175,b979b5eb61fb154ae08dbb’

    Guys

    Please post each issue in a separate post. The issue here can be attributed to several things and it’s easier to track down each issue if we have a separate ticket for them. Not to mention that the posters here that have already fixed their problem probably don’t want an email every time someone new posts about an issue they already fixed.

    Thanks!

    tim

    Sorry,

    On a google search of the error this looked like the best out of three places to post.

    Regards,
    ANTi-CAP

    Totally fine to post in the forums. We just like making sure the issues are tracked separately. Just go here and post https://www.ads-software.com/support/plugin/wordfence

    Thanks!

    tim

    Hi Tim,

    I’m flat out working right now. I will do this later if I get time and the issue has not resolved it’s self, as I’m sure the issue is your end.

    Regards,
    ANTi-CAP

    Thread Starter micsu

    (@micsu)

    Still having this issue. Ping from that server is not even returning unreachable (doesn’t return anything until timeout).
    Curl connectivity tests pass but “wp_remote_post() test to noc1.wordfence.com failed! Response was: 404 Not Found” is still the same.
    Which port’s that test using?

    Asking the dev team. I’ll let you know what they say. I can confirm that isn’t working on one of my sites either.

    tim

Viewing 15 replies - 16 through 30 (of 33 total)
  • The topic ‘Call to Wordfence API to resolve IPs failed’ is closed to new replies.