Server Issues¶

This page will address problems that may occur with a LiteSpeed Web Server/WHM installation. The installation process is covered in our Quick Start Guide.

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"

or

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 /usr/bin/gcc to 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

mod_lsapi Incompatibility¶

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.

404 and Default SSL Certificate Shown for Dedicated IP Domain¶

There is a use case where you may have a dedicated IP for your cPanel account, and only one domain.

Under normal circumstances, if you directly access the dedicated IP, the correct SSL certificate and website will be shown. You may find, though, that the main server certificate shows a 404 error, if your account has been suspended and then reactivated.

This is because the sequence of SSL virtual host configuration in httpd.conf matters. For a given IP, the default SSL certificate used is the first SSL vhost configured for that IP. In the case of an account that has been suspended and then reactivated, the vhost configuration sequence has been changed. As such, the default SSL vhost is configured first for the IP, and so the default certificate is used.

You can manually move the vhost configuration for your domain above the default SSL vhost, so that your IP will use the certificate configured for your vhost.

How to force the vhost configuration to be generated in the desired order is out of the control of LiteSpeed Web Server software. If you wish to do this, please contact the control panel vendor for further assistance.