Search results

Yes, Litespeed is capable of handle HTTP2 upgrade when SSL is not used. Just no browser does that, all require SSL.

So, user has problem with 4.2.22 as well? If Sucuri does HTTPS proxy, you may need to turn off SSL Renegoication protection, as Litespeed may block one IP if excessive HTTPS connections have been made from one IP.

Please tell us more details about the browsers, we will try to reproduce it ourselves. chrome is strict with ciphers when Http/2 is used, the error message tells you that. but if a browser does not support HTTP/2, only support SPDY, SPDY will be used.

Is it easy to reproduce? or happen in random? What browser are you using? Does it use SPDY? HTTP/2?

Need one configuration in .htaccess The Magento store need to install LiteMage module though. If interested, please contact sales for a free trial.

LiteMage allow user to purge cache from magento admin console under "Cache Management". Rarely need that as LiteMage can purge stale page accurately.

current solution is to set the per vhost cache storage path under user's home directory, user can delete it himself if need.

This kind of feature is already on our road map. Adding different caching rules for different web application is relative easy, the difficult part is to purge outdated cached objects timely and accurately. For wordpress, may have to install a cache purge plugin.

Please force reinstall 5.0RC3 to get the latest build. it should have been addressed a while back. /usr/local/lsws/admin/misc/lsup.sh -f -v 5.0RC3

Please check http://www.litespeedtech.com/support/forum/threads/error-500-internal-server-error-after-update-to-5-0-rc3.11269/

Yes, that's normal.

Well, if you have Xcache, you do not need to enable opcache. only need one opcode cache. You can decrease it to 5, no problem. 503 errors are caused by PHP crashes.

Please check your opcode cache configuration and usage, it is a waste if you reserve too much memory and actually uses a little. check the number of lsphp processes running. Check your "top" output to find out the process using too much CPU/memory.

Please wait for our LiteMage cache solution, it is in our final QA stage. In the mean time, I'd like to check the crash, can I login the server to take a look at the core file? Please install gdb with "yum install gdb"

reorder the rule

mysqldump will lock out all other clients, basically, blocks PHP.

just check and run it from command line make sure it works.

You need to install more 32bits libraries to make the 32bits /usr/local/lsws/admin/fcgi-bin/admin_php5 binary works under centos 7 64bits.

First thing, make sure you have "RewriteEngine on" in the .htaccess, assuming the rules is in .htaccess. Please turn on rewrite logging by adding "RewriteLogLevel 9" to the Apache vhost configuration if LiteSpeed read Apache configuration. Then check error log for rewrite related log entries.

The abort requests are most likely caused by front-end load balancer closes the connection to web servers. Maybe the request take too long to process, you need to check the PHP processes running on that server by that time. I think PHP was hanging on something. if by that time, the site is...