Search results

We raise the limit to 250K in 4.2.12, you can give it a try /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.12 However, we recommend avoiding large htaccess when possible. It may cause performance problem.

version 4.0.1 is the old pirate version, hosting provider installed it for you? which provider?

Can you please tell us the Apache configuration you are using. What has been set at global level and at vhost level?

Please check the log file for the reason of 404 errors. You can run LiteSpeed parallel to Apache with port offset 2000 , check if everything works on port 2080. You can turn on debug logging if need.

You should avoid using "?" in the rewrite target if it is not intended for query string part, it will definitely break Apache rewrite engine as well. According to the spec. If you have to, you can try URL encode it with "%3f".

Can you please confirm it is working with Apache? It could be the SNI, as LiteSpeed does not do SNI with HTTPS proxy backend, we are adding it now. We may need temp root access and the real domain name to verify the root cause.

Maybe the comment line causes LSWS to whitelist all IPs, treat it as "*". Try put only real IP in that file without comment, see if it is OK.

Looks like a bug in our mod_sec engine. We will give that rule a try in our lab. Do you have proxy in front of LSWS? What is in the whitelist.txt? please give us a short example. Which version of LSWS are you using? 4.2.11?

We will look into it. in the mean time, just download the package and run the install.sh to perform an manual upgrade.

You can follow our per-user php.ini setup, if you use cagefs, make sure the php.ini will be created inside user's cage. .user.ini does not work with lsphp, you can use php_value in .htaccess for that purpose.

You are asking if possible to serve content of a file without opening it. :-) We will do more testing to make sure that server does not keep the file open for reuse. You can check if new NFS client implementation see if have implementation that does not rely on silly rename.

Just go to your client area to release those two licenses.

you need to remove the "dl" directory after you added the "Alias", if there is one. can be added to .htaccess under /home/fakepath/downloads

do not tell anyone about it. and there are ways to protect from direct access.

For security reason, LiteSpeed does not serve file out side the document root. However, you can use Apache Alias or Litespeed "Static" Context to assign a URL to that directory, then LiteSpeed will be able to serve files from that directory.

You need to fix file permission of /home/****/public_html/client/.htaccess, make it readable for "nobody" user.

For wsgiApp, you need to set "Instances" to 1. Memory soft/hard limit should be set high enough, Process soft/hard limit should be set high enough. check /usr/local/apache/logs/error_log and stderr.log for related errors.

Please upgrade to 4.2.11 first /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.11 If the problem persists, we probably need temp root access to find out what is wrong. Please contact us at bug@litespeed...

How did you install it? How did you test it and believe it is not working?

Or, send a temp root access to bug@litespeed..., we can send you our IP if ssh access is firewalled.