Search results

Please try 4.1.1 release.

another option is to ignore mod_php5 sapi_apache2 configurations. http://www.litespeedtech.com/docs/webserver/config/general/#apacheIgnoredModules that matches apache behavior under Plesk.

If there are more than one hundred IP addresses assigned to that server, you should try a full stop, then start cd /usr/local/lsws/bin ./lswsctrl stop ./lswsctrl start LSWS will bind to *:80 instead of each individual IP:80 when there are more than 100 IP addresses, to reduce the number of...

How many IP do you have on that box? Have you checked "netstat -an | grep LISTEN" see if IP:80 are binded. Try a full stop, then start from command line. No need to manually add listener in admin console. Also you can manually download 4.1.1 package by changing version number in the download...

Thank you for the bug report. It is as designed, for better performance, LiteSpeed follows symbolic links for document root directories while loading the configuration during LSWS startup, instead of doing it for each request. It can be easily addressed with a graceful restart.

This issue will be addressed in 4.1.1 release. Thanks for the bug report.

Can you try Apache with this. LiteSpeed need to follow Apache's behavior. An easy solution is to something in .htaccess for example2.com, it should stop inheriting rewrite rules from example.com.

Also, please check output of "dmesg", it is likely because "ip_conntrack" limit being reached.

The <LocationMatch> issue should be addressed in our 4.1.1 release when you put security rule in native LSWS configuration. However, for vhost configured through httpd.conf, you should configure mod_security through httpd.conf as if Apache is used.

Those rules should work fine with 4.1 release. We need to either check it on your server, or copy your configuration to our lab environment to reproduce it.

Please download and update, should work now.

a new build is available, please do a "force reinstall" from web console.

Please download and upgrade to the latest 4.1 std package. Just updated it.

It is likely a slow SQL query or something else blocked all PHP processed, increasing "max connections" wont work. You need to find out what happened from command line, check "top" output for CPU utilization, I/O wait, load, memory usage, etc. Check mysql slow query cache, check "mysqladmin...

There have been a few bug fix updates of 4.1 based on user feedback. Please try a force reinstall of 4.1, the problem could have been fixed.

There are many suffixes available, "php", "php5", "php53", you can use "php" suffix for the default one, either 5.3 or 5.2, then use php5 for the other.

please update again.

Please update again.

new build of 4.1 is available. A few more bug has been addressed.

4.1 package has been updated to address a few bug based on feed backs.