Scan stops while indexing files

Hi @gloriousnoise, thanks for getting in touch.

As you’ve already undergone some troubleshooting regarding remotely starting scans, I apologize if any of this covers the same ground but make sure you’ve tried everything on the following page: https://www.wordfence.com/help/scan/troubleshooting/

If nothing there helps get to the bottom of it, feel free to drop us 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: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email

Thanks,

Peter.

Thank you. Sent!

Hi @gloriousnoise, thanks for sending that over.

Most of the information there doesn’t seem to flag as a site that can’t run scans to me. I’m satisfied with the max_execution_time at 30 and that you’re using CF-Connecting-IP for IP detection.

Have you already added your own site to Cloudflare’s whitelist? I suspect you may have as the scans were once working here, but you may need to update your Cloudflare settings to allow your site to connect to our servers and back to itself too. You should be able to do this by going to your Cloudflare control panel.

• Login to Cloudflare
• Go to “Firewall”
• Click the “Firewall Rules” tab
• Click “Create a Firewall rule”
• Name the rule under “Rule Name”
• Set the “Field” under “When incoming requests match…” to “IP Address”
• Enter your site’s IP address OR a Wordfence IP under “Value”
• At the bottom, under “Then…Choose an action” change “Block” to “Allow”
• Click “Deploy

You can discover your site’s IP in Wordfence > Tools > Diagnostics > Connectivity > IP(s) used by this server. Our IPs, should you also need to add those using the process above, are available at: https://www.wordfence.com/help/advanced/#servers-and-ip-range

Once you have added your site and our IPs to the Cloudflare Whitelist, head back over to your site and attempt another scan. It may also be worth clearing any caches on your server or WordPress plugins before doing so, too.

After making these changes, 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
• 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 this post.

Wordfence > Tools > Diagnostic > Debugging Screenshot

This will help me see exactly what is happening now if the scan is still failing.

Thanks,

Peter.

Thank you. Added my site’s IP and all the WF IPs to firewall rules in Cloudflare. Cleared cache. Enabled debugging mode and ran a scan and it still failed: “The current scan looks like it has failed. Its last status update was 15 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.”

Here are the last 20 lines:

[Jun 21 09:28:59] Scanning: /home/myuser/domains/gloriousnoise.com/public_html/wp-admin/js/customize-controls.min.js (Mem:47.0M)
[Jun 21 09:28:59] Scanning: /home/myuser/domains/gloriousnoise.com/public_html/wp-admin/js/customize-nav-menus.js (Mem:47.0M)
[Jun 21 09:28:59] Scanning: /home/myuser/domains/gloriousnoise.com/public_html/wp-admin/js/customize-nav-menus.min.js (Mem:47.0M)
[Jun 21 09:28:59] Scanning: /home/myuser/domains/gloriousnoise.com/public_html/wp-admin/js/customize-widgets.js (Mem:47.0M)
[Jun 21 09:29:00] Scanning: /home/myuser/domains/gloriousnoise.com/public_html/wp-admin/js/customize-widgets.min.js (Mem:47.0M)
[Jun 21 09:29:00] Analyzed 400 files containing 6.95 MB of data so far
[Jun 21 09:29:00] Scanning: /home/myuser/domains/gloriousnoise.com/public_html/wp-admin/js/dashboard.js (Mem:47.0M)
[Jun 21 09:29:00] Scanning: /home/myuser/domains/gloriousnoise.com/public_html/wp-admin/js/dashboard.min.js (Mem:47.0M)
[Jun 21 09:29:00] Scanning: /home/myuser/domains/gloriousnoise.com/public_html/wp-admin/js/edit-comments.js (Mem:47.0M)
[Jun 21 09:29:00] Scanning: /home/myuser/domains/gloriousnoise.com/public_html/wp-admin/js/edit-comments.min.js (Mem:47.0M)
[Jun 21 09:29:00] Scanning: /home/myuser/domains/gloriousnoise.com/public_html/wp-admin/js/editor-expand.js (Mem:47.0M)
[Jun 21 09:29:00] Scanning: /home/myuser/domains/gloriousnoise.com/public_html/wp-admin/js/editor-expand.min.js (Mem:47.0M)
[Jun 21 09:29:00] Scanning: /home/myuser/domains/gloriousnoise.com/public_html/wp-admin/js/editor.js (Mem:47.0M)
[Jun 21 09:29:00] Scanning: /home/myuser/domains/gloriousnoise.com/public_html/wp-admin/js/editor.min.js (Mem:47.0M)
[Jun 21 09:29:00] Scanning: /home/myuser/domains/gloriousnoise.com/public_html/wp-admin/js/farbtastic.js (Mem:47.0M)
[Jun 21 09:29:00] Scanning: /home/myuser/domains/gloriousnoise.com/public_html/wp-admin/js/gallery.js (Mem:47.0M)
[Jun 21 09:29:00] Scanning: /home/myuser/domains/gloriousnoise.com/public_html/wp-admin/js/gallery.min.js (Mem:47.0M)
[Jun 21 09:29:00] Scanning: /home/myuser/domains/gloriousnoise.com/public_html/wp-admin/js/image-edit.js (Mem:47.0M)
[Jun 21 09:29:00] Scanning: /home/myuser/domains/gloriousnoise.com/public_html/wp-admin/js/image-edit.min.js (Mem:47.0M)
[Jun 21 09:29:00] Scanning: /home/myuser/domains/gloriousnoise.com/public_html/wp-admin/js/inline-edit-post.js (Mem:47.0M)

Any updates? It seems like the scan is able to start but then just stops…

Hi @gloriousnoise,

I’ve checked through the topic and if you’ve followed the scan troubleshooting and altered the settings we discussed, I shouldn’t expect the scan to stop in the middle of the process any more.

If you’re still seeing the same results, please can you send me another diagnostic (so the settings changes should have taken effect compared to your first)? Please follow the instructions above again and let me know when you have sent it!

Thanks again,

Peter.