Search results

but... hosnestly, I found that running lsphp52 with or without -c from Cpanel /var/spool/cron/username will produce this error : but perform that command directly from console will works as it should be. so I have to delete all of Cpanel interface crons and move them to crontab -e :(

once again : thank you very much, NiteWave you and -c are so awesome

Hi NiteWave thanks for your explanation, I will try that. By the way is that /path-to-lsws/fcgi-bin/lsphp-5.2.17 without -q will have a chance to use custom php.ini from PHPIniDir ? Because right now I found alternative solution by using /path-to-lsws/lsphp52/bin/php but it seems using php.ini...

I did dual php (5.2.17 and 5.3.x) and works fine with all http://website with additional .htaccess AddType directive. But running cron job (php -f or -q /my-path/script.php) still execute php as 5.3 :confused: I have try /path-to-lsws/fcgi-bin/lsphp-5.2.17 -q but resulting an error : Could...

i am sorry, NiteWave, but that can't be done. some websites need to exclude some of specific atomic modsec rules to get their site working. because that was not just .* but either to website path for an example : <LocationMatch "/adminpanel/sidebar_option.php"> SecRuleRemoveById 34xxx...

hi NiteWave, thanks for your response. LocationMatch are placed on : /usr/local/apache/conf/userdata/std/2/username/ and /usr/local/apache/conf/ those works fine on 4.2.2, so I revert back to 4.2.2 to solve this.

I've found that : <LocationMatch .*> SecRuleRemoveById xxxxxx </LocationMatch> won't work with 4.2.3 :confused: please fix this.

hi brr, you might want to try "SecRule REQUEST_HEADERS:User-Agent" than "SecFilterSelective HEADER_USER_AGENT"

by the way I hope next build of lsws will revert back to neat old fashion of lsws processing as bellow : because newest build showing too long line of process :

thank you very much, George. it work flawlessly now :)

any update yet? because using 4.2.1 with Atomic rule set makes lsws restart oftenly :(

Hi NiteWave, Thank you, I will waiting so much for that next build. By the way : ----------------- lsphp5:/home/username/andsoon ----------------- will be more neat than : ----------------- /usr/local/lsws/fcgi-bin/lsphp5:/home/username/andsoon ----------------- that you are using now on...

any help from anybody?

Latest 4.2.2 build won't block with this simple rule : #### SecRule REQUEST_URI "/any-folder/.+/filename.\php" "id:20202020,rev:1,severity:2,msg:'must be denied',deny" \ #### Performing /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.1 and then the rule above did block filename.php as it should...

thank you, NiteWave. you could try another theme to reproduce the issue. because most of reporters doesn't use default theme. and as usual, switching to apache will bring normal looks comparing to litespeed. happy new year anyway :)

I receive plenty of reports from wordpress users regarding their broken theme after using wp-minify plugins. I have found that litespeed seems unable to translate css/js compression as this screesnhot bellow : >>> http://imageshack.us/photo/my-images/35/litespeedvsminify.jpg/ please release a...

new fresh instalation today, and i've got this : it is brand new colocation box with brand new cpanel (php 5.3.19) and also brand new lsws license and brand new lsws 4.2.1 automatically from whm plugin. i thought this 4.2.1 has something wrong inside. would you mind to rewrite litesped whm...

it's been three days now using lsws 4.1.13 and lsapi 6.1 to all of my boxes. no more error 503 emails from cloudlinux boxes after that.

I have three boxes using cloudlinux. one of them using lsws 4.1.13, and lsws 4.2.1 for others . but they are all using the same lsapi 6.1. and they are together keep sending 503 error emails. sometimes 503 errors stoped after setting Memory Soft Limit to beyond 650 Mb. but i have to stop...

hi there Alfa-Host, my current kernel is : 2.6.18-408.8.2.el5.lve0.8.61.3 #1 SMP Wed Jul 11 06:49:35 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux I didn't experience any crash which makes me to do hard reboot. I just got 503 error emails which told restarting lsws many times per day for...