Hi @itsasylum, thanks for reaching out.
A cURL error 7 often indicates the communication to our servers and back to your site is unable to happen at all. This error number can sometimes be solved from the hosts’ end, so it might be worth checking in with their support channels to see whether they’re able to communicate with noc1.wordfence.com.
wp_remote_post() failing looks like our connection, or the connection back to your site is being stopped by something on the server. Cloudflare can be one such cause, although I’m not certain of this as there’s no detailed log information available in this topic.
If you’re not running Cloudflare on your site, the documentation at this page could help further: https://www.wordfence.com/help/scan/troubleshooting/#scan-process-ended-after-forking
If your site is running Cloudflare, you may need to update your Cloudflare settings to allow your site to connect back to itself. You should be able to do this by going to your Cloudflare control panel.
- Login to Cloudflare
- Go to “Firewall”
- Click the “Firewall Rules” tab
- Click “Create a Firewall rule”
- Name the rule under “Rule Name”
- Set the “Field” under “When incoming requests match…” to “IP Source Address”
- Enter your site’s IP address under “Value”
- At the bottom, under “Then…Choose an action” change “Block” to “Allow”
- Click “Deploy
Once you have added your site to the Cloudflare Whitelist, head back over to your site and attempt another scan. Sometimes, the same process needs to be done for our IP addresses, which can be found here: https://www.wordfence.com/help/advanced/#servers-and-ip-range
Also ensure your visitor IP detection is set up correctly for Cloudflare. Head over to your site and go to Wordfence > All Options > General Wordfence Options > How does Wordfence get IPs. You will most likely need to select “Use the Cloudflare “CF-Connecting-IP” HTTP header to get a visitor IP. Only use if you’re using Cloudflare.”.
Thanks,
Peter.
