Search results

I guess #touch /var/cpanel/fileprotect mean enable fileprotect. it's best to ask cPanel about this question. if you get the reply, welcome to share back.

confirmed this one doesn't really purge cache: but after adding my.url.domain.com's IP, it has worked! i.e., #php purge_cache_byurl.php -r my.url.domain.com /hello.php IP-of-my.url.domain.com 80 the syntax is: /usr/local/lsws/admin/misc>php purge_cache_byurl.php Invalid arguments! Usage: php...

can you have the test first ? I'm a bit confusing too. the test is the King.

is ok to access the server ? at this point there is no clue unless trouble-shooting on the server directly.

it's weird. force delete the whole cache by #rm -rf /cache-folder/* then access /hello.php, is its value refreshed ?

200 mean purge succeeded, but you said it's 400 ? after above purge success, access /hello.php again. is its value refreshed ?

yes, it's the cache policy and looks ok. so when you run at command line: root@MYSERVER [/usr/local/lsws/admin/misc]#php purge_cache_byurl.php -p my.url.domain.com /hello.php the output ?

it should work. what's the cache policy ? and #curl -I my.url.domain.com/hello.php always has response header X-LiteSpeed-Cache: hit ?

maybe run this command : # touch /var/cpanel/fileprotect instead of /scripts/disablefileprotect ?

here's the list we have experience with lscache: https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:lscache enabling lscache for particular URL is relatively easy, but the difficult part is business logic: which URL under which condition can be cached or can't may need...

yes. I did test on a litespeed server: /usr/local/lsws/admin/misc>php purge_cache_byurl.php Invalid arguments! Usage: php purge_cache_byurl.php -(r|p) domain url [server_ip] [port] -r method option: Refresh cache (use stale cache while updating cache) -p method option: Purge cache...

this is wrong. should be tester:nobody please refer http://www.litespeedtech.com/support/forum/threads/solved-404-not-found-on-all-domain.9918/#post-82332

I think wildcard is not supported -- you have to specify the full URL. however you can delete all cached files by OS command, e.g.: #rm -rf /lsws-cache-folder/*

please provide the ssh access to the server, I can login and trouble-shoot. click on my name, choose "Start a Conversation"

is any special character in the uploaded image name ? try to upload a simple name image like abc,png, there will be problem as well ?

please find /usr/local/lsws/admin/misc/purge_cache_byurl.php to see if that works fine, it's the latest version.

LSWS 4.2.23 or LSWS 5.0 ? if it's 5.0, try to force re-install at command line: #/usr/local/lsws/admin/misc/lsup.sh -f -v 5.0 and access port 7080 again, see if the issue has gone.

which mode lsphp5 are running ? suExec or non-suExec ? please refer this wiki http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:php:concurrency 70 is used to control php concurrency in lsws, not in any php settings(php.ini etc) should be no problem at all. and have no...

this looks a good approach. when "restrict wp-login.php either by password or to the user's IP address", normal user still can log in wordpress while bots can't so php process won't start to process the illegal login. just wonder why need disable access to xmlrpc.php at the same time. is...

so during attack, this URL is not accessible to normal user as well in theory implementing this feature in web server level looks possible, and looks possible implemented in a wordpress plugin ( or maybe one is there already ? )