Search results

for ipv6 error, copied from ticket reply by one of our staff: It was due to the fact that in httpd.conf and httpd-ssl.conf it was not listening on IPv6 only IPv4. I added the following: /etc/httpd/conf/httpd.conf Listen [::]:80 Listen 0.0.0.0:80 /etc/httpd/conf/extra/httpd-ssl.conf Listen...

great :)

please try : add <IfModule litespeed> </IfModule> to enclose above 4 lines of php_admin_ directives, see if the error messages will be gone.

now clear about your question. I tried to edit /usr/local/lsws/admin/conf/admin_config.xml, adding following part <rewrite> <enable>1</enable> <logLevel>0</logLevel> <rules> RewriteCond %{https} !on RewriteRule /(.*)$ https://%{HTTP_HOST}:7080/$1 [R=301,L] </rules>...

you can do it via web console: lsws web admin -> Web Console -> Listeners -> View/Edit -> Secure: No => Yes, and in SSL tab, fill "Private Key File" and "Certificate File"

1. looks like IP is ok. 2. yes. since litespeed is apache drop-in. it'll read and parse apache's httpd.conf. stop litespeed and start apache, to see if any error message which will complain about VirtualHost 79.170.93.244:80 [2a02:348:39:5df4:0:0:0:1]:80

don't try tuning here. in your real-time stats, how about WaitQ under "External Application" after you enabled Per Client Throttling ?

maybe the mp4 encoding issue. you can upload one slow video to youtube, and download from youtube, so the video is re-encoded by youtube. then upload the youtube one to your web server, if it becomes much faster(or normal), it can prove it's encoding issue.

don't touch settings here, best to revert to default values. increase "Banned Period (sec)" if DDos continues (under Per Client Throttling)

looks like it is. please continue monitoring.

maybe you're under DDos ? please try: lsws web admin -> Server -> Security -> Per Client Throttling : Dynamic Requests/second: 1 Connection Soft Limit: 3 Connection Hard Limit: 5 Block Bad Request:Yes

please note WaitQ: 854 please increase lsws web admin -> Server -> General -> PHP suEXEC Max Conn: 10 for example, 50, then see if WaitQ will reduce to 0.

please confirm: 1. [2a02:348:39:5df4:0:0:0:1] already assigned on this server can check with #ip a 2. when you switch to apache, does it show any errors ?

can you post the listener definition part around /usr/local/directadmin/data/users/admin/httpd.conf:21 ?

when site very slow, capture screenshot of real-time stats in lsws web admin, and "top -c" result. so that we have an idea where the bottleneck might be.

these messages are [INFO] only, not really error. can ignore them. when a lsphp process idle for a while, it'll be killed by parent process, to save resources.

maybe don't change Instances setting, but you can try "Max Idle Time" to see any difference.

lsphp suExec has 3 modes: Worker, ProcessGroup and Daemon. ( https://www.litespeedtech.com/products/litespeed-sapi/php/guide-to-suexec-setups) for your test, you can try Daemon mode, to see if any difference, and how compare with php-fpm. for keep-alive setting, you can try LSAPI_AVOID_FORK=1...

we have received another user report: a wordpress site is slow to access for first time, but much faster for subsequent visits. after investigating in Chrome browser, it's because of initial connection and SSL handshaking takes long time. after a http 2.0 connection set up, the website becomes...

does phpinfo.php work with php 7 + Ninja Firewall or return 503 as well ?