Hi there – I have just read through all the posts because I couldn’t remember what solved it. It appears that it suddenly started working again at the 123-reg sites so they must have done something at their end. I still have lots of 123-reg sites, and all scans currently running fine.
Thread Starter
mkcn
(@mkcn)
Hi @singingcyclist – that’s interesting that your scans are running fine, thanks for letting me know that.
I have now come across the following suggested settings is in a separate topic that you posted on:
Maximum execution time for each scan stage: 15
Time limit that a scan can run in seconds: 0
Did you try this?
Looks like that’ll be the next thing I try to see if a “standard” scan will work within the allocated 3 minutes. All my “standard” scans are switching to “limited” overnight.
I changed so many things, its hard to remember! But I have just looked at one site and its not set to that anymore.. I think the host were changing my settings overnight anyway. One thing I do remember doing is changing them all to limited . Good luck!
Hey @mkcn,
Here are a few troubleshooting steps you can try that might help.
Go to Wordfence “Scan Options” page.
In the section “Performance Options”, set “Maximum execution time for each scan stage” to 15 seconds.
Don’t forget to “Save Changes”.
Try another scan.
If the scan still does not complete, try this instead:
Go to the Wordfence Tools page, click the Diagnostics tab, and open the “Other Tests” section.
Now click on “Click to view your system’s configuration in a new window”.
Look for max_execution_time.
Go back to the “Scan Options” and the section “Performance Options” and set the “Maximum execution time for each scan stage” to about 80% of that value. So if it’s 90, try setting the option to 75.
Try another scan and see if that works.
Can you please try these steps and let me know if it helps?
https://www.wordfence.com/help/scan/troubleshooting/#scan-time-limit-exceeded
Thanks,
Gerroald
Thread Starter
mkcn
(@mkcn)
Thanks @wfgerald
After setting the maximum execution time for each scan stage to 15 seconds, standard scans have managed to complete under 3 minutes on the first two websites I tried. The third resulted in:
Fatal error: Out of memory (allocated 174063616) (tried to allocate 217088 bytes) in */wp-db.php on line 1972 The site is experiencing technical difficulties
I have asked 123-Reg for help on this one.
I’ll leave the scan settings as they are on the first two and see what happens overnight. 123-Reg support stated that their system is triggered to update Wordfence settings if a scan exceeds 3 minutes.
-
This reply was modified 6 years, 11 months ago by
mkcn.
-
This reply was modified 6 years, 11 months ago by mkcn.
Hi again
Mine have now started to fail again.. so I think that 123-reg are probably resetting them again, which is really annoying. I will try the suggestions above
Thanks – I have just followed the suggestions by @wfgerald to do with setting the scan stage times to 80% of the max execution time and it has worked. Thank you!
Thread Starter
mkcn
(@mkcn)
Hi @singingcyclist and @wfgerald
I am finding that settings can be changed and scans run successfully on demand, but overnight the scan will be reset to Limited with the following settings:
Limit the number of issues sent in the scan results email: 1000
Time limit that a scan can run in seconds: 180
How much memory should Wordfence request when scanning: 256
Maximum execution time for each scan stage: 180
I have set a time limit of 178 on a standard scan and it stills gets reset, similarly I have reduced the maximum execution time to 15 seconds and it still gets reset.
Thread Starter
mkcn
(@mkcn)
Yep, 123-Reg have confirmed that Wordfence settings are automatically changed overnight to the ones they support – i.e. “Limited” scans.
yes you are right .. I can make the scans work manually, but by setting the max execution time , but then 123-reg reset it
this really isn’t a workable solution for me as I need Wordfence to run in the background and alert me of problems
Hi All,
I’ve spoken with the developers about this. They’re reaching out to 123-Reg to see if we can get this resolved. But unfortunately, there isn’t anything we can do to resolve it on our end. I’ll be sure to report back here when I know more.
My apologies for the inconvenience.
Thanks,
Gerroald
