Viewing 1 replies (of 1 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @hellosite,

    I normally suggest to Litespeed customers having trouble with scans, some “noabort” code to be added to the site’s .htaccess. This stops Wordfence scans failing during operation. This checkbox option is for sites where the administrator has disabled these aborts globally already. If “External Application Abort” is set to “No Abort” in Litespeed, then you can enable this option so that Wordfence will skip checking for the .htaccess code.

    However, if you’re either not sure or can’t change this setting yourself, don’t check this option as your .htaccess file will probably require the following “noabort” code and therefore Wordfence will need to check for it:

    # BEGIN litespeed noabort
    <IfModule rewrite_module>
    RewriteEngine On
    RewriteRule .* - [E=noabort:1]
    </IfModule>
    # END litespeed noabort

    In some cases, depending on the host’s configuration, the above code may not help. An alternate method which may work is this:

    # BEGIN litespeed noabort
    <IfModule Litespeed>
    RewriteEngine On
    RewriteRule .* - [E=noabort:1]
    </IfModule>
    # END litespeed noabort

    OR

    # BEGIN litespeed noabort
    SetEnv noabort 1
    # END litespeed noabort

    We have a bit more information on this in this page in our docs: https://www.wordfence.com/help/advanced/system-requirements/litespeed/

    Thanks,

    Peter.

Viewing 1 replies (of 1 total)
  • The topic ‘Wordfence on Litespeed server’ is closed to new replies.