Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @calsmillie,

    This error suggests that something is blocking access to the wp-admin directory which contains the admin-ajax.php file Wordfence needs access to.

    I would first suggest checking our troubleshooting guide for this error:

    https://www.wordfence.com/help/scan/troubleshooting/#scan-process-ended-after-forking

    Secondly, if none of the approaches above work, could 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.

    Note: For the fastest response time, please make sure and add any information or questions directly to this post and not the email address above unless asked.

    Thanks,

    Peter.

    Thread Starter calsmillie

    (@calsmillie)

    Hi @wfpeter,

    I tried to figure out the problem as best as I could via the troubleshooting guide, but to no success.

    I have just sent a report by email as instructed.

    Many thanks.

    Plugin Support wfpeter

    (@wfpeter)

    Hi @calsmillie, thanks for supplying that diagnostic information, it was very helpful.

    The report looks like a setting on Litespeed is aborting the scan. If you contact your web hosting provider to add the relevant .htaccess code (found in the link below) to disable the LiteSpeed External Application Abort setting, scans should then run:

    https://www.wordfence.com/help/advanced/system-requirements/litespeed/#if-litespeed-aborts-wordfence-scans-and-updates

    Thanks,

    Peter.

    Thread Starter calsmillie

    (@calsmillie)

    Thanks very much Peter, this solved the issue.

    Take care

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘San Failed’ is closed to new replies.