Search results

4.1.1 package has been updated.

Please download and upgrade again, it should work now.

LSLB does not care about the physical locations of the backend server, as long as it can be reached. However, if you do load balancing over the WAN, network speed and stability is likely to have more impacts than load balancing over a fast LAN.

the web console is similar to the web server product. It can be easily done, the LB provide a lot more options. you should download and give it try. need to read the tutorial and pop up tips.

Yes. works with any web server backend.

For cache function, it is much more flexible than just a few configuration options. Please read http://www.litespeedtech.com/support/forum/showthread.php?t=4719 You can add reverse proxy IP as trusted IP at server level http://www.litespeedtech.com/support/forum/showthread.php?t=4719 You'd...

You should get rid of varnish and use LiteSpeed cache instead, it works equally well if not much better than varnish. You cannot expect anti-DDoS to work when you have varnish running in front of LiteSpeed. The reason for blocking reverse proxy IP is that LSWS do not even able to parse the...

Just download 4.1.1 and manually upgrade again.

It is a PHP internal bug causes PHP to crash while processing IPN reply. You can try a different version of PHP.

You need to use 4.1.x release to get mod_macro support.

$VH_NAME is used in which configuration? Please give an example.

We will address this in next build of 4.1.1, we use symbolic links to easily switch between different versions. As long as the link and the target directory is owned by root, it should be fine.

You should remove the [P] flag, it is for proxy, not sure what apache will do, but proxy to the same server is a bad idea anyway.

That's because the request is not finished processing, For some buggy script, even though the "Content-Length" header is set in response, the script may not exactly follow it, so chunked encoding is used. It will be addressed in next build of 4.1.1 for your specific case.

That's likely is a bug. we need to investigate more. Possible to login to your server to take a look? Are you sure there is no .htaccess under /home/user and /home/user/domains ?

Looks like a infinity loop exhausted stack or heap memory. have to be addressed from PHP internally. You should report this bug to php.net

We need to do more analysis on the log file, please either send the log file to bug@litespeed..., or let us login to your server to take a look.

We fixed a few bugs that cause 4.1 crash, however, for this particular one, we still need a more detail report running LSWS under valgrind.

Can you check the request header with firebug or liveheader, what is the value of REQUEST_COOKIES:PHPSESSID ? Also, please enable LSWS debug logging and Mod security debug logging SecDebugLogLevel 9 It should show what exactly happened.

add concurrent_php to ignored Modules. http://www.litespeedtech.com/docs/webserver/config/general/#apacheIgnoredModules 4.1.1 added that by default.