mkcn

Hi @wfgerald,

123-Reg did try to help but I kept getting as far as Analyzed 0 files containing 0 B of data and the scanner moved on to the next step without analyzing any files.

In the end I deactivated the plugin, used Wordfence Assistant to delete all data and removed the .user.ini and wordfence-waf.php files from the root WordPress folder, as well as the Wordfence config in the .htaccess file.

I then reactivated the plugin, went through the setup process again and things look to be performing as normal. So possibly a corrupt DB table or config file.

Thanks for getting back to me,

Mark

• This reply was modified 4 years, 10 months ago by mkcn. Reason: To mark as resolved

Thanks @wfgerald,

They won’t lift the restriction, and when asked about why the limited scan fails they said…

Not only the size on disk of a website matters when a scan is performed. Also the number of pages of the website can increase the scan time. I can understand how frustrating this can be. I’m afraid that the scan time cannot be increased to more than 180 seconds.

Website has about 10 pages, so should I go looking for old media uploads to delete?

PS just to confirm, the Regex issue is also 123-Reg specific?

Yep, 123-Reg have confirmed that Wordfence settings are automatically changed overnight to the ones they support – i.e. “Limited” scans.

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.

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 5 years, 6 months ago by mkcn.
• This reply was modified 5 years, 6 months ago by 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.