Scan failed to start

Hello @spiraledgeuk and thanks for reaching out to us!

If your site is protected by Cloudflare, you may need to update your Cloudflare settings to allow your site to connect back to itself. You will have to add your server IP into the Cloudflare Allowlist. 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

Once you have added your site to the Cloudflare Whitelist, head back over to your site and attempt another scan.

Let me know if this helps and if you have any questions!

Thanks again!

Hi @wfadam thanks for this, so I added a rule for the site’s IP address and the scan still fails to start, both with and without start scan remotely set (although I can see the IP being allowed in the Cloudflare logs). Is a rule also needed for the WF IP range perhaps? Or other suggestions welcome!

Can you send a diagnostic report to wftest @ wordfence . com? 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.

I want to see if the IP detection is working correctly.

Thanks again!

Ok thanks, I have done that, I also sent the scan logs.

Can you see anything?

It is now working again. For anyone else encountering this issue, a combination of whitelisting IPs (Cloudflare and site) and clearing cache on both the hosting and Cloudflare eventually solved it, but I am not sure which of these actually did the trick.

Thanks for letting us know what resolved it!

I was just typing a reply for you and then noticed you sent that previous message.

Thanks again!