Search results

I believe that there is a admin/ directory under the public directory, otherwise, LSWS will not redirect. You should either remove it, or rewrite "/admin" to "/dispatch.lsapi" with a rewrite rule at vhost level, it will tell LSWS to skip the checking of admin directory, thus the redirect.

It is really up to you. ;) To me, it will be much easier to parse the bytes log than the XML file. log file is pretty small and can be deleted after processing, diskspace is not a concern to me unless your sites were getting >300hits/secs. As to running out of file descriptors, OS limit is can...

If you want to limit the total bandwidth usage, you do need to run a backend cron job to update total bandwidth usage from the cPanel compatible bytes log file, and ban the account from a .htaccess with a rewrite a rule. Just check out how cPanel does that, should not be hard to duplicate that...

You are correct about those. There is no direct match for mod_cband, however, our IP level bandwidth throttling and connection accounting is pretty close to what mod_cband does, just not apply a per-vhost limit, but in real world use, per IP throttle usually has similar end results. For...

Is it for dynamic contents or static files? Anyway, it is hard to do with either one. My suggestion is to avoid distributing the same file on multiple servers if you can. With LSWS, you probably don't need to do, one server should be more than enough to serve static file with any kind of volume...

Are you talking about the import Apache configuration during installation, not the "Using Apache configuration" feature, right? The former import Apache configurations into LSWS configurations and you can customize it from our web admin console. The later just read Apache configuration file...

Digest authentication is not supported yet.

This directive is not supported.

I see. I updated the package to force "UseCanonicalName on" for FrontPage Extensions. Please give it a try. Thanks.

The number of processes running as that user on the entire server.

You need to increase process soft/hard limit for lsphp external app.

When lsphp dies, try starting a lsphp from command with the same user that LSWS starts lsphp. And you can check error.log and stderr.log see if anything suspcious.

Realm editing in vhost template does not work, the reason is that the path name may contain a wild card like $VH_ROOT to let each vhost uses it own realm file, so editing is disabled intensionally. Just instanciate a vhost and edit your realm from vhost configruation.

I am not sure, maybe you can check the process limits in LSWS configuration, if apache, LSWS and lsphp run under the same user. Try start lsphp under the same user from command line and see if you can start it when that happens. LSWS 3.0 should be able to replace apache completely for a cPanel...

Just click the name of the user file.

For #2, it is a work around as expected. I just wonder why Apache can do it without domain.com:80? I thought it was "UseCanonicalName on", so CGI env SERVER_NAME will be always set to "www.domain.com" when accessed through http://doamin.com/... , and I just added support for UseCanonicalName in...

It is the intended behavior for the reason you mentioned already. To remove the old version, do lsws/admin/misc/mgr_ver.sh -d 3.0RC1

To use PHP_LSAPI_CHILDREN, just set it as a environment variable to match "Max Conn" value, set "instances" to 1. The benefit of doing this is that all PHP processes sharing the same block of memory for the opcode cache, but all PHP processes will be started statically, not on demand...

I see. The second redirect is because of missing trailing slash for the admin directory in the URL, LSWS does not check the "X-Forwarded-Proto" header. This extra redirect can be avoided. You can either add a matching context for URL "^/admin$", forward it directly to mongrel, tell LSWS...

It is a issue with the external load balancer and mongrel/Rails, LiteSpeed is just the messenger. :-) Mongrel or rails need a special HTTP header "X-forwarded-Proto: https" in order to know the connection is SSL, when LiteSpeed handle the SSL connection directly, LSWS will set the header, so it...