• Resolved benz1

    (@benz1)


    Are you having issues with scans at the server end today? I’ve run scans on 2 sites on different servers and both have failed with the “Scan Failed – The current scan looks like it has failed” message, even after adding define('WORDFENCE_SCAN_FAILURE_THRESHOLD', 900);
    to my wp-config. It’s also been talked about in at least one Facebook group so it’s not just me having problems.

    Thanks.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Hi @benz1

    In the scan troubleshooting guide, please follow “Adjust the max execution time” and “Adjusting memory settings” sections, as those are the most common reasons for such an issue you have.

    If this didn’t help then please kill any running scan at the moment and make sure “debug mode” is enabled then run a new scan. When it hangs, send a scan activity log to “alaa [at] wordfence [dot] com”. I’ll take a look on this report and let you know my findings.

    Also, you can go to (Wordfence > Tools => Diagnostics) and click on “Send Report by Email” button at the top of the page, send the report to the same email address I mentioned above, this will be helpful too.

    Thanks.

    Thread Starter benz1

    (@benz1)

    Thanks @wfalaa, have sent the emails. I can send the same from other servers if necessary. Thanks.

    Thread Starter benz1

    (@benz1)

    Hi @wfalaa, FYI since sending the logs, I have increase memory limits as per below but it has made no difference:

    define( 'WP_MEMORY_LIMIT', '256M' );
    define( 'WP_MAX_MEMORY_LIMIT', '512M' );

    Hi @benz1

    I got only the diagnostics report email, not the “scan activity log” one, please resend it.

    Meanwhile, you can do the following:
    – Disable these scans (if you have any of them enabled):
    * Scan files outside your WordPress installation
    * Scan images, binary, and other files as if they were executable
    * Enable HIGH SENSITIVITY scanning (may give false positives)

    – Enable this option:
    * Use low resource scanning (reduces server load by lengthening the scan duration)

    – Exclude the caching plugin folder from the scan, check this guide.
    – Disable other installed plugins -temporarily- and run a new scan.

    Thanks.

    Thread Starter benz1

    (@benz1)

    Thanks @wfalla, I did these things but it still hung. I have sent another activity report just now.

    Thanks.

    Hi @benz1

    I’ve checked the diagnostics report and I can see your server is running Litespeed, it could be that Litespeed is aborting the scan silently, I recommend following these steps mentioned here then run a new scan.

    Thanks.

    Thread Starter benz1

    (@benz1)

    Thanks, adding the noabort seems to have solved the problem although it’s a little surprising as other sites on the same server were completing the scan without problem?

    Thanks,
    Benz1

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Scans failing’ is closed to new replies.