Hi @nanny7,
I can find a diagnostic you sent us on 21 July which didn’t seem to contain any connectivity issues, but can’t see any further emails flagged up with your forum username more recently. Feel free to send us another email to wftest @ wordfence . com with your username in the subject line to help us identify it.
Has a site cleaning already been performed after the compromise you mention in the subject?
If the above message you sent wasn’t a specific scan log, please try the following:
- Kill the existing scan if it is still running (The “Start New Scan” button turns in to a “Stop” button while the scan is running)
- 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”
- 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 or so from the Log (click the “Show Log” link) once the scan finishes and paste them in the post.
I apologise if the lengthy scan is required to obtain this log information, but it can be extremely descriptive in discovering the reason why a scan has frozen or executed for a long period of time and been stopped by the server.
Thanks,
Peter.
