Search results

then try killall -9 lshttpd Then ./lswsctrl start

The execution of the rewrite looks correct. When result is 1 or 2, means the pattern has been matched. /100-laine-vierge was rewritten to "/". Have you configured those rewrite rules at vhost level? It will affect some PHP _SERVER[] variables as we made some change to match Apache's behavior...

Please do ./lswsctrl stop ./lswsctrl start or ./lswsctrl restart

You can use rewrite rule to tell LSWS to proxy request to the target Apache instance. What you need to do is to define a "Web Server" external application from LSWS web console, with name of "127.0.0.1:82". Then define a rewrite rule like RewriteRule (.*)\.cgi$ http://127.0.0.1:82/$1 [P]

Check lsws/autoupdate/ fold see if the 3.3.15 package is still there. It is available on our web site as well.

litespeedtech.com has been on 3.3.18, our joomla installation still works.

Can you turn on RewriteLog and check the error.log? Actually, there is a change in 3.3.17 which affect PHP environment variables, PHP_SELF, SCRIPT_NAME. It should not affect rewrite rules.

Where did you install LSWS to? you may have permission problem if you install to a user's home directory and did not choose to run web server on behalf of that user. Install it to /opt/lsws or /usr/local/lsws if you can.

What is your OS? 32bit? 64bit? The updateagent is not directly related to admin interface. Which version of LSWS are you using?

LiteSpeed can pass certain request to backend Apache running on a different port. http://www.litespeedtech.com/docs/webserver/config/general/#apacheHandledContent For example, you have Apache run on port 78, in LiteSpeed, "Apache Port Offset" is set to "2", so LiteSpeed will run on port 80, if...

change it from command line with lsws/admin/admpass.sh

LiteSpeed Web Server 3.3.18 has been released This release is mainly to support a new feature in cPanel. Download LiteSpeed Web Server View Version History

That's normal, each PHP process is configured to serve 500 requests then quit. It does not affect anything.

Yeah, just change version number in that file.

If hardware a dynamically allocated, I think it may not work well with LiteSpeed, because it may void the license key due to hardware signature changes. If EC2 allocate fixed hardware to your service, it may work. I think it may require a different licensing model to make it work well with...

The truss output shows that the connection was closed immediately, maybe due to protocol error. Maybe you can try the 64bit version if it is a 32bit/64bit compatibility issue.

Yeah, some opcode cache is not suexec friendly as it requires all PHP processes forked off one parent process. eaccelerator may be better as it uses a on disk cache which can be shared by all PHP processes.

Bash may not available by default, even on some solaris distribution. Maybe use if [ -f ... ]; then instead to make it compatible with most shell.

This configuration can be overridden in the same way as with mod_php. through the vhost configuration in Apache httpd.conf, php_admin_flag safe_mode off it wont work in .htaccess. if vhost is configured natively through LSWS web console, add above configuration to "Apache style...

Please download and try latest 3.3.18 package, should work now.