• Resolved sbct

    (@sbct)


    Hello there!
    I’m contacting because I’m having a problem activating lite speed web cache.
    I see that in cPanel I get an error “warning” when activating the lite speed function: could it be the extended protection that modifies the .htaccess? In this case how could I resolve?

    Thanks!

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

    (@wfpeter)

    Hi @sbct, thanks for reaching out to us.

    When activating Litespeed in your hosting cPanel, Wordfence should not be acting on any of this process due to its protection being directly related to actions on your WordPress site rather than the wider hosting environment.

    I would first speak with your host’s support to see if any file permissions or other hosting settings on your account are preventing the activation of Litespeed. Detail to them the precise error you’re seeing on-screen and they should be able to get it resolved.

    Once Litespeed is active on your site, you will want to consult this guide to make sure it’s set up correctly with Wordfence: https://www.wordfence.com/help/advanced/system-requirements/litespeed/

    Peter.

    Thread Starter sbct

    (@sbct)

    Hello @wfpeter,
    Thanks for your help!

    I’ve contacted the hosting service but they said there could be a problem with the installation and they need a “clean” .htaccess as they say it could be the problem of this, but I can’t reset the file as I have different plugins which write security-related features on it.

    I’ve added the code you advised in the link into the .htaccess.

    Do you have any idea on how I can resolve the issue?

    Thanks!

    • This reply was modified 4 years, 1 month ago by sbct.
    Plugin Support wfpeter

    (@wfpeter)

    Hi @sbct,

    If you have the Litespeed “noabort” code, then you are likely prepared for using Wordfence on Litespeed but if you’re unable to activate it then the code in .htaccess probably doesn’t have the desired effect.

    You could try backing up this .htaccess and suggesting to the host that they can work with a ‘clean’ one now if they desire to configure/troubleshoot Litespeed. You could then either run a disable/enable cycle (or remove/reinstall) on appropriate plugins that have modified this file to re-write the missing data into your new .htaccess, or copy the differences from your backup .htaccess to the new one.

    Thanks again,

    Peter.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Lite speed problem’ is closed to new replies.