Scan stopped

Hi @tsfm,

Sometimes the module does need to be individually checked after choosing your PHP version in cPanel (as an example), but certainly shouldn’t be causing a problem if it is. I can think of a past case where cURL was disabled by the host, so the setting at the site would always be overridden. You may need to speak to your hosting provider about whether this is the case.

If your host doesn’t see an issue with your configuration, could I take a look at the diagnostics output myself please? You can send them to wftest @ wordfence . com. The link is at the top of the Wordfence > Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

NOTE: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email

Thanks,

Peter.

Hi @tsfm,

Sorry for any delay, I wasn’t looking out for the diagnostic as this topic hadn’t been updated since my reply. I’ve now seen we have a diagnostic from you and have checked it.

cURL support appears to be turned off, which could certainly be an issue. This can often be turned on either by your host, or as a checkbox (among other PHP modules) in your hosting control panel where your PHP version is selected.

Aside from this, I notice your max_execution_time value is 300, which has been found to be detrimental to scan speed. We have seen issues arise when this number is above 60, so I would suggest altering this before going further.

You can then try the following:

• Stop the existing scan if it is still running (The “Start New Scan” button turns into a “Stop” button while the scan is running).
• Go to your Wordfence > Scan > Manage Scan and locate the “Performance Options” section. Set “Maximum execution time for each scan stage” to 20.
• Click to “Save Changes”.
• Go to the Tools > Diagnostics page.
• In the “Debugging Options” section check the circle “Enable debugging mode”.
• If “Start scan remotely” is checked, uncheck this option.
• Click to “Save Changes”.
• Start a new scan on the Scan page.
• If the scan fails again, copy the last 20 lines or so from the Log (click the “Show Log” link) once the scan finishes and paste them in the post.

On some sites, this will correct the issue. Adding “20” for the “Maximum execution time for each scan stage” tells the scan to pause every 20 seconds and start again where it left off, which makes the scan more performance-friendly for some servers. If this fixes the issue and scans run again, you can leave all the settings above except for “Enable Debugging Mode”.

For a screenshot of my recommended Performance setting options – Click Here.

Thanks again,

Peter.