Scan process ended after forking error

Hello GisokuBudo,
we have a similar issue documented for Litespeed. Have you tried that yet?

I tried it before without any luck, but did so again last night and added the code before the WordPress gear. No luck unfortunately. There is some W3 cache code in before there, would that be causing any issues?

What’s interesting is that Wordfence will still keep me informed of admin logins and will also notify me if plugins are out of date. Does this help narrow down what’s potentially happening?

Hello GisokuBudo,
could you please send me a diagnostics report so I can investigate this further? Go to Wordfence “Diagnostics” page and at the bottom click the button that says “Send Report by Email”. Change the prefilled address to [email protected] and please provide your username so I know who the mail is coming from.

Hello,

I have the same issue on all sites that have wordfence installed since 24th of April I guess…

Nothing to add, just posting here to be informed of any reply ??

Thanks
F.

Thanks Frederic,
I’m sorry to hear that. Would you consider sending me a diagnostics report as well? It will help when trying to narrow this down. If so, please follow my instructions in the post above. Thanks in advance.

Done,

Sent from 4 of the sites I’m managing. Hope this helps

Hi wfasa – all done, thanks for looking into this!

Any update ?

FYI, upgrading to Wordfence 6.1.7 had no effect, still the same error. Nevertheless, I receive the weekly status. Only the scan seems to hang.

Hi,

On the Wordfence options page, below the option that says “Update Wordfence automatically when a new version is released”, do you see a warning about LiteSpeed still? If the .htaccess code @wfasa mentioned is included, usually that warning should disappear.

I tested on a local LiteSpeed server and it is working here, but @wfasa sent me your diagnostic reports, and typically we should see “$_SERVER[‘noabort’]” in the PHP Variables section, but it’s missing in these two reports.

This might be a change in the latest version of LiteSpeed, or it might be due to LiteSpeed’s settings. If you have access to LiteSpeed’s configuration, can you check these options on the page for your virtual host?
* On the General tab, “Access File” Name should be “.htaccess”
* On the Rewrite tab, “Enable Rewrite” should say “Yes”

If you have access to the server’s main config, you can also try a setting on the Server tab, on the General tab below that — if you set “External Application Abort” to “No abort”, see if the scan can run after that.

If you have access to the site’s error logs, can you see if there are any errors after running a scan?

-Matt R

@wfmattr: Thanks for the reply, here are my findings:

do you see a warning about LiteSpeed still?: I just checked and yes, I still see it.

I’ve checked the available config options I have on the virtual server and I don’t have access to manage/configure Litespeed to implement the changes you have suggested. I can send your instructions through to our host to see if they can make the changes though. Would your instructions suffice for what they need to do, or is there additional information I would need to pass along?

Hi,

I believe this should be enough information, but if the host has other settings that might be stopping the .htaccess file from working normally, it may not fix the issue. (If they set the “No abort” option directly, Wordfence can’t detect that to make the warning message go away, but it would still help the scans complete fully.)

It’s also possible this is caused by a difference in some LiteSpeed versions, so if it still doesn’t help, let me know and I’ll see what else we can find out.

-Matt R

Hello,

I just checked and to the question “do you see a warning about LiteSpeed still?” the answer is non, I don’t see it…

Unfortunately, I don’t have access neither to litespeed nor to the server configuration…

Hello Frederic,
if you check the .htaccess in your root, do you see a # Wordfence WAF section there containing an auto_prepend_file directive? If so, try adding this to the bottom of your .htaccess. You can use the path that is already defined in the # Wordfence WAF section.

<IfModule lsapi_module>
  php_value auto_prepend_file 'path/to/wordfence-waf.php'
</IfModule>

Hi,

I checked on two sites, on one I have the #Wordfence WAF section, not on the other…

On the one that has that section, I past the lines you mentionned, but it didn’t correct the issue ??

Hello Frederic,
I have the diagnostics reports you sent me earlier and I saw that they were all LiteSpeed V6.9 so I thought that could have worked.

What is the default value that is chosen for you when you configure the Firewall?