Search results

Currently "Require env" and "Require expr" are not supported. We will add that to our to-do list.

that configuration is for newer systemd release, harmless, you can ignore it.

Please check stderr.log and follow our 503 trouble shooting guide. https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:php:503-errors

Maybe some problem with the PHP7 binary, you can try run the PHP7 binary see if you get any error, you can also check stderr.log .

Yeah, you can reproduce it by reinstalling ea-apache24 rpm. We have added more protection against it. Please try update to the latest build of 5.1.11 with command /usr/local/lsws/admin/misc/lsup.sh -f -v 5.1.11 see if it happen again or not.

Ok, guys, mod_passenger based CloudLinux ruby/python selector support has been added to 5.2RC1, please help us test it. The steps required, is make sure ruby/python selector works properly under Apache (follow CloudLinux instruction to install required packages) install/upgrade to 5.2RC1...

Have you upgrade LSWS server and Magento LiteMage extension to the latest version? after making SSL configuration change, have you purged cache?

50x errors may not related to the rewrite rule. if it is 503, please follow our PHP 503 trouble shooting guide in our wiki.

Unfortunately, it is how a dummy web cache works, you can not expect that cache will update following the updates in original server, unless you purge it manually. https://support.cloudflare.com/hc/en-us/articles/200169246-How-do-I-purge-my-cache- Cloudflare support strong etag, but it has...

Are you using a trial license? Maybe it reach the maximum trial limit.

SecRemoteRules is not supported yet.

Yes, the email message should be updated. Right now, you only got the warning.

You can use Apache style directive for the HTTPS vhost to enable HTTP/2 only. by default, spdy and HTTP/2 is on.

HTTP/2 should be enabled with the default cPanel HTTPS setup. HTTP/2 is picky about cipher used, if user customize the cipher, it could affect HTTP/2.

It is not the immediate to-do list, probably in early 2017.

could be, just run our script again to fix it.

it should work with litespeed enterprise.

And use our wordpress cache plugin. https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cpanel:whm-plugin-lscwp-management

put it in a userdata include configuration file should work.

LVE limit is for PHP. processes not for litespeed server process. each account should be able to have 200% usage.