This wiki will address problems that may occur on a LiteSpeed Web Server/WHM installation. The installation process is covered in our Auto-Installer wiki.
Note: For free support of LSWS please use the LiteSpeed forum. If you have an issue with cPanel (even while using LSWS) please contact cPanel support. They are fully trained to handle LiteSpeed Web Server.
Insufficient Process Memory¶
Insufficient process memory may result in the following error messages (when you try to build matching PHP):
Found Errors ERROR: /usr/local/bin/php -i returns 6 You can try to build matching PHP from command line: "/usr/local/cpanel/whostmgr/cgi/lsws/cmd_buildmatchingphp.sh"
Found Errors ERROR: /usr/local/bin/php -i returns 134 You can try to build matching PHP from command line: "/usr/local/cpanel/whostmgr/cgi/lsws/cmd_buildmatchingphp.sh"
To fix this, try increasing the Max cPanel process memory (Minimum: 512) in WHM > Server Configuration > Tweak Settings.
LiteSpeed Does Not Restart When Configuration Changes¶
In order for configuration changes to take effect, LiteSpeed Web Server should restart automatically. Do NOT uncheck the
httpd service under WHM > Service Configuration > Service Manager. If unchecked, WHM will not restart LiteSpeed automatically when configurations have been changed.
Incorrect gcc Permissions¶
cPanel may set permissions for
0700. This will break our PHP build script. To fix this, change the permissions for the directory:
chmod 0755 /usr/bin/gcc
After finishing your PHP build, you can change permissions back:
chmod 0700 /usr/bin/gcc
LSWS is not compatible with mod_lsapi so we recommend disabling it before installing LiteSpeed. All the functionality that mod_lsapi offers is already built directly inside of LSWS, so mod_lsapi is unnecessary, and in fact may cause issues and performance decreases.
Unexplained site downtime¶
If you have sites experiencing unexplained downtime, and you are using a proxy shield (such as CloudLinux Imunify360) we recommend disabling the shield. If the downtime ceases, then this is likely not a LiteSpeed or cPanel issue. Please contact the proxy shield software's support team.