Call to Wordfence API to resolve IPs failed

Hi @891122john, thanks for sending that over.

Without the PHP/server logs in tandem with the timestamps of this issue that might point to the specific error being thrown to cause cURL to error, I can only see the same as you. Broadly speaking, cURL Error 7 often means that the website can’t make the connection to our servers at all. If you are running Cloudflare or another environment that might need further configuration, then we do have some common troubleshooting you can try: https://www.wordfence.com/help/central/connect/#troubleshooting-connection-issues

If none of the above helps, we might be able to tell more about your server environment and most common reasons for connectivity issues on that environment if you also provide your diagnostic. You can also send that to wftest @ wordfence . com directly from the link 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.

I am seeing the same problem – will try the troubleshooting. Started December 10th – Probably my rate limiting is stopping the reply. What’s the call to wp_remote_post() I need to allow? SHowing: <title>Your access to this site has been limited</title> under Connecting to Wordfence servers

• This reply was modified 1 year, 3 months ago by mrcfisher.
• This reply was modified 1 year, 3 months ago by mrcfisher.

Hi wfpeter,

Thanks for your prompt reply.

I have followed all steps in : https://www.wordfence.com/help/central/connect/#troubleshooting-connection-issues

But it looks the same issue still exsit. I already sent the diagnostics report to “[email protected]”. Please keep following up troubleshooting.

Thank you so much.

Thanks @891122john for sending that over!

As the connection back to your site seems to be working and other permissions along with IP detection seem good too, it doesn’t necessarily seem to point to misconfiguration or firewall blocks – that would also often prevent the loopback to your own site.

If Wordfence IPs can be added to any allowlists/whitelists you have, they’re available here: https://www.wordfence.com/help/advanced/#servers-and-ip-addresses

If allowlisting our IPs isn’t an option or doesn’t make any difference, from the diagnostic it looks like the site can’t connect to our server at noc1.wordfence.com.

If you have a shell on the server, try running curl -v https://noc1.wordfence.com/ and send us the output. This may show whether the server’s resolver is getting the wrong IP. If you can’t run it on the server, ask your host or server administrator to try for you.

Thanks again,
Peter.

Hi wfpeter(@wfpeter),

Please refer to the attachment from server supplier. And we did not block any IP in https://www.wordfence.com/help/advanced/#servers-and-ip-addresses , thank you.

Hi @891122john, thanks for doing that.

As the cURL Error 7 persists when Wordfence (and other elements of your site) are removed from the equation, it could be that your host is either intentionally blocking access to our server, or misconfiguration elsewhere on the server. I would reach out to your host’s support to see if they can shed any light on it such as trying to connect to noc1 themselves and troubleshooting, or they may inform you whether this is blocked by design.

Let us know what you find out!
Peter.

Hi wfpeter,

Thanks for your reply, would you please provide your e-mail to contact with our host’s support team?

Thank you.

Hi wfpeter(@wfpeter),

Is there any update for follow-up?

Thank you.

John.