Search results

Yes, you can install LSWS to use "lsws/lsws" as user/group, set HTTP port to 80, make sure other web server have been stopped.

Are you using cPanel + LiteSpeed? are you using PHP suEXEC? Are you using a VPS? PHP opcode cache? It should be fast no matter what.

You need two IPs, and create SSL listener for each individual IP instead of "*:443".

Options -indexes

If you want to reinstall, you should remove the whole lsws/ directory.

Getting 503 error usually means that your PHP binary may crashed for some reason. please check error_log and stderr.log for any hint.

You need to build PHP with configuration options matching that from Apache mod_php or suphp.

You should install cPanel first, then install litespeed by following our wiki.

Turn it off as you are with apache.

looks like cPanel has changed some scripts. will look into it.

You should not set the limit that low, you are looking for trouble as the OS will count all processes running as that user, when the limit has been reached, no more processes can be launched. You should set the limit at lsphp5 external app level, it should be high enough for normal operation. I...

It is not likely going to work unless you chroot cPanel as well.

I think there are two sources for this problem. One is that user only send one request, LiteSpeed tries it multiple times due to back-end (PHP or backend app server) failure, like the charging credit card problem Tony had, for this part, it can be improved from LSWS internal. Another one is...

how many connections are in use?

You can try increase "Max connections" http://www.litespeedtech.com/docs/webserver/config/tuning/#maxConnections

Load balancer uses 1-CPU, most load balancer setup is Network I/O bound, not CPU bound unless you need to serve mostly HTTPS traffic. You can use the license on a server with any number of CPU/Cores. For load balancing large amount of HTTPS traffic, we can customize multiple CPU core license for...

http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:php:lsapi#trouble_shooting

3.3.24 is available now

Thanks for the recommendation. I think LSWS has most of those features already, and we will consistently improve our product upon that.

LiteSpeed always use the first context matched, in our case, without specifying the location, that "/login" context was associated with login/ directory, trailing slash was added automatically because of that. When there are multiple possible choices, LSWS always use the first match, and...