Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
litespeed_wiki:plesk:apache [2015/07/21 17:52] Jackson Zhang [Steps to replace Apache with LSWS] |
litespeed_wiki:plesk:apache [2015/11/06 22:15] (current) Michael Alegre [Stopping Nginx Reverse Proxy Before LiteSpeed Installation] |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| With LSWS 3.3.1 Enterprise or later, the LSWS installer can setup configuration for Plesk 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 install LSPHP through RPMs from LiteSpeed repository (for RHEL/CentOS Systems) or build PHP5 binary yourself. You should use the same PHP configuration used for building Apache mod_php to build the lsphp binary. You can user phpinfo page for Apache as a reference to install or build your own one. | With LSWS 3.3.1 Enterprise or later, the LSWS installer can setup configuration for Plesk 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 install LSPHP through RPMs from LiteSpeed repository (for RHEL/CentOS Systems) or build PHP5 binary yourself. You should use the same PHP configuration used for building Apache mod_php to build the lsphp binary. You can user phpinfo page for Apache as a reference to install or build your own one. | ||
| + | ===== Stopping Nginx Reverse Proxy Before LiteSpeed Installation ===== | ||
| + | The latest version of Plesk may configure Nginx as a reverse proxy server that stands in between the Internet and Apache. Before installing LSWS, please turn off Nginx reverse proxy so that Apache is the only web server handling live traffic. Not stopping the Nginx reverse proxy will cause system errors and block the LiteSpeed process from being started. | ||
| - | + | Please refer [[litespeed_wiki:plesk:installation-12#stopping_the_nginx_reverse_proxy|here on how to turn off nginx reverse proxy]]. | |
| ===== Steps to replace Apache with LSWS ===== | ===== Steps to replace Apache with LSWS ===== | ||
| Line 30: | Line 31: | ||
| to run litespeed on port 2080 and apache on 80 at the same time. | to run litespeed on port 2080 and apache on 80 at the same time. | ||
| + | |||
| + | * LiteSpeed has default Admin Console Port as 7080 from long time ago, however Plesk use this port lately for reverse proxy bank-end Apache port, which causes numerous trouble and errors. We suggest to set default Admin Console Port to 7088 for Plesk users to avoid hassles. | ||
| * Open LiteSpeed Web administration console, under "server"->"General" tab, view configurations in "Using Apache Configuration File" table. For Debian based installation, you need to manually set those configurations | * Open LiteSpeed Web administration console, under "server"->"General" tab, view configurations in "Using Apache Configuration File" table. For Debian based installation, you need to manually set those configurations | ||
| Line 47: | Line 50: | ||
| - | * Now LSWS host web sites 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. | + | * Now LSWS host web sites on port 2080 and secured sites on 2443. You can test your domains for those two ports. Some application can not be tested this way. For example, WordPress specifies front-end URL with port in WP admin page hence you have no way to test 2080 unless you change it. If this case, you may have to just switch the traffic to LiteSpeed for testing.If all sites work properly, stop Apache, change "Apache Port Offset" to 0, restart LSWS, all hosted web sites are powered by LiteSpeed now. |
| * in case you may fail to stop Apache(service httpd stop;service httpd status) after LSWS installed: check if /usr/sbin/httpd_ls_bak exists and /usr/sbin/httpd is just an lsws wrapper. then | * in case you may fail to stop Apache(service httpd stop;service httpd status) after LSWS installed: check if /usr/sbin/httpd_ls_bak exists and /usr/sbin/httpd is just an lsws wrapper. then | ||