Scan Failed too often
-
Most of the time, my scan won’t complete due to the following error
Scan Failed
The current scan looks like it has failed. Its last status update was more than 3 hours ago. You may continue to wait in case it resumes or cancel and restart the scan. Some sites may need adjustments to run scans reliably. Click here for steps you can try.
-
This topic was modified 8 years, 7 months ago by
Anonymous User 15521305.
-
This topic was modified 8 years, 7 months ago by
-
Hi @topsan123,
Please take a look at this article on our documentation platform. It addresses the type of issue you’re experiencing.
Hi, I am experiencing a similar problem. It happened a few months ago, and I fixed it by setting the Maximum execution time for each scan stage to 15, and flushing the cache before running a ‘full scan’. I have the max run time for a scan set at 20,000 seconds.
However, I have now tried setting that variable to as low as 7 and as high as 25 and still the scans don’t finish, it pauses when scanning additional files.
I am with GoDaddy.
The article above recommends editing the wpconfig.php file, but I am somewhat nervous about mesing about in the guts of WordPress. Is there another solution?
The article above recommends editing the wpconfig.php file, but I am somewhat nervous about mesing about in the guts of WordPress.
Create a copy your current wp-config.php file as wp-config-prev.php and then make your changes to the wp-config.php file. If something goes wrong, simply replace the edited file via FTP with your original PREV version.
I don’t know if this is related, but the full scan worked after the release of 6.3.20, so I haven’t had to open up the bonnet of wp-config.
Thanks for letting us know, @wehearthart!
Have you changed anything to your Wordfence configuration? Like disabling specific scan options or deactivating specific plugins?
Could you also check with your hosting provider if there were any recent changes made to the environment (PHP upgrade, allocation of additional resources,…)?@topsan123,
Are you still having the issue? Have you tried to apply the solution suggested here?Thanks for your help. I’m very busy, Sorry for late reply. I’ve tried your first instruction but it’s not working. Here’s some of the scan detailed activity:
[Oct 11 23:15:44] Calling fork() from wordfenceHash with maxExecTime: 20 [Oct 11 23:15:44] Entered fork() [Oct 11 23:15:44] Calling startScan(true) [Oct 11 23:15:44] Got value from wf config maxExecutionTime: 20 [Oct 11 23:15:44] getMaxExecutionTime() returning config value: 20 [Oct 11 23:16:02] Test result of scan start URL fetch: WP_Error::__set_state(array( 'errors' => array ( 'http_request_failed' => array ( 0 => 'cURL error 28: Operation timed out after 18002 milliseconds with 0 bytes received', ), ), 'error_data' => array ( ), )) [Oct 11 23:16:02] Starting cron via proxy at URL http://noc1.wordfence.com/scanp/localhost/Project1/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=1&scanMode=full&cronKey=7bfb0000741800006e710000 [Oct 11 23:16:04] Scan process ended after forking. [Oct 12 16:00:48] Scheduled Wordfence scan starting at Thursday 12th of October 2017 04:00:48 PM [Oct 12 16:00:48] Entering start scan routine [Oct 12 16:56:54] Calling Wordfence API v2.23:https://noc1.wordfence.com/v2.23/?v=4.8.2&s=http%3A%2F%2Flocalhost%2FProject1&k=e8fc76ec1dce4a33cd70fd82e2eb8b0249bbe9dbf5f61d38df83378039884c1538babb4bc7e5b9d3c710e2ff53cc790f71509661f4857387186176f2658c6d6d25146ffe8ca21045514e46c8bc9bcc5b&openssl=268443791&phpv=7.0.10&betaFeed=0&cacheType=disabled&action=ping_api_key [Oct 12 16:56:54] Calling Wordfence API v2.23:https://noc1.wordfence.com/v2.23/?v=4.8.2&s=http%3A%2F%2Flocalhost%2FProject1&k=e8fc76ec1dce4a33cd70fd82e2eb8b0249bbe9dbf5f61d38df83378039884c1538babb4bc7e5b9d3c710e2ff53cc790f71509661f4857387186176f2658c6d6d25146ffe8ca21045514e46c8bc9bcc5b&openssl=268443791&phpv=7.0.10&betaFeed=0&cacheType=disabled&action=ping_api_key [Oct 12 16:56:58] Calling Wordfence API v2.23:https://noc1.wordfence.com/v2.23/?v=4.8.2&s=http%3A%2F%2Flocalhost%2FProject1&k=e8fc76ec1dce4a33cd70fd82e2eb8b0249bbe9dbf5f61d38df83378039884c1538babb4bc7e5b9d3c710e2ff53cc790f71509661f4857387186176f2658c6d6d25146ffe8ca21045514e46c8bc9bcc5b&openssl=268443791&phpv=7.0.10&betaFeed=0&cacheType=disabled&action=get_known_vuln_pattern [Oct 12 16:56:59] Calling Wordfence API v2.23:https://noc1.wordfence.com/v2.23/?v=4.8.2&s=http%3A%2F%2Flocalhost%2FProject1&k=e8fc76ec1dce4a33cd70fd82e2eb8b0249bbe9dbf5f61d38df83378039884c1538babb4bc7e5b9d3c710e2ff53cc790f71509661f4857387186176f2658c6d6d25146ffe8ca21045514e46c8bc9bcc5b&openssl=268443791&phpv=7.0.10&betaFeed=0&cacheType=disabled&action=get_known_vuln_pattern [Oct 12 16:57:02] Calling Wordfence API v2.23:https://noc1.wordfence.com/v2.23/?v=4.8.2&s=http%3A%2F%2Flocalhost%2FProject1&k=e8fc76ec1dce4a33cd70fd82e2eb8b0249bbe9dbf5f61d38df83378039884c1538babb4bc7e5b9d3c710e2ff53cc790f71509661f4857387186176f2658c6d6d25146ffe8ca21045514e46c8bc9bcc5b&openssl=268443791&phpv=7.0.10&betaFeed=0&cacheType=disabled&action=plugin_vulnerability_check [Oct 12 16:57:02] Calling Wordfence API v2.23:https://noc1.wordfence.com/v2.23/?v=4.8.2&s=http%3A%2F%2Flocalhost%2FProject1&k=e8fc76ec1dce4a33cd70fd82e2eb8b0249bbe9dbf5f61d38df83378039884c1538babb4bc7e5b9d3c710e2ff53cc790f71509661f4857387186176f2658c6d6d25146ffe8ca21045514e46c8bc9bcc5b&openssl=268443791&phpv=7.0.10&betaFeed=0&cacheType=disabled&action=plugin_vulnerability_check [Oct 12 16:57:05] Entering start scan routine [Oct 12 16:57:05] Entering start scan routine [Oct 13 16:42:54] Calling Wordfence API v2.23:https://noc1.wordfence.com/v2.23/?v=4.8.2&s=http%3A%2F%2Flocalhost%2FProject1&k=e8fc76ec1dce4a33cd70fd82e2eb8b0249bbe9dbf5f61d38df83378039884c1538babb4bc7e5b9d3c710e2ff53cc790f71509661f4857387186176f2658c6d6d25146ffe8ca21045514e46c8bc9bcc5b&openssl=268443791&phpv=7.0.10&betaFeed=0&cacheType=disabled&action=ping_api_key [Oct 13 16:43:06] Calling Wordfence API v2.23:https://noc1.wordfence.com/v2.23/?v=4.8.2&s=http%3A%2F%2Flocalhost%2FProject1&k=e8fc76ec1dce4a33cd70fd82e2eb8b0249bbe9dbf5f61d38df83378039884c1538babb4bc7e5b9d3c710e2ff53cc790f71509661f4857387186176f2658c6d6d25146ffe8ca21045514e46c8bc9bcc5b&openssl=268443791&phpv=7.0.10&betaFeed=0&cacheType=disabled&action=get_known_vuln_pattern [Oct 13 16:43:24] Calling Wordfence API v2.23:https://noc1.wordfence.com/v2.23/?v=4.8.2&s=http%3A%2F%2Flocalhost%2FProject1&k=e8fc76ec1dce4a33cd70fd82e2eb8b0249bbe9dbf5f61d38df83378039884c1538babb4bc7e5b9d3c710e2ff53cc790f71509661f4857387186176f2658c6d6d25146ffe8ca21045514e46c8bc9bcc5b&openssl=268443791&phpv=7.0.10&betaFeed=0&cacheType=disabled&action=plugin_vulnerability_check [Oct 13 16:43:53] Entering start scan routine [Oct 13 16:43:53] Got value from wf config maxExecutionTime: 20 [Oct 13 16:43:53] getMaxExecutionTime() returning config value: 20 [Oct 13 16:44:11] Test result of scan start URL fetch: WP_Error::__set_state(array( 'errors' => array ( 'http_request_failed' => array ( 0 => 'cURL error 28: Operation timed out after 18003 milliseconds with 0 bytes received', ), ), 'error_data' => array ( ), )) [Oct 13 16:44:11] Starting cron via proxy at URL http://noc1.wordfence.com/scanp/localhost/Project1/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&scanMode=quick&cronKey=42890000428e00004aaf0000 [Oct 13 16:44:12] Scan process ended after forking. [Oct 14 12:31:55] Scan kill request received.I’m going to try your additional instruction and let you know the result. It would be great if I can scan without involving in further setting or adding any files. I haven’t rate the plugin. But I would like to give you 5 stars but the scan is not okay for me. By the way, I’m using WampServer. This might be the cause?
The topic ‘Scan Failed too often’ is closed to new replies.
