Replies: 0
Hello,
I am using WordFence as a security plugin in my main domain and in 2 subdomains from around 1 year without any issues.
However, after 1 February 2019, WordFence Security Scans aren’t happening in all of the websites, saying —
Scan Failed
The scan has failed to start. This is often because the site either cannot make outbound requests or is blocked from connecting to itself. Click here for steps you can try.
I go through all the troubleshooting method recommend by the WordFence and go through those below points —
1) Troubleshooting using below links
https://www.wordfence.com/help/scan/troubleshooting/#if-your-scans-arent-starting
https://www.wordfence.com/help/tools/diagnostics/#debug-mode
https://www.wordfence.com/help/scan/options/#max-execution
2) Contacted my Hosting Provider and Cloudflare to see if they are blocking WordFence Scan Server IP address range?
Turnout they aren’t blocking WordFence Scan Server IP address range. And I also allowed that IP range through Cloudflare Firewall.
3) Changed Max execution time according to the documents. And turned on Debug Mode and found these log —
[Feb 07 13:07:00] Ajax request received to start scan.
[Feb 07 13:07:00] Entering start scan routine
[Feb 07 13:07:00] Got value from wf config maxExecutionTime: 0
[Feb 07 13:07:00] Got max_execution_time value from ini: 300
[Feb 07 13:07:00] ini value of 300 is higher than value for WORDFENCE_SCAN_MAX_INI_EXECUTION_TIME (90), reducing
[Feb 07 13:07:00] getMaxExecutionTime() returning half ini value: 45
[Feb 07 13:07:00] Starting cron via proxy at URL https://noc1.wordfence.com/scanp/*****.******.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&scanMode=custom&cronKey=******0d744864715296f0******
[Feb 07 13:07:01] Scan process ended after forking.
***Removed few info in the log
Please help me to solve this issue.
Thanks…