Hi @hankseifert,
Thank you for sending us those diagnostics.? If you’re still having issues with your scan, I have a few suggestions I’d like to make.
Since you’re using Cloudflare, please ensure you’ve configured Cloudflare to allow connections from your site’s server back to itself. Our guide on that is here: https://www.wordfence.com/help/advanced/compatibility/
Settings over 60
for the max_execution_time
have been known to cause issues in the past.? Please set max_execution_time = 60
or 30
in php.ini.
Please set WP_MEMORY_LIMIT
to 256M
or 512M
in wp-config.php. WooCommerce, for example, recommends 256M minimum, so if you also have many hits on the site at once during a Wordfence scan, a lower limit here could be reached fairly easily. Your PHP memory_limit
value should be set to the same or higher to accommodate this change otherwise there won’t be enough room for WordPress to use the higher value it is requesting.
Please enable Use only IPv4 to start scans in Scan > Scan Options and Scheduling > Advanced Scan Options.? Be sure to Save Changes.
If scans are still failing after implementing those suggestions, I’d like to get a debugging log from you. If you could do the following steps for me:
- Go to the Wordfence > Tools > Diagnostics page
- In the “Debugging Options” section check the circle “Enable debugging mode”?
- Click to “Save Changes”.
- CANCEL any current scan and start a NEW scan
- Click the “Email Activity Log” link once the scan finishes and send that to wftest @ wordfence.com and respond here after you have sent it.
Wordfence > Tools > Diagnostic > Debugging Screenshot
This will help me see exactly what is happening when the scan fails.
Thanks,
Margaret