Unable to scan

Hi @chordzone, Thank you for reaching out.

Have you already tried all of our troubleshooting tips centered around this type of error message? https://www.wordfence.com/help/scan/troubleshooting/#scan-process-ended-after-forking 

From the error log,  I noticed you have high value set for the max_execution_time . Sometimes, a higher max_execution_time value has been found to be detrimental to scan speed. We have seen issues arise when this number exceeds 60, although Wordfence will only attempt to use half of this value by default. don’t have some performance options set. 

Go to your Wordfence > Scan > Manage Scan and locate the “Performance Options” section. Set “Maximum execution time for each scan stage” to 20. For a screenshot of my recommended Performance setting options – Click Here.

Adding “20” for the “Maximum execution time for each scan stage” tells the scan to pause every 20 seconds and start again where it left off, which makes the scan more performance-friendly for some servers. Once done, go to Wordfence > Scan > Scan Options and Scheduling and check to see if the bottom two options in General Options are disabled. It would be best to have those disabled for now (Scan files outside your WordPress installation, Scan images, binary, and other files as if they were executable)

Additionally, confirm that the Scan Option is set to Standard. Be sure to save your changes in case you make any changes here.

Please try running scan with the updated settings and let me know whether you have any issues.

Thanks,

Mark.

i have made the changes like you said and after saving, I’m getting the same error. It is stopping after forking

Can somebody please help me? This is the error I’m getting after making the above changes:

• [Nov 17 00:56:07] Ajax request received to start scan.
• [Nov 17 00:56:07] Entering start scan routine
• [Nov 17 00:56:07] Got value from wf config maxExecutionTime: 20
• [Nov 17 00:56:07] getMaxExecutionTime() returning config value: 20
• [Nov 17 00:56:07]?Starting cron via proxy at URL https://noc1.wordfence.com/scanp/www.chordzone.org/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&scanMode=custom&cronKey=…
• [Nov 17 00:56:07] Scan process ended after forking.

Hello @chordzone, Sorry for the delayed response.

Go to Wordfence > Scan > Scan Options and Scheduling and check to see if the bottom two options in General Options are disabled. It would be best to have those disabled for now (Scan files outside your WordPress installation, Scan images, binary, and other files as if they were executable)

Additionally, please confirm that the Scan Option is set to Standard. Be sure to save your changes in case you make any changes here.

Can 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.

Thanks,

Mark

Hi

I’ve sent you the report. I checked the bottom two options and they were turned off. The scan was set to standard and i tried again. I got the same error as above and the scan stopped.

@chordzone,

Thank you for sending the diagnostic report.?

Are you by any chance running your website on Cloudfare? 

If your site is running Cloudflare, you may need to update your Cloudflare settings to allow your site to connect back to itself. 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 Source Address”
• Enter your site’s IP address under “Value”
• At the bottom, under “Then…Choose an action” change “Block” to “Allow”
• Click “Deploy

Once you have added your site to the Cloudflare Whitelist, head back over to your site and attempt another scan. Sometimes, the same process needs to be done for our IP addresses, which can be found here: https://www.wordfence.com/help/advanced/#servers-and-ip-range

Also ensure your visitor IP detection is set up correctly for Cloudflare. Head over to your site and go to Wordfence > All Options > General Wordfence Options > How does Wordfence get IPs. You will most likely need to select “Use the Cloudflare “CF-Connecting-IP” HTTP header to get a visitor IP. Only use if you’re using Cloudflare.”.

Thanks,

Mark