I've installed LiteSpeed, and couldn't be happier!
However, it is expensive which is a downside.
You won't find a cracked version unless you already have it.
It's a sweet webserver application that replaces Apache.
This guide will show you how to integrate it with cPanel. :happy:
Before you do this - you should have it installed
---
How to use LiteSpeed together with cPanel/WHM
Directory Auto Index
To turn on directory auto index, just change Index Files configuration
Run Apache behind LSWS for missing features
There are some rarly used Apache features which are not supported by LSWS, like Server Side Include, full mod_perl functionalities, mod_svn, etc., dont worry, LSWS can forward requests to Apache running behind LSWS. For example, to forward request of SSI page with suffix shtml to Apache, do the following:
Restart Apache and LSWS, SSI pages should be served by backend Apache now.
However, it is expensive which is a downside.
You won't find a cracked version unless you already have it.
It's a sweet webserver application that replaces Apache.
This guide will show you how to integrate it with cPanel. :happy:
Before you do this - you should have it installed
---
How to use LiteSpeed together with cPanel/WHM
Steps to replace Apache with LSWScPanel is one of the most popular web hosting control panels used by web hosting companies. cPanel uses Apache web server and depends on many Apache features. LiteSpeed web server is designed to be Apache interchangeable as a drop-in replacement. Since 2.2.5 release, LiteSpeed Web Server works very well with cPanel managed web sites.
You will get many benefits by replacing Apache with LSWS, web pages get loaded faster, server load is lower and memory usage is lower. More web sites can now be hosted on the same server.
With LSWS 3.3.1 Enterprise or later, the LSWS installer can setup configuration for cPanel automatically. The default LSWS configuration comes with support for both PHP4 and PHP5, however, only pre-built PHP4 binary is available, if you want PHP5 support, you need to build PHP5 binary yourself. Just login to the web console then select Actions→Build PHP. You should use the same PHP configuration used for building Apache mod_php to build the lsphp binary, you can get the information from a phpinfo() page.
- Install LiteSpeed Web Server as root user. During installation, make sure to set User/Group to nobody:nobody, do NOT import Apache configuration, do NOT set 2080 or 80 as the HTTP service port, those ports will be used when httpd.conf is loaded.
- Open LiteSpeed Web administration console, under server→General tab, change configurations in Using Apache Configuration File table.
PHP suEXEC Max Conn can be adjusted based how many and how big the sites has been hosted. For a server dedicated for a large Wordpress or vBulletin site, you can safely increase it to 10, 15 or 20, try different value and see what is the best for you.Load Apache Configuration => Yes
Auto Reload On Changes => Yes (Changes made in WHM/cPanel will be applied automatically)
Apache Configuration File => /usr/local/apache/conf/httpd.conf
Apache Port Offset => 2000 (Try LiteSpeed on port 2080 and 2443 first, change to 0 later, do NOT use 8088 or 8008)
Apache IP Offset => 0
PHP suEXEC => Yes (Run PHP in suEXEC mode)
PHP suEXEC Max Conn => 5 (The maximum PHP processor each account can have)
- Restart LSWS and try web sites hosted on port 2080 and secured sites on 2443. If all sites work properly, stop Apache, change Apache Port Offset to 0, restart LSWS, all hosted web sites are powered by LiteSpeed now.
If you have a script that monitors for the web server process, remember to update it to reflect the location of LSWS. If your datacenter or third-party administrator monitors your web server for you, you may want to contact them to inform them of the change.cd /etc/init.d
chkconfig httpd off
Directory Auto Index
To turn on directory auto index, just change Index Files configuration
If PHP open_base dir option has been enabled, you may get error likeAuto Index => Yes
Auto Index URI => /_autoindex/default.php
You need to add directory /usr/local/lsws/share/autoindex to the open_basedir list, or move dirtory /usr/local/lsws/share/autoindex to /usr/lib/php/autoindex, then create a symbolic link from /usr/lib/php/autoindex to /usr/local/lsws/share/autoindex.Warning: Unknown(): open_basedir restriction in effect.
File(/usr/local/lsws/share/autoindex/default.php) is not within the allowed path(s):
(/home/lsws:/usr/lib/php:/usr/local/lib/php:/tmp) in Unknown on line 0
Warning: Unknown(/usr/local/lsws/share/autoindex/default.php):
failed to open stream: Operation not permitted in Unknown on line 0
Run Apache behind LSWS for missing features
There are some rarly used Apache features which are not supported by LSWS, like Server Side Include, full mod_perl functionalities, mod_svn, etc., dont worry, LSWS can forward requests to Apache running behind LSWS. For example, to forward request of SSI page with suffix shtml to Apache, do the following:
- Listening port of apache should be changed to 79 for HTTP and 442 for HTTP.
- Apache Port Offset configuration in LSWS should be changed to 1, so LSWS will use port 80 and 443.
- Set Apache Handled Content configuration to .shtml, this will off load all request to *.shtml to backend Apache, if you want to have apache handle request with certain URL prefix, for example, a svn repository under URI /svn/, then you can set Apache Handled Content to .shtml, /svn/ to let Apache handle both *.shtml and /svn/*
Restart Apache and LSWS, SSI pages should be served by backend Apache now.