Can’t Scan

Hi @tpaul25, thanks for your message and providing your diagnostic.

The diagnostic report isn’t report scan issues, or connectivity issues for that matter that would immediately highlight an obvious problem. Can you do the following so I can get more information help you?

• 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 from the Log (click the “Show Log” link) or so of the activity log once the scan finishes and paste them in the post.

Thanks,

Peter.

Hi @tpaul25, thanks for the detailed log information.

Please check the instructions under Scan process ended after forking in our documentation to ensure permissions and .htaccess blocks are not preventing access to the wp-admin folder. Memcache or object-cache may also need to be restarted twice if present on your configuration. Also ensure your own server IP has access to this folder.

If none of the approaches above succeed, could you send a diagnostic report to wftest @ wordfence . com? You can find the link to do so at the top of the Wordfence Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

Note: For the fastest response time, please make sure and add any information or questions directly to this post and not the email address above unless asked.

Thanks,

Peter.

Hi @tpaul25,

I can’t find anything in your diagnostic that points to a cURL connectivity issue or plugins that are known to conflict with the scan process. There are also 0 scan issues being reported there. Your WordPress and PHP memory limits also look good so I don’t suspect that the site is running out of memory during the scan at this stage.

If you have tried from the link I provided that wp-admin has the recommended 755 permissions by using your hosts’ file manager or FTP, or is not blocked through .htaccess rules, then we might be looking at a different cause.

Is the scan able to run if you disable all plugins except for Wordfence? Also, it might be worth trying the scan in low-resource mode:

• Navigate to All Options (wp-admin/admin.php?page=WordfenceOptions)
• Scroll to the “Performance Options” section.
• Check the box that says “Use low resource scanning (reduces server load by lengthening the scan duration)”.
• Save the change.

Thanks again,

Peter.