Support » Plugin: Wordfence Security - Firewall & Malware Scan » WordFence scan fails: “The current scan looks like it has failed.”

  • Resolved bcasey

    (@bcasey)


    I switched hosts to SiteGround and haven’t been able to complete a scan since the move.

    I get the following error:
    “Scan Failed
    The current scan looks like it has failed. Its last status update was 12 mins ago. You may continue to wait in case it resumes or stop and restart the scan. Some sites may need adjustments to run scans reliably.”

    The scan stops when scanning additional files. Before scanning additional files it says of found 7195 files containing 106MB of data. It then consistently stops scanning at 1151 files.

    I have excluded directories I believed to have lots of files or large files like images, cache and it still fails.

    I have increased the memory limit in the WordFence options to 256MB.

    I have tried adding define(‘WORDFENCE_SCAN_FAILURE_THRESHOLD’, 600); to the wp-config file and it just increased the time before I get the error.

    I have also contacted the host and they said they did what they could from their end. They suggested I open a ticket here to see what else I or they could do.

    The page I need help with: [log in to see the link]

Viewing 11 replies - 1 through 11 (of 11 total)
  • Hello @bcasey,

    Ivan Atanasov from SiteGround here. I took some time to check your account associated with the aforementioned domain and found no chat session or support ticket where this was discussed. I suspect you spoke with us over the phone.

    The problem you are describing could be caused by many and different reasons.

    It is possible that the scan is triggering one of our mod_security rules. I saw some ModSecurity errors in our web server logs related to your domain. However, there is no way for me to confirm as I am unable to reproduce the issue without your permission.

    Please post a support ticket from your SiteGround User Area so that we can investigate this for you.

    Plugin Author WFSupport

    (@wfsupport)

    Thanks for adding your thoughts Ivan. Another reason we think SG’s support rocks. 🙂

    We’ve seen Mod_security cause some issues like this before too. Since you guys are working this in your ticket system, would you mind reaching back out in this thread if it is or isn’t the issue?

    For the record, these are the things we usually ask customer’s to do if there is an issue to help us troubleshoot.

    • Kill the existing scan if it is still running (The “Start New Scan” button turns in to a “Stop” button while the scan is running)
    • Go to your Scan > Scan Options and Scheduling page and locate the “Performance Options”
    • Set “Maximum execution time for each scan stage” to 20 on the options page
    • Click to “Save Changes”
    • Go to the Tools > Diagnostics page
    • In the “Debugging Options” section check the circle “Enable debugging mode”
    • Click to “Save Changes”.
    • Start a new scan
    • Copy the last 20 lines from the Log (click the “Show Log” link) or so of the activity log and paste them here

    Reply back with these in case Ivan and SG aren’t able to assist.

    tim

    Thread Starter bcasey

    (@bcasey)

    Thanks to both Ivan and Tim for your responses.

    I have opened a ticket with SiteGround and will see if they can fix the problem.

    I’ll post an update when I hear back.

    • This reply was modified 2 years, 10 months ago by .
    Thread Starter bcasey

    (@bcasey)

    SiteGround responded very quickly to my ticket and resolved the issue.

    Apparently the Maximum execution time for each scan stage was set too high. They adjusted this value and the scan runs properly now.

    Big thanks to SiteGround for resolving it quickly.

    I’ve tried to work with siteground to fix the scans failing issue. They have not helped and I have hit the 3 support ticket limit:

    “You already have 3 or more open tickets for this account, please update the previous tickets for additional issues or comments, or wait for their resolution”

    We have about nine websites in that account with various issues including wordfence scans, infected backups/restores and inaccurate malware/infection reporting from the internal scans. Wordfence scans would really help, especially since they fail at vulnerability and file changes. And their phone number is currently busy from my end. smh

    Plugin Author WFSupport

    (@wfsupport)

    @brent Please create your own topic instead of adding to this one. Have you followed these steps? Do this and paste the last 20 lines of the scan log into your new one.

    Kill the existing scan if it is still running (The “Start New Scan” button turns in to a “Stop” button while the scan is running)
    Go to your Scan > Scan Options and Scheduling page and locate the “Performance Options”
    Set “Maximum execution time for each scan stage” to 20 on the options page
    Click to “Save Changes”
    Go to the Tools > Diagnostics page
    In the “Debugging Options” section check the circle “Enable debugging mode”
    Click to “Save Changes”.
    Start a new scan
    Copy the last 20 lines from the Log (click the “Show Log” link) or so of the activity log and paste them in your support topic.

    Tim

    I also had the same problem of Wordfence scans not completing on Siteground.

    When i moved hosts, the scans ran normally.

    Can you share what you changed the timing to?

    I am running into the same issue.

    Thread Starter bcasey

    (@bcasey)

    My “Maximum execution time for each scan stage” is currently set to 40 and it is working.

    I have the same issue as bcasey, but didn’t manage to find a fix yet. The log stops here:
    [Jul 26 09:54:25] Scanning contents: wp-content/plugins/js_composer/config/wp/shortcode-vc-wp-pages.php (Size: 1.98 KB Mem: 24 MB)
    [Jul 26 09:54:25] Scanning contents: wp-content/plugins/js_composer/config/wp/shortcode-vc-wp-posts.php (Size: 1.86 KB Mem: 24 MB)
    [Jul 26 09:54:25] Scanning contents: wp-content/plugins/js_composer/config/wp/shortcode-vc-wp-recentcomments.php (Size: 1.58 KB Mem: 24 MB)
    [Jul 26 09:54:25] Scanning contents: wp-content/plugins/js_composer/config/wp/shortcode-vc-wp-rss.php (Size: 2.39 KB Mem: 24 MB)
    [Jul 26 09:54:25] Scanning contents: wp-content/plugins/js_composer/config/wp/shortcode-vc-wp-search.php (Size: 1.26 KB Mem: 24 MB)
    [Jul 26 09:54:25] Scanning contents: wp-content/plugins/js_composer/config/wp/shortcode-vc-wp-tagcloud.php (Size: 2.08 KB Mem: 24 MB)
    [Jul 26 09:54:25] Scanning contents: wp-content/plugins/js_composer/config/wp/shortcode-vc-wp-text.php (Size: 1.4 KB Mem: 24 MB)
    [Jul 26 09:54:25] Scanning contents: wp-content/plugins/js_composer/include/autoload/backend-editor-ie.php (Size: 204 B Mem: 24 MB)
    [Jul 26 09:54:25] Scanning contents: wp-content/plugins/js_composer/include/autoload/bc-access-rules-4.8.php (Size: 5.98 KB Mem: 24 MB)
    [Jul 26 09:54:25] Scanning contents: wp-content/plugins/js_composer/include/autoload/bc-multisite-options.php (Size: 757 B Mem: 24 MB)
    [Jul 26 09:54:25] Scanning contents: wp-content/plugins/js_composer/include/autoload/class-vc-settings-presets.php (Size: 9.22 KB Mem: 24 MB)
    [Jul 26 09:54:25] Scanning contents: wp-content/plugins/js_composer/include/autoload/class-vc-vendor-presets.php (Size: 2.48 KB Mem: 24 MB)
    [Jul 26 09:54:25] Scanning contents: wp-content/plugins/js_composer/include/autoload/frontend-editor-ie.php (Size: 133 B Mem: 24 MB)
    [Jul 26 09:54:25] Scanning contents: wp-content/plugins/js_composer/include/autoload/hook-vc-grid.php (Size: 5.84 KB Mem: 24 MB)
    [Jul 26 09:54:25] Scanning contents: wp-content/plugins/js_composer/include/autoload/hook-vc-message.php (Size: 340 B Mem: 24 MB)
    [Jul 26 09:54:25] Scanning contents: wp-content/plugins/js_composer/include/autoload/hook-vc-pie.php (Size: 318 B Mem: 24 MB)
    [Jul 26 09:54:25] Scanning contents: wp-content/plugins/js_composer/include/autoload/hook-vc-progress-bar.php (Size: 358 B Mem: 24 MB)
    [Jul 26 09:54:25] Scanning contents: wp-content/plugins/js_composer/include/autoload/hook-vc-wp-text.php (Size: 339 B Mem: 24 MB)
    [Jul 26 09:54:25] Scanning contents: wp-content/plugins/js_composer/include/autoload/params/hidden.php (Size: 463 B Mem: 24 MB)
    [Jul 26 09:54:25] Scanning contents: wp-content/plugins/js_composer/include/autoload/params/vc_grid_item.php (Size: 6.81 KB Mem: 24 MB

    What shall I do?

    [Sep 30 20:42:29:1569863549.322659:2:info] 9000 files indexed
    [Sep 30 20:42:28:1569863548.834781:2:info] 8500 files indexed
    [Sep 30 20:42:28:1569863548.424542:2:info] 8000 files indexed
    [Sep 30 20:42:27:1569863547.784467:2:info] 7500 files indexed
    [Sep 30 20:42:27:1569863547.452935:2:info] 7000 files indexed
    [Sep 30 20:42:26:1569863546.975037:2:info] 6500 files indexed
    [Sep 30 20:42:26:1569863546.285461:2:info] 6000 files indexed
    [Sep 30 20:42:25:1569863545.393581:2:info] 5500 files indexed
    [Sep 30 20:42:24:1569863544.925941:2:info] 5000 files indexed
    [Sep 30 20:42:24:1569863544.493899:2:info] 4500 files indexed
    [Sep 30 20:42:24:1569863544.025571:2:info] 4000 files indexed
    [Sep 30 20:42:23:1569863543.598768:2:info] 3500 files indexed
    [Sep 30 20:42:23:1569863543.156592:2:info] 3000 files indexed
    [Sep 30 20:42:22:1569863542.811670:2:info] 2500 files indexed
    [Sep 30 20:42:21:1569863541.828529:2:info] 2000 files indexed
    [Sep 30 20:42:21:1569863541.491909:2:info] 1500 files indexed
    [Sep 30 20:42:21:1569863541.255398:2:info] 1000 files indexed
    [Sep 30 20:42:20:1569863540.566641:2:info] 500 files indexed
    [Sep 30 20:42:17:1569863537.635076:2:info] Found 1 themes
    [Sep 30 20:42:17:1569863537.634749:2:info] Getting theme list from WordPress
    [Sep 30 20:42:17:1569863537.634480:2:info] Found 30 plugins
    [Sep 30 20:42:17:1569863537.632885:2:info] Getting plugin list from WordPress
    [Sep 30 20:42:17:1569863537.574340:2:info] Unable to access available disk space information

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘WordFence scan fails: “The current scan looks like it has failed.”’ is closed to new replies.