• We value your experience with Plesk during 2025
    Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
    Please take this short survey:

    https://survey.webpros.com/
  • On Plesk for Linux mod_status is disabled on upgrades to improve Apache security.
    This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.

Question What is your Experience with Litespeed Webserver on Plesk?

lanix343

Basic Pleskian
Hey Pleskians,

I've been thinking about switching to Litespeed Enterprise for my Webserver. I tested it with the Plesk extension and I've been getting major performance improvements across all sites.

I'm interested to hear what your opinion and exprience with LS is.

Best,
Thomas
 
I wonder what you expect from Litespeed web server? Why does a default Nginx web server, for example, seem to you to be the worst option?
 
Hey Pleskians,

I've been thinking about switching to Litespeed Enterprise for my Webserver. I tested it with the Plesk extension and I've been getting major performance improvements across all sites.

I'm interested to hear what your opinion and exprience with LS is.

Best,
Thomas
We have all our servers with plesk an litespeed, @IgorG , performance are very better than nginx/apache and include that nginx only, just try it with lscache and you will see the diference! The bad thing is that it's not free, but in our case, we have buy our licence directly
 
Oh yes, it absolutely destroys apache nginx performance wise. Especially when it comes to uncached TTFB and wordpress backend speed.
 
I want to briefly share my experience with LiteSpeed on Plesk.

LiteSpeed doesn’t always work immediately after installation. On AlmaLinux, the solution was:

cd /usr/local/lsws/
wget https://www.litespeedtech.com/packages/lscache/lsws-wordpress-cache-manager-latest.tar.gz
tar -xzf lsws-wordpress-cache-manager-latest.tar.gz
chown -R root:root lsws-wordpress-cache-manager
chmod -R 755 lsws-wordpress-cache-manager


After this, everything worked perfectly.

Another important point: after installing LiteSpeed, domain-level PHP settings like memory_limit, max_execution_time, max_input_time, post_max_size, and upload_max_filesize will not work. These settings will only take effect if you configure them in the global PHP version. Otherwise, you may encounter 503 errors and won’t understand why—LiteSpeed does not enforce Plesk’s domain-level PHP limits.

You will also need to increase OS-level system limits for LiteSpeed to function properly.

SELinux will not show any errors under LiteSpeed. To troubleshoot SELinux issues, you need to temporarily switch back to Apache. Additionally, you will need to install SELinux modules related to LiteSpeed to prevent it from being blocked.

Resource Controller (Cgroups) does not work with LiteSpeed, so you will need to handle this separately.

In general, LiteSpeed is faster than Apache + Nginx in a proxy setup, but the improvement is not dramatic. I would not recommend using LiteSpeed with Plesk as it is not a fully mature setup. While you can optimize everything to the maximum, after a Plesk update, it’s likely that things will break and stop working.
 
Back
Top