Search results

no need. any license change, at command line, you just need run /usr/local/lsws/bin/lshttpd -r in cPanel app change the license should work too --- follow by a lsws restart.

please refer http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:license:command_reference check the license on command line /usr/local/lsws/bin/lshttpd -V

main config file is /usr/local/lsws/conf/httpd_config.xml if you have defined some lsws native virtual hosts, then need backup these .xml files as well. if lsws read apache's config files, then backup those files just like backing up apache.

can you provide more information ? are you under attack ? is it working under apache ? have you installed WHM(cPanel) ? if you are under attack, please try our anti-ddos service, now it's free...

I'd recommend to use latest rulesets. mod_security is our upstream and keeps updating frequently. so we're lag with them almost all the time. But 1st, I don't think mod_security is all of security; 2nd, one fact I know of, when I log in our customers' server, I see quite a lot of them...

official document about pmFromFile: https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual#wiki-pmFromFile this directive only support in apache's httpd.conf, not inside Litespeed config. litespeed native config compatible up to mod_security 1.9.x. pmFromFile directive is...

please try. currently our lab's cPanel server not available. so I can't test it now. for reference: http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:reverse_proxy_cache 1. Create Web Server External App Name:127.0.0.1 Address:127.0.0.1:80

most web servers include litespeed, is working in this way. the cookies are in request header, but not in response header. Correct me if wrong. base on above reason, still need separate domain to eliminate cookies, no cookie s transfer between client and server.

looks DNS issue on the server: run #host www.litespeedtech.com to verify it.

how about increase more, say 1G

Sorry, the issue resolved or not? have you tried the way in the wiki page:

please refer http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:apache:ezcpanel Step 3: Build matching PHP binary see if it resolves this issue.

if you actually don't need timezonedb.so eaccelerator.so then that's just the fix. if you need them, you have to build timezonedb.so or eaccelerator.so from source code. the build procedure, please refer...

just now reproduced the issue. on a x86_64 linux box, when set to 5000M, upload a 1.4G file failed; when set to 2000M, upload 1.4G succeeded. Has reported to development. Thanks!

Sorry, typo corrected: # /usr/local/lsws/bin/lshttpd -V # /usr/local/lsws/bin/lshttpd -r # /usr/local/lsws/bin/lshttpd -V

for a quick possible solution, please try: comment out ;extension=timezonedb.so ;extension=eaccelerator.so in php.ini see if the errors disappear.

how about run: # /usr/local/lsws/bin/lsttpd -V # /usr/local/lsws/bin/lsttpd -r # /usr/local/lsws/bin/lsttpd -V

I did tests on a local 32-bit x86 linux box, uploaded 1.2G file with succeed. if you're using php to handle the uploaded file, please check upload_max_filesize and post_max_size limit set in php.ini(you can refer...

please enable debug log(lsws admin console->Actions->Toggle Debug Logging) during upload, see if can capture useful info/error message

please force re-install 4.2.2, I tested the latest build(about 1 hour ago), the warning has gone.