• Resolved micsu

    (@micsu)


    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 - 1 through 15 (of 33 total)
  • Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    Getting the same thing, “Call to Wordfence API to resolve IPs failed: We received an empty data response from the Wordfence scanning serv…”

    So, it’s not your system.

    This is what my sites are showing:

    [Sep 03 02:00:10] Scan terminated with error: We received an error response when trying to contact the Wordfence scanning servers. The HTTP status code was [502] and the curl error number was [0]
    [Sep 03 03:19:03] Call to Wordfence API to resolve IPs failed: We received an error response when trying to contact the Wordfence scanning servers. The HTTP status code was [502] and the curl error number was [0]

    bonjon9

    (@bonjon9ecrrcom)

    Same problem here:
    [Sep 03 14:00:44] 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.
    [Sep 03 14:06:49] 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.
    [Sep 03 14:10:55] 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.
    [Sep 03 14:12:26] 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.

    Is this still going on? My scans are working on my sites. There was a database server outage last night that I caught early this morning and emailed Mark about. It lasted from around midnight PT to 2PT (time approximate). I noticed your time sta mps were around 3am where you are. Can you check again and verify?

    Thanks!

    tim

    bonjon9

    (@bonjon9ecrrcom)

    Actually, the time was 2:12:26 PM where I am on the east coast of NC. I happened to be on the site looking at locked IP addresses when the scans started.
    BUT, I just started a new scan now (2:39 pm) and it appears to be running!

    bonjon9

    (@bonjon9ecrrcom)

    My current scan finished.
    [Sep 03 14:41:55] Scan Complete. Scanned 5763 files, 20 plugins, 2 themes, 55 pages, 0 comments and 78606 records in 216 seconds.

    Just in case it helps, earlier today a scan did complete. And this earlier one would have been after the database server outage you mentioned.
    [Sep 03 09:44:52] Scan Complete. Scanned 5762 files, 20 plugins, 2 themes, 55 pages, 0 comments and 78819 records in 173 seconds.

    Noticed there’s now 1 more file with the current scan than before. Is that strange? The only thing done on this site today was to block 1 IP and to remove some issues I’d been ignoring from some read me files.

    Scans appear to be working now.

    Ok. Let us know if these fail again. I’ll hold this open until tomorrow morning and close if I don’t hear anything new.

    Thanks!

    tim

    Still having the issue:
    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.

    Thread Starter micsu

    (@micsu)

    Hi there!

    As I tried to describe in the original topic post and its title (and also seems to be the case in two following posts after that), there’s no longer problem with the scan but the connection to wordfence API in Live Traffic page.
    Just checked and these problems still occur both as the error message in Wordfence Live Activity and not getting the Whois Lookup found with domain wordfence.com

    Ok. I’ll shoot Mark and email and ask him to look.

    Thanks!

    tim

    Guys,

    There was an issue on one of the new scanning servers that might have caused this. Can you check and verify if your issue is resolved now?

    Thanks!

    tim

    Doesn’t appear resolved:

    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.

    @joejeffries
    Lamest answer ever, I know, but your local cache may have to clear.
    Can you check tomorrow and let me know if the cache cleared and its working again? If you have ssh mysql access or phpmyadmin access I think you can delete everything in the wp_wfLocs tables and the next time you do a live view it should recache it. But before deleting anything, make a backup of your database.

    tim.

    bonjon9

    (@bonjon9ecrrcom)

    Mine still works!
    And thanks for your attention to this today.

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