Scan Failed – 2

Hi @donkeyboy33,

Please ensure max_execution_time = 60 is set in php.ini. Wordfence’s scan only ever attempts to use half of this value by default but there have been known problems with higher values than 60 being set due to lengthy waits for timeouts if something has gone wrong.

Have you tried starting scans remotely from the Wordfence > Tools > Diagnostics > Debugging Options section? Does the exact same issue occur? There are other scan troubleshooting tips here: https://www.wordfence.com/help/scan/troubleshooting/

If that doesn’t work, could you do the following steps for me:

• Go to the Wordfence > Tools > Diagnostics page
• In the “Debugging Options” section check the circle “Enable debugging mode”
• Click to “Save Changes”.
• CANCEL any current scan and start a NEW scan
• Copy the last 20 lines from the Log (click the “Show Log” link) or so of the activity log once the scan finishes and paste them in this post.

Wordfence > Tools > Diagnostic > Debugging Screenshot

This will help me see exactly what is happening at the moment the scan fails.

Thanks,
Margaret

Hi guys,

Thank you for the fast respons.
I’ve already tried the dubugging mode, but the last 20 lines are just regular scanning lines, unfortunately. Since i’m not sure whether this information is sensitive, i’ve covered the url.

I’ve also set the max_execution_time to 60 and did another scan, same results. See screenshot.

When trying to use the remote scan i receive another error and the scan doesn’t start:

I’ve also shared the diagnostics report with your team via the ‘E-mail activity report’ function on the scan page.

Thanks!

Erik

Just resended the diagnostics report via Tools > Diagnostics > with my ticketnumber / username.

Hi @donkeyboy33,

Thank you for following up.  We have not yet received diagnostics for this site, so please send those again if you haven’t already.

Please disable the Remote scanning option located in Wordfence > Tools > Diagnostics > Debugging Options.  Once that’s disabled, please try running a Standard Scan in Wordfence > Scan > Scan Options and Scheduling > Basic Scan Type Options. We recommend only using High Sensitivity scanning occasionally or when a compromise is suspected on the site.

Please also test running a scan with Use only IPv4 to start scans enabled, which is located in Wordfence > Scan > Scan Options and Scheduling > Advanced Scan Options.

Thanks,
Margaret

Hi Margaret,

Thanks for the tips, i just tried to resend the diagnostics report, hope you received it well.

I’ve tried the IPv4, but the scan doesn’t start, so i set it back to IPv6. After setting the scan back to ‘basic’ i receive the same result. Except it just ‘stops’ a little earlier in the process. It just waits for 5-20 minutes before i receive an error message.

Thanks Erik

Just ran another scan including the diagnostics and sended it to you. Same results, it simply stops running.

Hi @donkeyboy33,

I did notice that you are on a LiteSpeed server. There have been cases in the past, where LiteSpeed server will kill PHP processes without warning and without error messages. I think this may be what is happening on your site.

You should be able to prevent this behavior by adding one of the following codes to the .htaccess file that is located in the root of your site.

# BEGIN litespeed noabort
<IfModule rewrite_module>
RewriteEngine On
RewriteRule .* - [E=noabort:1]
</IfModule>
# END litespeed noabort

In some cases, depending on the host’s configuration, the above code may not help. An alternate method which may work is this:

# BEGIN litespeed noabort
<IfModule Litespeed>
RewriteEngine On
RewriteRule .* - [E=noabort:1]
</IfModule>
# END litespeed noabort

OR

# BEGIN litespeed noabort
SetEnv noabort 1
# END litespeed noabort

We have a bit more information on this in this page in our docs: https://www.wordfence.com/help/advanced/system-requirements/litespeed/

Thanks,
Margaret