Search results

The HTTP/2 over clear text was off by default, probably hard coded to off now. Need to make it configurable. Will add that in 5.1.8 release.

Server may double the limit to 240 for 2-CPU license. So, you can increase PHP_LSAPI_CHILDREN if need. But, you may want to check why got 1240 running PHP processes, is it true and normal?

Definitely within this year. we are building something to match mod_passenger functions.

if the certification has an OCSP uri, then server will use it automatically, if not, it will use the default URL. Looks like server cannot locate the OCSP uri from the certification. Do you know which certification? have you verify it manually...

Yes, you can continue using that to combine JS and CSS, LSWS WP plugin should cache the result. If any problem, please let us know.

We have tested this rule before, it is working fine. You may need to turn on modsec debug logging with SecRuleDebugLevel 9 to check what is going on. Maybe the rule was bypassed for some reason.

You can customize a mod_security rule to detect that, use "drop" action, instead of "deny", then the connection and sub-subsequent connections from the same IP will be immediately dropped.

I wonder why they left Litespeed out, we have at least more than 20% of HTTP/2 market share, if exclude contribution from CloudFlare, we are about head to head with nginx. Instead, they test some non-production ready/toy HTTP/2 servers. :-) By design, HTTP/2 may be vulnerable to some kind of...

The one click update should take care of everything for you, there is no need to build matching PHP with EA4, all are ready-to-use rpm packages. You can try updating to the latest the 5.0.19 build see if it can take care of everything. /usr/local/lsws/admin/misc/lsup.sh -f -v 5.0.19 If it...

can you please try again? I have no problem with that link.

We are able to identify and fix the problem.

Please send us temp root access via PM or our ticket system.

If your C++ app runs in its own process and communicating with front-end web server through WebSocket, there is no API call required between you C++ app and litespeed server. If you plan to use Nginx as reverse proxy, you can use LiteSpeed in the similar way. If you want to embed your...

no worry, major improvement for 5.1 is in mod_security. and you can revert back anytime.

Moved. Absolutely, you can upgrade from 5.0 to 5.1 or downgrade from 5.1 to 5.0 at any time. /usr/local/lsws/admin/misc/lsup.sh -f -v 5.1.7

compare phpinfo() output with cage enabled/disabled, fix the difference. maybe php.ini was modified. Or, PHP selector switches PHP to another version. PHP selector only works when cagefs is on.

something missing in the cage, it is not because litespeed. Please try cagefs_ctrl --force-update

Are you talking about CloudLinux Ruby/Python/NodeJS selector? We have that on our to-do list, but lower priority. Is NodeJS your main concern? mod_passenger is a big project. It is a majro effort to make LiteSpeed compatible with mod_passenger. we need to evaluate the amount of work involved...

Looks like the gzip compression problem has been fixed with latest LSWS build . I do not get error with curl any more and pagespeed insight test finish without error.

global cache directory wont be used for vhosts with their own cache directory. you can use /dev/shm if you want, server reboot will clear it. server creates those directory automatically with correct ownership, no need to worry about that.