chw0rd
Forum Replies Created
Viewing 5 replies - 1 through 5 (of 5 total)
-
Problem solved! My host turned on curl_exec, and now the scanning is working just fine. Thanks for your help.
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
Thank you, I have sent the diagnostic!
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 9 months, 4 weeks ago by chw0rd.
Could you share how you got this working—I have the same error. I did all the steps suggested on the support page but still get the, “Scan process ended after forking.”
I was able to get the scan going once by munging the URL and changing isFork=0 to isFork=1
Viewing 5 replies - 1 through 5 (of 5 total)