Hi @flesaux, thanks for your message!
In some instances with load balanced databases and web sites, the scan will stop with this exact error. In Wordfence > Scan > Scan Options > General Options, this has been known to be fixed by disabling the “Scan file contents for malicious URLs” option.
If that doesn’t work, check your maximum execution time:
- Cancel any existing scans.
- Go to your Scan > Scan Options and Scheduling page and locate the “Performance Options”
Set “Maximum execution time for each scan stage” to 20 on the options page
- Click to “Save Changes”
- Try another scan.
If you continue to experience problems, you can also take the following steps so that I can grab some information to help you:
- Go to the Tools > Diagnostics page
- In the “Debugging Options” section check the circle “Enable debugging mode”
- Click to “Save Changes”.
- Start a new scan.
- Copy the last 20 lines from the activity log (click the “Show Log” link) once the scan finishes and paste them here.
There could also be issues around caching, allowlisting of IPs, or a problem with the database itself (depending on your platform) so it might still be necessary to troubleshoot further, but seeing what exactly the scan was trying when it failed would be useful.
Thanks,
Peter.
