Scan keeps failing “Scan stop request received.”

Also, the scans keep resulting in 521 server errors.

Hi @rdrup, thanks for seeking out our help on this.

Traditionally, issues with scans on Cloudflare have been solved by specifically just entering 69.46.36.0/24 and 54.68.32.247 (if you’re using Wordfence Central) into your allowlist in Cloudflare’s settings. You shouldn’t need to allow our scan IPs in Wordfence itself.

The 521 error in Cloudflare is related to blocking, although not specific to Wordfence, so makes sense that it’d be showing if this process isn’t completing successfully. I have seen a case before where the user had Cloudflare IPs that were blocked in the server blocklist, so please give this a check.

If you’re no further forward after that, can you send me 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.

Note: For the fastest response time, please make sure and add any information or questions directly to this topic and not the email address above unless asked.

Thanks,

Peter.

Hi Peter

Thanks for your reply.

We’ve added the above 54.68.32.247 ip now and also checked the blocked list for any cloudflare IPs but none where blocked.

However, it seems the scan problem still persists. It also seems intermittent across our websites too, which is weird.

I’ve just sent you a diagnostic report from one of our sites.

I successfully ran a scan on this website a couple of days ago, Monday. So it’s strange that the scan stop requests are happening today on this site now.

Thanks for your help, it’s much appreciated.

Hi @rdrup,

Now I’ve seen your diagnostic, it seems to be linked to a cURL error that has occurred a number of times where Cloudflare can’t connect to your site, so Dreamhost and Cloudflare will need to fix the problem if you can contact their support channels.

I would just like to issue a correction (for you and anybody ever referencing this ticket) to our IP range that is 69.46.36.0/27 rather than /24, but that is not the issue at hand here.

Thanks,

Peter.