Search results

yes. it's enabled by default. and as far as I know, no way to disable it. you can use curl to test: #curl -H "Range: bytes=10-100" URL-of-a-static-file to download 10th - 100th (total 91 bytes) of the file.

Yes, you can log a ticket and we can log in your server to take a look and better follow up.

Just FYI, this is not a formal document or API, but can get latest build's info. package time stamp -- Last-Modified ~>curl -I https://www.litespeedtech.com/packages/5.0/lsws-5.2-ent-x86_64-linux.tar.gz.lastbuild HTTP/1.1 200 OK ETag: "2-596814f3-565c8f9a9e5b1040" Last-Modified: Fri, 14 Jul...

Sorry, this is a known bug of 5.0.18. have to upgrade in command line: #/usr/local/lsws/admin/misc/lsup.sh -f -v 5.1.17

https://en.wikipedia.org/wiki/ICO_(file_format) WebAdmin Console -> General -> MIME Settings: $SERVER_ROOT/conf/mime.properties ico: image/vnd.microsoft.icon but according above wiki, it looks like image/x-icon is better :) please try either way: 1. in WebAdmin Console -> Tuning -> GZIP...

what's your setting: lsws web admin->Server->Security->Force Strict Ownership

you can switch to apache, see if the issue exists. this is the quickest way to identify it's a litespeed specific issue.

for new installation, please follow this is our goal -- if all can be done in GUI, that's ideal. I think is more for old installations -- lscache feature is introduced on lsws 4.0(March 2009. per release log: https://www.litespeedtech.com/products/litespeed-web-server/release-log-archive)...

there is a wiki page about LSPHP_MaxWaitQ : https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:php:maxwaitq-limit

please refer https://www.litespeedtech.com/docs/litespeed-sapi/php/configuration you can configure LSPHP_MaxWaitQ to prevent / mitigate / reduce the impact of such sudden traffic( ddos alike).

name servers are not set within any web server, include litespeed. they must set ready before install / setup web server. who is your web site host ? contact them. your web site host may be same as your domain host, or different one.

#chmod o+x /home/username/lscache may be able to have those error disappear. however I think it's ok not to backup /home/username/lscache since they are cache files and keep updating all the time. so should be ok to ignore the error.

is it working under apache ? if it works with apache but not with litespeed, we'll look into it.

it just means "cache result returned by php", that's just what lscache does. for litespeed, means 1. your litespeed license need contains lscache option (for 2-CPU and above license, it's included) 2. enable lscache for php. for wordpress, mean install "lscache plugin for wordpress" and enable it.

if can't connect it at all, it should be firewall issue. please ensure the server open port 7080 access to your IP. if forgot username/password, you can reset password by /usr/local/lsws/admin/misc/admpass.sh

I think no need change /opt/cpanel/ea-php56/root/usr/bin/lsphp etc to /usr/local/bin/lsphp since cl_phpselector already defined. in Script Handler, just select cl_phpselector for suffix "php". restart lsws. please inform if it's working or not.

basically, the issue is that you can't establish a http connection with the web server. there are many factors will result this. poor network connection, server side mod_security etc. probably you can further identify this issue by check the logs at the web server side. if network ok, you should...

have you enabled per-client throttling like lsws web admin->Server->Security->Per Client Throttling ?

performance wise, there is no difference I think. it looks like SetEnvIf can be regarded as a subset of mod_rewrite(though I haven't researched about it at the moment). maybe sometimes SetEnvIf is easier to understand, so it's not bad to have another choice for the user.

I think it's because you haven't defined a virtual host listen to port 80. i.e., you've defined virtual host like <VirtualHost *:443> ServerName www.transferyourpension.com but not define <VirtualHost *:80> ServerName www.transferyourpension.com and those rewrite rules are under...