error] Call to Wordfence API to resolve IPs failed

  • Resolved John

    (@shadowcrown)


    2 years, 8 months ago

    Hi

    I’m in the process of cleaning up my current site installation readying to move to a VPS.

    My first attempt collapsed due to a catastrophic server 403 Forbidden error, which was resolved through updating the apache html version permissions. However, while this is the case, I’m still experiencing a number of internal 403 errors — “Update failed: <!DOCTYPE HTML PUBLIC “-//IETF//DTD HTML 2.0//EN”> 403 Forbidden”

    Ok, how’s this is relevant… well, before moving my site again, which I know does work besides the internal errors above, I decided to run some Wordfence checks where my site currently sits. I opened up the WordFence Logs.

    Wordfence Full Activity Log:
    While most of the results seem promising, I found this in red —
    “error] Call to Wordfence API to resolve IPs failed: There was an error connecting to the Wordfence scanning servers: cURL error 6: getaddrinfo() thread failed to start”

    I have had a look through the net for an answer and found the one below through this forum. I have taken the liberty to run the checks, bearing in mind I don’t have anything installed to run “Trace Route” or, “tracert”.

    dig noc1.wordfence.com – 46 IN A 44.239.130.172
    nslookup noc1.wordfence.com – Address: 44.239.130.172
    host noc1.wordfence.com – Address: 44.239.130.172
    getent hosts noc1.wordfence.com – Address: 44.239.130.172
    ping noc1.wordfence.com – 56(84) bytes of data (frozen)

    “You should then see the IP 69.46.36.28 returned.”

    As you can see the address is different from the one provided.

    Any ideas, or do I not need to worry!?

    My Appreciation in advance. John

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter John

    (@shadowcrown)

    Update: I also have this in site health.
    The scheduled event, wordfence_completeCoreUpdateNotification, failed to run

    everything else does!?

    Plugin Support wfpeter

    (@wfpeter)

    Hi @shadowcrown, thanks for the detailed description of what you’ve been seeing.

    Often, the failure of cron jobs like wordfence_completeCoreUpdateNotification comes with a list of other failed/overdue jobs in the Wordfence > Tools > Diagnostics page, even for other plugins and WordPress core functionality, because the site is having trouble making outbound connections and back to itself. This is further confirmed by the cURL error 6, which rather than being a “blocked” type message, it’s stating its failure to reach the intended destination altogether.

    Our IP addresses that sometimes need to be allowed in load balancers, server-side firewalls etc. are available for your reference in our help documentation: https://www.wordfence.com/help/advanced/#servers-and-ip-addresses

    My first instinct, unless you’re running on Cloudflare or LiteSpeed where whitelisting our IPs or adding noabort code could help, would be to see if your host can see a fundamental reason why your site would be having trouble making any outbound connections. They may not, but it’s worth ruling out as they can check routes and connectivity from their end.

    You could also send a diagnostic report to wftest @ wordfence . com so we can take a closer look at your configuration. You can find the link to do so at the top of the Wordfence > Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    NOTE: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email

    Thanks,

    Peter.

    Thread Starter John

    (@shadowcrown)

    Hi, Peter

    Appreciated. I’ll look into that shortly and have a dig around. I will also need to consider both the setup and impact of migration. So the information may also be helpful there too.

    I’ll report once done ??

    Thanks, John

    Thread Starter John

    (@shadowcrown)

    How do,

    Everything is now a green light in Site Health! however, there does seem to be a deeper/hidden issue that needs addressing.

    So I’ll close this one now and open another… it’s a weird one!

    KR, John

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