Scan Error: Scan process ended after forking

  • Resolved chw0rd

    (@chw0rd)


    10 months, 3 weeks ago

    Hi Wordfence Friends,

    I have the “Scan process ended after forking” error, even after taking all the steps specified, and even after deleting and removing all the tables.

    Interestingly, and I don’t know how this worked, but I got one scan to start by URL hacking isFence from 0 to 1.

    I have emailed my logs 🙂

    Thank you. ch0

    • This topic was modified 10 months, 3 weeks ago by chw0rd.
Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter chw0rd

    (@chw0rd)

    10 months, 2 weeks ago

    A couple other factors that might be relevant:

    • My webhost is on PHP 7.4. Don’t know why.
    • Curl is disabled
    • I do have the Wordfence CLI running now on the server! That program is fantastic, but I’d prefer to have this working through the plugin
    • Above where I mentioned changing isFence—what I meant by that is that I took the URL from the log and pasted it into a new browser window, and changed the isFence variable from 0 to 1. Somehow, this kicked off a full scan. But the approach no longer works.
    • This reply was modified 10 months, 2 weeks ago by chw0rd.
    Plugin Support wfmargaret

    (@wfmargaret)

    10 months, 2 weeks ago

    Hi @chw0rd,

    Thanks for reaching out. Can you also 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: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email

    Thanks,
    Margaret

    Thread Starter chw0rd

    (@chw0rd)

    10 months, 2 weeks ago

    Thank you, I have sent the diagnostic!

    Plugin Support wfmargaret

    (@wfmargaret)

    10 months, 2 weeks ago

    Hi @chw0rd,

    Thanks for sending those over! Stop any currently running scans. In Wordfence > Scan > Scan Options and Scheduling > Advanced Scan Options, please enable Use only IPv4 to start scans. Make sure to save the change.

    Then, go to Wordfence > Tools > Diagnostics and expand the Debugging Options section. Enable the option Enable debugging mode and save changes.

    Start a new scan. If the new scan fails, please send me an updated scan log. Let me know here once you’ve sent that. Remember to disable Enable debugging mode after you have finished.

    Thanks,
    Margaret

    Thread Starter chw0rd

    (@chw0rd)

    10 months, 2 weeks ago

    Hmmm. The option “Use only IPv4 to start scans” is greyed out for me 🙁

    Curl is enabled on my shared host.

    cURL supportenabled

    cURL Information7.74.0

    Plugin Support wfmargaret

    (@wfmargaret)

    10 months, 2 weeks ago

    Hi @chw0rd,

    Thanks for letting me know. While I see the cURL extension is enabled on the site, curl_exec is disabled. If your host plans to keep curl_exec disabled, please see if they can disable the entire cURL extension, or if they can disable the other curl_ functions, such as curl_init.

    Please also check if there is any filtering on outbound requests. The host may be dropping requests when the query string contains certain keywords, or outbound POST requests, for example.

    Thanks,
    Margaret

    Thread Starter chw0rd

    (@chw0rd)

    10 months, 1 week ago

    Problem solved! My host turned on curl_exec, and now the scanning is working just fine. Thanks for your help.

    Plugin Support wfmargaret

    (@wfmargaret)

    10 months, 1 week ago

    Hey @chw0rd,

    Awesome, I’m glad to hear that! Thank you for letting us know! I’m going to mark this resolved.

    Thanks,
    Margaret

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Scan Error: Scan process ended after forking’ is closed to new replies.

Tags