PHP not working only in one account
I have a WHM 11.40.1 (build 11) controlled Centos 6.5 Server in which every account is working normally except for one - where any php file is not parsed no matter what directive I use in the .htaccess file
I have tried all the following individually:
Still it refuses to parse resulting in the browser trying to download the file/ displaying the php code or if I use the php5 mode, it results in internal server error. I have checked the account's root and found nothing abnormal - no extra php.ini. I would be grateful for any solution to this problem.
Addhandler application/x-httpd-php .php .html
Addhandler application/x-httpd-php5 .php .html
SetHandler application/x-httpd-php
Still it refuses to parse resulting in the browser trying to download the file/ displaying the php code or if I use the php5 mode, it results in internal server error. I have checked the account's root and found nothing abnormal - no extra php.ini. I would be grateful for any solution to this problem.
-
Hello, Your access level is listed as Website Owner, have you spoken to your host about this yet? 0 -
I own the dedicated server in which we host multiple sites of our own. I am sorry if I chose the wrong id inadvertently. To continue with the issue - it shows no errors in the log. The server runs SuPHP and there is no issue reported in the suphp_log either. I copied the entire directory of the site to a local Centos server and everything works normally. So it has to be a cPanel issue. 0 -
I solved the issue finally. The old .htaccess file in the root of the problematic account contained lots of directives. I started with a clean slate and added only what was immediately necessary. That resulted in this error: SoftException in Application.cpp:363: GID of script "/home/useraccount1/public_html/some.php ttt.php" is smaller than min_gidAnd I changed the group id to that of the useraccount1 and PHP started working. I still don't know why the earlier .htaccess didn't show any errors.0 -
Hello :) I am happy to see you were able to resolve the issue. Thank you for updating us with the outcome. 0
Please sign in to leave a comment.
Comments
4 comments