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.