Search results

Alright, I'll see if this is the last bug ( :) )before we can deploy LSWS in all cPanel boxes. Thanks.

I'm glad this latest 2.2.2 fixes it. - mailman is working ok (needed to force group to nobody) - users cgi-bin work again I hope this is the last surprise I'm going to get from the latest 2.2.2. ;) Thanks!

Another issue is that, every customer's script in their /cgi-bin/ is now 404. Everyone's script will always be read from server docroot cgi-bin (/usr/local/apache/cgi-bin/). I think this just comes up with the latest version or so.

OK, that fixes mailman issue. But wouldn't force running CGI as nobody group break other users' CGI scripts in the system?

Have been running LSWS 2.2.x happily in one busy production cPanel box for a week and no single issue comes up. :) Today a customer reports that when he accessed mailman interface through "http://domain1.com/mailman/admindb/list1_domain1.com", he got a 403 Forbidden error. I checked and...

No, that's the whole thing. Apache works ok with that file. Lsws just reports 401 and the log says: x.x.x.x - - [12/Sep/2006:21:20:33 +0700] "GET /path-to/admin/index.php HTTP/1.1" 401 396 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6"

Well, not quite there yet. Switching to lsws still shows 401 without asking for authorization. This is on latest 2.2.1 and the .htaccess file in question look simply like this: AuthType Basic AuthName "Restricted Area" AuthUserFile "/home/username/.htpasswds/admin/passwd" require...

Great, I'll let you know in a few days if this is the last obstables for running lsws instead of apache in our production systems.

With 2.2.1 released, I don't know if this has been fixed or not. Can't see it in the Changelog. Thanks.

Oh, well well. I guess almost all customers use that kind of double quote in their .htaccess so I guess I better be waiting ... :) Thank you mistwang.

lsws 2.2, set to use httpd.conf directly. Everything else works nicely, except .htaccess from all virtual host. lsws error_log shows that .htaccess were detected, but it just refused to work. Something as simple as basic authentication such as: AuthType Basic AuthName "Restricted Area"...

Awesome! Very well done, guys. THANK YOU!

This is probably the last bit of features that I may need before deploying lsws in cpanel servers. Will be waiting too... :) 1. install lsws 2. build php with litespeed 3. config lsws to read httpd.conf directly 4. remove httpd from default runlevel & disable httpd from chkservd 5. enjoy...

Great stuff, but can't get it to work try putting rocommunity public above this line pass .1.3.6.1.4.1.8888 /etc/snmp/litespeed/sample.php

We have successfully ported our high traffic web site (ThaiLE.com) from apache2+mod_php to lsws+php-lsapi. This site has been serving about 3.5 million page view per day plus 3+ more million banner serving through lighttpd. In essense, it's a banner exchange web site with 3M+ requests per...

Actually, the thing I'm getting by doing this is a big reduction in memory and a moderate reduction in CPU usage by replacing apache+php with lsws+php. :) There are also a couple other servers that apache were replaced by LSWS completely. One of them used to run apache2 then replaced by...

Cool. Is there any ETA on this? Real cool. The way that cPanel suspends account is simply to put a rewrite rule into user's public_html/.htacces file: # cat .htaccess RedirectMatch .* http://main.server.host/suspended.page/ Options -Includes -Indexes -ExecCGI Well, seem like LSWS...

After many days of proxying from apache to lsws, there are still something of interest though. In "Use apache config" mode, does lsws capable of running php in suExec mode, or do we need to tinker with deploying lsphp for each vhost through External App setting in VH template section...

I am willing to help you with that. Just let me know what you're looking forward to. Well then I may be able to come up with something later.

I think this problem can be solved by adding .htaccess or appending to existing ones into user's public_html dir with a simple perl command. If you don't think this is worth implementing, then you can safely skip this and working on something else to make lsws compatible with cpanel, or...