Can’t optimize WAF with Litespeed

  • Resolved Daniel P.

    (@danidub)


    2 years, 3 months ago

    Hello, we have installed Wordfence plugin on a fresh WordPress website that uses Litespeed as the web server.

    We followed setup as usual, .htaccess was modified and .user.ini & wordfence-waf.php created without any issues.

    The problem is that the message “To make your site as secure as possible, take a moment to optimize the Wordfence Web Application Firewall:” never disappears.

    I have tried as told on other tickets to add noabort flags on .htaccess but the warning is still shown.

    I’m sending the diagnostic report related to my user to wftest @ wordfence . com

    Thank you.

    • This topic was modified 2 years, 3 months ago by Daniel P..
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @danidub, thanks for sending your diagnostic over.

    Nothing seems unsual aside from the auto_prepend_file required for optimization confirming as “No” rather than “Yes”. Even though you’re not running on OpenLiteSpeed, it might be worth checking your host’s control panel to see if they have a similar option to the “php.ini Override” mentioned here: https://openlitespeed.org/kb/enable-wordfence-on-openlitespeed/

    This is an example of “CyberPanel” where users had to use an override like that for it to work, even though it was using LiteSpeed Enterprise:
    https://community.cyberpanel.net/t/config-auto-prepend-file-does-not-work/17906/4

    Ultimately, you could also try manually optimizing by adding the:

    ; Wordfence WAF
auto_prepend_file = '/your/path/to/wordfence-waf.php'
; END Wordfence WAF

    …to your .htaccess file to see if it rectifies the message seen in your dashboard.

    Thanks,

    Peter.

    Thread Starter Daniel P.

    (@danidub)

    Hi @wfpeter,

    We have talked with the hosting provider and they manually insert the value on the auto_prepend_file parameter.

    All is working OK now, thank you.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Can’t optimize WAF with Litespeed’ is closed to new replies.