Adding the constant:
define('WORDFENCE_SCAN_FAILURE_THRESHOLD', 1800);
to wp-config.php restarted the scans immediately without intervention.
Refer: https://www.wordfence.com/help/scan/troubleshooting/#the-current-scan-looks-like-it-has-failed
Refer: https://www.wordfence.com/help/advanced/constants/
They still failed after 33 minutes, so I changed 1800 to 3600.
-
This reply was modified 8 years, 4 months ago by stevedoig.
-
This reply was modified 8 years, 4 months ago by stevedoig.
We’re receiving the same issue for 2 websites on our Linux shared hosting platform.
Wordfence 7.0.1.
Wordpress 4.9.2
We’ve updated max_execution_time to 600, and memory_limit to 512MB, and the issue remains for both.
This is as far as we get on both websites.
-
This reply was modified 8 years, 4 months ago by stevedoig.
-
This reply was modified 8 years, 4 months ago by stevedoig.
-
This reply was modified 8 years, 4 months ago by stevedoig.
-
This reply was modified 8 years, 4 months ago by stevedoig.
