Search results

set "Memory Soft/hard Limit" to "500M" or above.

yes, that's normal.

No real difference, the rails context just make the configuration easier, behind the scene, corresponding external app will be added automatically.

Please follow our trouble shooting guide http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:rails:troubleshoot

both should work, using the rails context is recommended.

most likely a loop redirection happened, maybe caused by rewrite or "Redirect" directives, you need to find out which request causes this.

I create a simple proof of concept shell script, acting as Apache to LSWS wrapper, which replaces Apache executable. If some one help us test and prove that it works, we will add code to automate everything. It will be the ultimate solution for all hosting control panels.

sure, no problem

I don't know, but what I observed on your server is that, the data stay in TCP send buffer for very long time, so, it is TCP/network problem. You can check that with netstat -an | grep ESTA The "Send-Q" value stay the same non-zero value for very long when you experience the "SLOW" problem...

check the result of "iptables -L" You have rate limit. I don't know it is the root cause or not, but it is definitely a problem of your kernel configuration.

The first is due to memory limit, you may need to increase the memory limit.

I think it's because that IP address is not available on that server.

If you run Litespeed off Apache httpd.conf (with control panel), you cannot configure Awstats with Litespeed. use the one control panel provides.

It is a bug has been fixed in 3.3.7 release, have you upgraded to 3.3.7?

Check your "ServerRoot" directive in httpd.conf, audit_log should be at <ServerRoot>/logs/audit_log with LSWS 3.3.7 release.

tested it again, works well.

Your rule action is "log,pass, ...", it won't block anything, check the audit log see if anything logged.

Use write rule to redirect from http -> https or vice versa. Testing if ${SERVER_PORT} is 443.

https://localhost/

You need to check SSLv3 and TLSv1, MEDIUM and above.