Hi @barryseal, thanks for sending that over.
Aside from your auto_prepend_file not being set, meaning the firewall is working in Basic Protection mode, connectivity, permissions, and IP detection all seem to check out.
You do appear to be running on Litespeed so ensure it has been told not to abort firstly.
After this, I see the max_execution_time in your php.ini file is at -1, which is effectively limitless. Wordfence’s scan only ever attempts to use half of the value set here by default but there have been known problems with timeouts when higher values than 60 are set, so it could be worth changing to 60 or 30.
For a screenshot of my recommended Performance setting options inside the plugin too – Click Here.
Your WP_MEMORY_LIMIT values seem fine at 512M, where we might see problems below 128 so you shouldn’t need to change this.
Thanks,
Peter.
Hi @wfpeter,
Thank you for your reply. I have changed the max_execution_time to 30 as you suggested and will monitor it to see whether that makes a difference. If it doesn’t, I will change it to 60 as you indicated.
I will keep in touch with any updates.
Thanks,
@barryseal
Thanks @barryseal, let us know if any further issues crop up.
Hi @wfpeter,
It appears the latest scan has failed after adjusting the max_execution_time to 30 as you suggested.
The error message reads: “
“Scan Failed The current scan looks like it has failed. Its last status update was 1 hour 51 minutes ago. You may continue to wait in case it resumes or stop and restart the scan. Some sites may need adjustments to run scans reliably.” Click here for steps you can try. (opens in new tab)
Can you offer any suggestions on how to fix this please? Wordfence scans were stable for a some weeks prior to this, so I’m at a loss to explain why this has started again.
I sent the report once again from within Wordfence and attached my username: @barryseal.
Thank you for your assistance!
@barryseal