Search results

It is not directly related to mod security, in general, we recommend using DEBUG or INFO level logging, so we can get more information from error log when we need to trouble shoot something.

Please force update to the latest build 5.0.12, run command /usr/local/lsws/admin/misc/lsup.sh -f -v 5.0.12 If it is not fixed, we need one example of such configuration. Is the directory the same as a vhost public_html directory? a sub directory under public_html? or it is above all...

Yes, for that particular log entry, NOTICE is fine.

You want those rewrite rules to be applied to all vhosts? We nee to know how the rewrite rule was configured? in a <Directory ...> context or not. Can you give us the content as-is in your Pre VirtualHost Include?

Please contact bug@litespeed with core files available for download. we need to find out what happened with the core file.

It is working fine in our lab. Maybe something special in your setup. We need to know more about your server environment. control panel? is a sub-domain? Best way to trouble shoot is to give us a temp root access.

Please try the latest build 5.0.12 /usr/local/lsws/admin/misc/lsup.sh -f -v 5.0.12

If you have trouble with their cache, you can try ours. https://wordpress.org/plugins/litespeed-cache/

yes. they can.

It is likely that you have compression enabled on PHP side. Please check PHPinfo page, make sure zlib.output_compression is off.

https://nghttp2.org/documentation/h2load-howto.html

HTTPS wont be able to match HTTP. sendfile() system call cannot be used. Serving HTTPS traffic is CPU bounded as every bytes has to be encrypted/decrypted. Fully utilized multi-core license should help. Your test does not use HTTP/2 to save HTTPS handshake cost.

We did some tests, it is working fine. maybe you can turn on full debug logging and send us log for analysis. Just grep your IP in the log to get related entries.

The autoupdate system still follow 5.0.x releases. For you, you should manually upgrade to 5.1.2 /usr/local/lsws/admin/misc/lsup.sh -f -v 5.1.2

If you google "zend_mm_heap corrupted" you will find a lot work around attempts, give them a try.

5.1RC3 is pretty stable now, you can give it a try if you have not yet. /usr/local/lsws/admin/misc/lsup.sh -f -v 5.1RC3

Anything in stderr.log around 2016-01-06 19:35:00.820 It looks like not a memory limit issue. I wonder if PHP crashed. have you tried another version of PHP?

Will it work if you upload less than 5 pictures? Does the picture size matter? Do you have Apache setup, will Apache work if switch back to Apache? Have you checked error log and stderr.log for related log messages? It could be PHP crashed. Need to follow the 503 trouble shooting guide in our...

Unfortunately, it is the way it works. client IP are received through x-forwarded-for request header. LSWS cannot block proxy IP, so all requests forwarded from proxy server has to be accepted. unless there is a way to notify the proxy server to block those IPs at proxy server, no way to block...

Are you using a front-end proxy? Since all traffic going through the proxy server, LSWS has no idea which IP the request coming from until the whole request header has been received as the real client IP is forwarded through request header.