Search results

admin console->Serer->Request Filter->Request Filtering Rule Set please ensure all rules under it are disabled or just delete them.

can add the rules before #LSWS Cache

one website may be much different than another. if all of your sites response fast and working well, I see no reason why switch to litespeed or other solutions.

your VPS's memory is 4G: to my search just now, this 4G also the burstable memory. Hence should use Ultra VPS license. so not sure what "2GB actual RAM" means. just read the 1st column, so the concurrent connections is very low -- max 16 for your example output.

right, it's in wiki page: http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:multiple_phps_in_control_panel_lsws you have to use one of those suffixes to replace php53cache

can archive this by rewriterule easily(in .htaccess for example): RewriteCond %{HTTP_HOST} domainB RewriteRule robots.txt /robots_for_domainB.txt create a text file robots_for_domainB.txt under document root to block all requests; another robots.txt is for other domains.

these [NOTICE] messages not error message. don't help to identify the issue of "LiteSpeed is not up! Please check log file for errors."

can you try to install standard version on the same vhost but in another location instead of default /usr/local/lsws. then access the homepage, there is a demo page for Authentication, see if that works for you. the line read: "Authentication: Password protected content, use user name: test...

then this one: /usr/local/lsws/admin/conf/admin_config.xml

it's a bad idea to restart a web server every 5 minutes --- just what most admin try to avoid. anyway you can do it by cronjob. you can add a entry to /etc/crontab: */5 * * * * root /usr/local/lsws/bin/lswsctrl restart

compared with an local test box of mine, can you set some values of: <maxCacheSize></maxCacheSize> <cacheTimeout></cacheTimeout> for example, 200, 60 respectively.

ssh to your server, and edit the config file.

the apache document is here: http://httpd.apache.org/docs/2.2/mod/core.html#require so in your config file, <required></required> should be something like <required>user xxx</required> or <required>valid-user</required> /path/to/users should be a file, an sample: #cat /path/to/users...

update: error in LSWS error log 2013-05-21 16:51:51.427 [ERROR] [SSL] Config SSL Context with Certificate File: /var/cpanel/ssl/installed/certs/redoundspa_com_d3e64_fb0db_1400371199_76c8374e867edb375e150408ea192d0a.crt and Key...

please refer this thread: http://www.litespeedtech.com/support/forum/showthread.php?t=5545

did simple tests: it's default behavior of Apache as well e.g, the default is AcceptPathInfo Default http://httpd.apache.org/docs/current/mod/core.html Default The treatment of requests with trailing pathname information is determined by the handler responsible for the request...

it's one function of GD library --- http://php.net/manual/en/function.imagecreatefromjpeg.php recompile php with option --with-gd http://www.php.net/manual/en/image.installation.php

the new rewrite environ variable E=noabort:1 only available since 4.2.2 so please upgrade to 4.2.2 and try this solution: <IfModule litespeed> RewriteRule .* - [E=noabort:1] </IfModule>

must configure in above way. for this part: set $remote_addr_new $remote_addr; if ($remote_addr ~* ^::ffff:(.*)) { set $remote_addr_new $1; } fastcgi_param REMOTE_ADDR $remote_addr_new; may be able to use rewriterule to archive similar purpose: RewriteCond...

set up 2 listeners, one is ipv4, one is ipv6, but map to same vhost. just tested on an production server which run lsws, it works. please try, any issue please report back.