The scan has failed to start

Hi @innlina, thanks for sending your diagnostic over!

A cURL error 7, which is what I’m seeing in your diagnostic, often indicates the communication to our servers and back to your site is unable to happen at all. This error number can usually 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 or whether this is blocked at their end.

It does look like you’re not using the correct IP detection method for Cloudflare, and may benefit from also whitelisting your own site’s IP in Cloudflare rather than just our server IPs.

Select “Use the Cloudflare “CF-Connecting-IP” HTTP header to get a visitor IP. Only use if you’re using Cloudflare.”.in Wordfence > All Options > General Wordfence Options > How does Wordfence get IPs?

You will need to update your Cloudflare settings to allow your site to connect back to itself, too. 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 Address”
• Enter your site’s IP address under “Value”
• At the bottom, under “Then…Choose an action” change “Block” to “Allow”
• Click “Deploy

Let me know how you get on!

Thanks,

Peter.