Scan stage failed

Hi @barryseal, thanks for the description of your issue.

What steps have you already tried from the “Click here for steps you can try” link in the notice? It’d just be good to know if anything I may suggest on face value with this issue already hasn’t helped.

If all checks in Wordfence > Tools > Diagnostics > Connectivity are green and “OK”, there could be issues with max_execution_time or the Wordfence settings around scan stage execution times being too long, but I suspect there may be an issue with connectivity caused by a CDN such as Cloudflare, or other load balancer/firewall/proxy depending on your host. Litespeed can experience scan timeout issues unless a configuration change is made, too.

Let us know what you see in your diagnostic,
Peter.

Hi @wfpeter,

Thank you for your response.

To answer your question on what steps I tried after receiving the error, I simply contacted my hosting provider about the issue, who looked at my Wordfence area remotely and concluded there was no issue.

However, upon reading your email and checking Wordfence > Tools > Diagnostics > Connectivity, I noticed the following error: “wp_remote_post() test back to this server failed! Response was: cURL error 7:”

I’m not sure why my hosting provider did not find an issue. Can you help me fix this issue?

Thank you for your help!

@barryseal

Sure @barryseal,

I’ll take a look at your diagnostic rather than ask too many questions around the circumstances of the connection failure you’re seeing to see if I can help you out.

If you could send a diagnostic to wftest @ wordfence . com directly from the link at the top of the Wordfence > Tools > Diagnostics page, that may help. 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 again,
Peter.

Thank you @wfpeter. I have sent you a report via the Wordfence > Tools > Diagnostics page as you indicated in your previous message.

I look forward to your thoughts on how to fix the issue.

Thank you!

@barryseal