Search results

If you use LiteSpeed + hosting control panel, you can try switching back to Apache. If you use LiteSpeed native configuration, have you add any special configuration like rewirte/redirect? If the site uses .htaccess for some feature, you should post your post it.

Please try 4.0.9 . the webadmin code has been updated.

LiteSpeed Web Server 4.0.9 has been released Download LiteSpeed Web Server View Version History This release fixed a bug that causes random 503 errors in 4.0.7 and 4.0.8 . Upgrade is recommended. AutoUpdate will be activated a little bit later, if we do not receive serious bug report about...

It is possible if the botnet is large enough, for example, 1000 bots, each bots make 10 connections, that will be 10,000 connections, and it still not reach the threshold to ban a IP yet. If it happen again, you should check your netstat output see if it is true. What can you do if it is true...

Please follow: http://www.litespeedtech.com/how-tos.html#qa_dos

Please enable INFO level logging, no enough information to analyze it. It could be a real one.

This bug has been fixed, please download and try 4.0.8.

4.0.8 is available now, please download and upgrade.

4.0.8 release package is available to address bugs in 4.0.7, please download and give it a try.

Please download 4.0.7 again and have a manual update see if you still get it.

Are you using a hosting control panel? cPanel or other? looks like redirects are messed up. Is it a default installation? We do have installation service available $150.

what exactly not working properly? It should work out of box.

Please download 4.0.7 package again, the initial build may have 503 error, should have been fixed.

Maybe the best way to trouble shoot this is to PM me a temp root access to the test server. I could not reproduce it in our lab, must be something special in your environment.

You can continue use DirectAdmin + LiteSpeed, everything is still managed in DA. Please check our wiki for conversion guide.

Please download 4.0.7 release package again and do a manually upgrade. It should be fixed.

That's a strange error as we did not change anything related to https. if possible, please PM me a temp root login, I will take a look.

It could happen on a very busy server during graceful restart, the old server stop serving request for the admin console, while the new server process is not ready yet.

Can you please try the 4.0.7 release?

Right now, LSWS just follow linux file system permission, not act like suphp which block script with permission mask 777. LSWS uses open_basedir instead. However, it is nice to have feature, so we will add it to our to-do list. Yes, those permission settings posted in the image is for static...