Search results

please refer https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:php:503-errors for complete instruction

either mode should be ok here. this selection is for php with apache Litespeed will build its own php -- lsphp based on the settings used in EasyApache, if suphp + apache is working well, and litespeed + lsphp has 503 error, we need more detailed info regarding it.

looks normal. what's lsws version ?

>Perms: 0666 I tried chmoding to 644 (InterWorx file manager: cannot_chmod) please check the parent directory's permission as well. assume lsphp5 running as user1, then ssh to the server as user1, it should be able to $cd /path/to/wp-content/uploads/2014/07 $ls -l egy....jpg >Force Strict...

please check 1)the permission of wp-content/uploads/2014/07/egy....jpg 2)is php suExec enabled or not ? lsws web admin-> Server -> General -> PHP suEXEC: Yes or No ? or lsphp running as nobody or each account's username ? 3) please check lsws web admin -> Server -> Security -> File Access

yes, that's it :)

@amirreza, I can login. has replied you there for 2 questions.

under lsws web admin -> Actions -> Real-Time Stats->External Application watch the "In Use", "Idle", "WaitQ" columns if WaitQ > 0 frequently, need increase the default "PHP suEXEC Max Conn" value which is 10.

may need add --with-jpeg-dir=/usr to rebuild lsphp please refer https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:php:lsapi-troubleshooting for more php build issues.

I think "--with-mysqli=/var" is invalid, so it's replaced by default --with-mysqli=mysqlnd for php 5.4.x. what "Client API version" shows in phpinfo under litespeed after you re-compile it with --with-mysql=/usr ? if it shows 5.5.38 which is same as apache, the issue should be gone

should only server (proxy IP on it) at DDoS provider can block the X-Real-IPs so the best WHM or litespeed can do is to provide the list of x-real-ip to proxy server(at DDos provider), then proxy server block these IPs. is the DDoS provider cloudflare ? I think apache don't support X-Real-IP...

much clear now ... another question: is the Proxy IP on your server or not ? if Proxy IP not on your server, how can you block those X-Real-IPs ?

by google the error message, it looks the problem is: "Your database server is set to use old passwords by default." "mysqlnd cannot use it to connect to the MySQL server." can you try --with-mysql=/usr --with-libdir=lib64 to recompile lsphp5. also check the mysql client version installed on...

for server level, can you give more details how to make use of such IPs? here is one example: with above rewrite rule, you can log the x-real-ip in access log with following parameter: %{X-REAL-IP}e related apache document: http://httpd.apache.org/docs/current/mod/mod_log_config.html

can you create a simple php page like http://www.php.net/manual/en/function.mysql-connect.php Example #1 to test if it's ok ?

I've read the phpinfo page, so it's php 5.4.30, and without "Configure Command"! how about to build lsphp with --with-mysql=mysqlnd ?

Hi, the X-Real-IP should be in X-Forwarded-For, or part of X-Forwarded-For to confirm this, you can create a phpinfo page and check _SERVER["HTTP_X_FORWARDED_FOR"] to let the value of X-Real-IP header seen by php script, you can add a rewrite rule in .htaccess RewriteCond %{HTTP:X-Real-IP}...

please show the "Configure Command" under apache's phpinfo.

SetEnv -- not yet but ExpiresByType already supported for long long time. anyway just now tested ExpiresByType text/css A2592000 in .htaccess, working as expected. apache document http://httpd.apache.org/docs/2.4/mod/mod_expires.html

can you test your site with http://ipv6-test.com/validate.php ?