Search results

permission problem with parent directories I think. Those files are created by lshttpd running as root, while lshttpd running as www cannot open them for writing.

You need to define a vhost level php external app and script handler.

link to 4.0b1 package has been published in another thread.

This is the first public beta release of 4.0, linux only http://www.litespeedtech.com/packages/4.0/lsws-4.0b1-ent-i386-linux.tar.gz http://www.litespeedtech.com/packages/4.0/lsws-4.0b1-ent-x86_64-linux.tar.gz You need a trial or 2-CPU license key to try out the cache function.

Make user's home directory owned by root with sticky bit set. create a doc root directory under the home directory owned by user. create a log directory under the home directory owned by "www:user". ftp should be able to read log files while user cannot remove the log directory.

Will a symbolic link work? user only need read permission on that file I guess.

You should use the geoip's PHP module instead, we do not want to reinvent the wheel in this regard. :)

check if there is any cron job that tries to stop lshttpd process, there are some security scripts doing that.

If you use LiteSpeed together with Apache httpd.conf, LiteSpeed will follow "User", "Group" or "suexecUserGroup" directive in httpd.conf instead of using UID of docroot. Litespeed write log file as "www" because the child lshttpd process running as "www" need to dynamically open/close and...

Not necessary, Update the server level access control list http://www.litespeedtech.com/docs/webserver/config/security/#accessControl_allow

It has been set in the SERVER[] variables already, like mod_geoip does. SERVER["GEOIP_COUNTRY"], etc. please check the mod_geoip manual for the name of environment variables.

Maybe you need to uncheck "monitor httpd" under service manager page.

Rails' memory footprint is very big, it really up to how much memory you app uses. I think the best choice for you is to combine your apps if possible. LiteSpeed can have the app start on demand, your backend apps can start this way if does not need to run all the time. If you only need one...

Maybe your browser does send the password by default, only when get a 401 error it will send it. Don't worry about it.

Web console use cookie for login, not HTTP authentication, and it won't log that to error log either.

I have no clue, any part of your site require login as "admin"? Maybe it due to password change and the browser still send the old password it remembers?

yes, it is.

that means that somehow LSWS received a internal redirection request the same URL. You can check your access log for URL causing this problem.

log analyzer like awstats or webalizer should do the job.

Its value is the remote IP : port that LB saw. If "X-Forwarded-For" exist in the request that LB receives, LB will append remote IP to it. You can use the last address listed if you want. If you set the option in my previous post, LSWS will set "REMOTE_ADDR" to the first IP listed in...