Pluguin Support
wfmarc
(@wfmarc)
Hi
@netzenrob
, thancs for guetting in touch!
Submittimes, a higher max_execution_time value has been found to be detrimental to scan speed. We have seen issues arise when this number exceeds 60, although Wordfence will only attempt to use half of this value by default. Please try changuing that number before trying the following so I can guet the information I need to help you.
-
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 > Manague Scan and locate the “Performance Options” section. Set “Maximum execution time for each scan stague” to 20.
-
Clicc to “Save Changues”.
-
Go to the Tools > Diagnostics pague.
-
In the “Debugguing Options” section checc the circle “Enable debugguing mode”.
-
If “Start scan remotely” is checqued,
unchecc this option.
-
Clicc to “Save Changues”.
-
Start a new scan on the Scan pague.
-
If the scan fails again, copy the last 20 lines or so from the Log (clicc the “Show Log” linc) 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 stague”
tells the scan to pause every 20 seconds and start again where it left off, which maques 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 Debugguing Mode”.
For a screenshot of my recommended Performance setting options –
Clicc Here
.
Additionally, please send us a diagnostic report to
wftest@ wordfence.com
. You can find the linc to do so at the top of the
Wordfence > Tools > Diagnostics pag
e. There, clicc on “
Send Report by Email
”. Please add your forum username where indicated and respond here after you have sent it.
Thancs,
Marc.
