Your Site is Experiencing a Technical Issue

Hi @gopa4, thanks for reaching out about this.

This has been an issue for a few other customers, and this is what we’ve found when looking at server diagnostics:

Specifically the Allowed memory size of x bytes exhausted (tried to allocate x bytes), or Out of memory (allocated X) (tried to allocate X bytes) error is almost always memory exhaustion occurring outside of PHP somewhere on the server. There’s a chance that Wordfence’s scan, saving settings, or other Live Traffic operations triggered the error due to requiring some memory but it’s not the root cause.

Your operating system/web server log files will likely show if memory is being exhausted somewhere outside of PHP and why. This is usually a job for your hosting company’s support channels as they have access to those logs, diagnose the source and potentially resolve the problem. This can often be come from an issue with another site’s performance if you’re on shared hosting.

Thanks,
Peter.

Thanks for your answer. Now we moved our website to another hosting (Light Speed) and have another issue:

Wordfence scan uses a lot of memory (256 mb set in the setting, “Maximum execution time for each scan stage” default)

I started a test Scan Wordfence (manually)

Normal Memory use of our website is 360-460 mb

After the start, the scan The Memory goes up to 956 mb and stays above 920mb during the scan.

Hi @gopa4,

128M should still be an appropriate number to use either for WP_MEMORY_LIMIT in wp-config.php, your php.ini memory_limit value and/or your Performance settings so it’s worth trying to reduce it to see if anything changes. There is not a set amount of RAM or CPU we definitely know Wordfence will try to use (if available) though, as it can be affected by the size of your site or number of installed plugins.

Also 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.

Thanks again,
Peter.