Search results

my tests shows litespeed 5.0.8 behave same as apache. https://httpd.apache.org/docs/2.2/mod/mod_expires.html please check AllowOverride directive in httpd.conf, if see "AllowOverride None", try to change to "AllowOverride All", see if any difference. also, check if "RewriteEngine On" exist in...

yes, that mean already finished. then just restart lsws, new build lsphp-5.3.29 should be picked up. however, if you use cloudlinux's alt-php, no need "Build Matching LSPhp", since they already build ready by cloudlinux. you just need configure lsws to use alt-php.

confirmed it's a open litespeed 1.4.13 issue. but tested ok on lsws 5.0.8 reproduce steps: 1. vhost php Script Handler set to vhost level external App: lsphp 4.4.9 server level php Script Handler set to lsphp 5.x 2. define a "Static" context in vhost (note: not LiteSpeed SAPI context)...

can you try following https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:lscache:wordpress#website_level_settings to update your rewrite rules. e.g., CacheEnable public --> remove RewriteCond %{REQUEST_URI} !wp-admin|wp-login.php|wp-cron.php|bla|otherpages|etc ->...

message from dvsDave: "I've disabled the addon until the new update promised today by Slavik is delivered. Gonna work on moving to https (since I can run http/2 with litespeed) in the meantime." not sure why seeing this as spam. "new update promised today by Slavik?" not read it yet ...

the plugin is developed by XenForo developer and has been working since then. I noticed you left message on https://xenforo.com/community/threads/xenforo-litespeed-cache.65815/page-13 "I went from 4.2.21 to 5.0.7 and now the real-time stats say that it's not caching anything? Anyone else had...

Sorry for late response. can you give web admin access ( :7080) in PM, so we can work closer.

great use case :)

the web admin console for both litespeed are similar, most part are common. you can post the picture here. how did you add "Expire by Type" in open litespeed GUI ? if you want to add a expire header for .php, like Expires: Mon, 09 Nov 2015 09:16:13 GMT base on my previous test, you may try...

not very clear about the issue you've described. since it's about open litespeed, and this forum is for enterprise litespeed, so by the chance I did some tests on apache and enterprise litespeed. just an reference for your question while not direct reply. on both apache and litespeed (not...

please refer https://www.litespeedtech.com/docs/webserver/config/general#useIpInProxyHeader not sure if X-Forwarded-For header can be used in your case.

3 or 2 or 1, you can try all of them, then you know what's the best for your website. fail2ban should be no way to ban original IPs ? however it can send those IPs to CloudFlare to ban them.

it makes sense to send IPs to Cloudflare to block. but why use fail2ban ? all the http connections is from Cloudflare, use fail2ban(or iptables), you can only drop Cloudflare IPs. since Cloudflare server is in front of lsws, and actual connections are between CF and lsws, I'm not sure how...

as it said "Fine tune anti-DDoS configurations and set up a script using iptables to automatically block attacking IPs detected by web server." just what you've tried, but make it success.

in short, when lsphp5 in non-SuExec mode, use when in suExec mode, use more info -- https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:php:which_php_setup_am_i_using

Wow, an thread 1 year 10 months old! Header set X-SGServer "web2" should work on lsws 4.x as well ? anyway I did tests just now, now lsws version is 5.0.7 1. Header set Header set X-SGServer "web2" works at server level, both litespeed and apache 2.Header unset Server litespeed: works at...

for 1) I'm not sure. our other staff may reply. 2) this is a FAQ -- the standard answer: default setting already optimized and apply for most cases. no need change them unless you encounter any specific issue and need change them. a good way to monitor lsws's performance is lsws web admin ->...

just now visited your forum for a while. only 1 pattern is observed domain.com/image.php?u=8125&dateline=1406313471&type=thumb it's used to display forum member's avatar ? if so looks like it can be cached. -- you can try it anyway. please confirm if it's used to generate random images to...

so we assume step 1 has been done correctly. the problem occur at step 2. can you find out any info in log(error.log and stderr.log) when submit to google ? the time stamp should be right after 01:10 every day.

looks like 2 steps: 1. daily sitemap by vBulletin is it saved anywhere ? so can check if it always generate updated sitemap 2. submit sitemap to google daily see if can identify which step has the problem.