Search results

you can go https://store.litespeedtech.com/store/cart.php to know about license types(VPS,Ultra VPS, 1-CPU etc) and price, LSCache option need additional $6/month for VPS/Ultra VPS license.

update 2: looks my first reply introduced more issues. I did tests on proxy cache, after remove RewriteCond %{REQUEST_METHOD} ^HEAD|GET$ cache purge just works as expected. now I tend to agree with you: either without "RewriteCond %{REQUEST_METHOD}" or "RewriteCond %{REQUEST_METHOD}...

update based on my tests: 1) "curl -X PURGE " works, so no need rely on purge_cache_byurl.php cache purge wiki: https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:lscache:purge please note "Whitelist source IP to issue PURGE request", so need run PURGE on the...

PURGE has some limitation or restriction, to prevent anyone from anywhere can PURGE a cache page. please try /usr/local/lsws/admin/misc/purge_cache_byurl.php to purge the cache. while I'll mimic your env and try to reproduce the issue.

how about remove PURGE method ? i.e., change to RewriteCond %{REQUEST_METHOD} ^HEAD|GET$ RewriteRule (.*) http://<varnish>:6081/$1 [P,L,E=Cache-Control:max-age=3600]

the problem is in httpd.conf for normal domain/sub domain, in <VirtualHost> section, ServerName domain.com ServerAlias www.domain.com for wildcard subdomains, should configure as ServerName domain.com ServerAlias *.domain.com

I managed blog site which is WP multisite installation without any problem. can you provide the litespeed web admin ( :7080) and the backend of WP ? I can take a look to see if can find anything.

the standard way to trouble shoot a litespeed issue on a WHM/cPanel server: switch to apache, see if the issue exists as well. if exist, resolve it first. then switch back to litespeed, most likely the issue will be gone. (if you've rebuilt php using easyapache, then before switch back to...

maybe you can ask your store programmer

wiki page for 503 error: https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:php:503-errors is it possible to export production on command line ? if possible run it and see if export will succeed or fail, to compare with running it through admin panel.

may be enough. may need modify php.ini to add a line like extension=pgsql.so I checked one old "CentOS release 5.11 (Final)" box, lsphp5 support pgsql, here's the full build info from phpinfo: Configure Command => './configure' '--prefix=/usr/local/lsws/lsphp5' '--with-libdir=lib64'...

please refer: https://www.litespeedtech.com/products/litespeed-web-server/editions while standard version is Hosting control panel compatible Apache compatible but Limited to 5 Apache virtual hosts Use with hosting control panel plugins not supported so in practice, standard version won't...

just do a fresh-install with standard version, as if it's a new server.

quick and short update: it's because https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:common_installation:advanced#cache_policy_settings strictly follow the wiki to fill server level "Storage Path" with "/cache/storage/path", but not crate the path manually. another...

please try again ... one of our servers got problem ... already fixed. if still problem, please report here.

please PM the URL of the wordpress website. I'd check if the cache working for wordpress home page.

have you enabled lscache successfully ? how to check: https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:lscwp:installation#testing

I did a test, looks working after configure as below: a) virtual host -> Context, Add, select type Static b) URI: /subdir-1/ Location: subdir-1/ Allow Override: Check FileInfo Apache Style configurations:AddHandler application/x-httpd-php7 php

the issue has been identified and able to upload 900M files without issue. it's not lsws version related. ownCloud is a php package. the server is a typical CloudLinux + WHM + litespeed server with hundred of accounts running php in suExec mode. 1. reproduce the issue once uploaded a 60M...

if lsws done, admin panel will down as well. please specify what tests you've run to bring down lsws.