Search results

or you can manually upgrade to lsws 4.1.18, see if the issue still exists.

for quick solution, just disable this rule: admin console --> Server --> Request Filter -->XSS attack does this happen on firefox only ?

since you set lsphp is not in self-manage mode. when php suExec enabled, only eAccelerator able to share opcode cache between processes, since the opcode cache is saved on disk.

how about: json = application/json the full path of mime.properties ?

Hi Mark, created a wiki page for your long-term concerns https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:mod_security-compatibility

is lsphp suExec enabled ? so match for apache + suPHP

it should be a PHP issue. google "php same session id", there return many results. to ensure lsphp read this php.ini. or check if lsphp5 is using /usr/local/lsws/lsphp5/lib/php.ini

it's not likely possible to add it in admin console. but you can always build any version of php at command line: http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:php:lsapi

quick solution: #chmod 777 /tmp/diskcache

it looks php suExec enabled: lsws admin console -> Server -> General -> PHP suEXEC: Yes then increase PHP suEXEC Max Conn from 10 to 50 (for example)

still can't find other problems other than CPU --- and the mysqld occupied CPU much. install XCache can reduce lsphp5 load a bit. has it installed? wait: Swap: 34996216k total, 1735756k used with 32G memory, why still swap use 1.7G ? swap will cause very slow response. since you still...

per the real-time screenshot, the bottleneck is CPU: Load 5.66 can you capture output of "top -c" ?

please refer http://www.litespeedtech.com/litespeed-web-server-editions.html

per your ps output, no php is running :) please just "grep php"

can you provide more detail about this ? paste output #ps -ef|grep lsphp under litespeed and similar output under apache(mod_php or php-fcgi etc)

if vhost is defined in http.conf, mod_security rules from http.conf works; if vhost is defined in admin console(native vhost), rules defined in admin console(requests filter) works.

check if php is running as same user under apache and litespeed

lsadm is used to access lsws admin console(:7080) by design, not intended for normal websites(port 80). if litespeed is running as nobody user, change the document owner to nobody. #chown -R nobody:nobody /home/websites/domain.com/public

maybe a false alarm ... if we can reproduce this issue in our lab, that'll help us to identify the cause of the issue. what package do you use to upload image? and using any upload progress bar script?

can you give a screenshot of: lsws admin console->Configuration->Server->Request Filter