• Resolved Stephen

    (@ssgconline)


    Hi,

    I have received an email from Wordfence on one of my sites saying:

    To preserve the integrity of your website we are not running Wordfence auto-update.
    You are running the LiteSpeed web server which has been known to cause a problem with Wordfence auto-update.
    Please go to your website now and make a minor change to your .htaccess to fix this.

    However, my .htaccess file already has this entry after END WordPress.

    # END WordPress

    # Wordfence WAF
    <IfModule LiteSpeed>
    php_value auto_prepend_file ‘/home/ssgconli/balandscapes.com.au/wordfence-waf.php’
    </IfModule>
    <IfModule lsapi_module>
    php_value auto_prepend_file ‘/home/ssgconli/balandscapes.com.au/wordfence-waf.php’
    </IfModule>
    <Files “.user.ini”>
    <IfModule mod_authz_core.c>
    Require all denied
    </IfModule>
    <IfModule !mod_authz_core.c>
    Order deny,allow
    Deny from all
    </IfModule>
    </Files>

    # END Wordfence WAF

    Do I remove this existing code & place the new code above “# BEGIN WordPress”?

    Thanks,
    Stephen

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support wfphil

    (@wfphil)

    Hi @ssgconline

    That is not the code that we are referring to. It is this code outlined in this help guide below:

    https://www.wordfence.com/help/advanced/system-requirements/litespeed/

    Thread Starter Stephen

    (@ssgconline)

    I have changed the real domain name, but the entire current .htaccess file says:

    `# BEGIN WordPress
    # The directives (lines) between “BEGIN WordPress” and “END WordPress” are
    # dynamically generated, and should only be modified via WordPress filters.
    # Any changes to the directives between these markers will be overwritten.
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteRule .* – [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
    RewriteBase /
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    # END WordPress

    # Wordfence WAF
    <IfModule LiteSpeed>
    php_value auto_prepend_file ‘/home/bal.com.au/wordfence-waf.php’
    </IfModule>
    <IfModule lsapi_module>
    php_value auto_prepend_file ‘/home/bal.com.au/wordfence-waf.php’
    </IfModule>
    <Files “.user.ini”>
    <IfModule mod_authz_core.c>
    Require all denied
    </IfModule>
    <IfModule !mod_authz_core.c>
    Order deny,allow
    Deny from all
    </IfModule>
    </Files>

    # END Wordfence WAF`

    So do I need to update the file as shown below so there are 2 references to Wordfence?

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

    # BEGIN WordPress
    # The directives (lines) between “BEGIN WordPress” and “END WordPress” are
    # dynamically generated, and should only be modified via WordPress filters.
    # Any changes to the directives between these markers will be overwritten.
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteRule .* – [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
    RewriteBase /
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    # END WordPress

    # Wordfence WAF
    <IfModule LiteSpeed>
    php_value auto_prepend_file ‘/home/bal.com.au/wordfence-waf.php’
    </IfModule>
    <IfModule lsapi_module>
    php_value auto_prepend_file ‘/home/bal.com.au/wordfence-waf.php’
    </IfModule>
    <Files “.user.ini”>
    <IfModule mod_authz_core.c>
    Require all denied
    </IfModule>
    <IfModule !mod_authz_core.c>
    Order deny,allow
    Deny from all
    </IfModule>
    </Files>

    # END Wordfence WAF

    Thanks,
    Stephen

    Plugin Support wfphil

    (@wfphil)

    Hi Stehpen,

    Thank you for the update.

    There are three blocks of code listed in the documentation page.

    If Wordfence manual scans on the Scan page complete every time when none of those three blocks of code are added to your .htaccess file then there is no need to add one of those three blocks of code to your .htaccess file.

    If manual scans fail every time then you can test adding each of the three blocks of code one by one to your .htaccess file and run test scans. If a scan completes after adding one of the three blocks of code then you can leave that block of code and remove the others if you added those too.

    Thread Starter Stephen

    (@ssgconline)

    Thanks Phil,

    I have gone to Wordfence –> Scan –> Start New Scan & it ran successfully with everything ticked from Server State to User & Option Audit.

    The reason I started looking at this was because of an email I received from wordfence.

    To preserve the integrity of your website we are not running Wordfence auto-update.
    You are running the LiteSpeed web server which has been known to cause a problem with Wordfence auto-update.
    Please go to your website now and make a minor change to your .htaccess to fix this.
    You can find out how to make this change at:
    https://www.wordfence.com/help/?query=dashboard-litespeed-warning

    So if everything is OK, I just need to manually update Wordfence instead of auto-update when updates become available?

    Thanks,
    Stephen

    Plugin Support wfphil

    (@wfphil)

    Hi @ssgconline

    Thank you for the update.

    The email is warning you about a feature of LiteSpeed called External Application Abort. If it is enabled on LiteSpeed then it can cause the automatic update of our plugin to fail and cause scans to fail. If your scans complete everytime then this means that the External Application Abort feature is unlikely to be enabled on LiteSpeed and you don’t have to worry about Wordfence automatic updates from failing.

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

The topic ‘Wordfence & Lightspeed’ is closed to new replies.