mickalo

Well-Known Member
Apr 16, 2002
782
5
318
N.W. Iowa
Hello,

we have a domain on our server, www.decisionbar.com which all of sudden can be viewed, keep getting the error:
Code:
You don't have permission to access / on this server.
the site was working fine earlier this morning, everything else is working... FTP, shell access,..etc. DNS is ok. The /public_html folder is set correctly and hasn't been changed... this one has me stumped!

Any help would be greatly appreciated.

we found this in the apache error log:
Code:
Permission denied: /home/decision/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
what exactly does this mean... never seen this type of error before?

Mickalo
 
Last edited:

C4talyst

Well-Known Member
Jun 21, 2008
55
0
56
Sucks that no one answered you on this one. Same problem here. Error message is obviously self-explanatory, however chmod 777 doesn't do squat. I'm at a loss so far.
 

C4talyst

Well-Known Member
Jun 21, 2008
55
0
56
Looks like the public_html folder needed a chmod 755, fixed it. Strangely, I had already done this a few days ago, I wonder if some cpanel script autochanges permissions on these directories?
 

DaveUsedToWorkHere

Well-Known Member
Dec 28, 2001
686
1
318
Looks like the public_html folder needed a chmod 755, fixed it. Strangely, I had already done this a few days ago, I wonder if some cpanel script autochanges permissions on these directories?
They should be 755 by default from our side. If you see the directory changing frequently to different permissions, feel free to submit a support ticket and we'll take a look. It's possible that the customer is uploading the entire public_html directory or using a synchronize function in publishing software that is pulling in a public_html with different permissions.
 

greetingsc

Well-Known Member
May 18, 2004
45
0
156
Dave -

I just ran apache update and ran across this exact problem. I had no problems before the update and after had to chmod 755 each accounts public_html folder individually to get everything working again.

On my other server all public_html folders are currently 750. What is the correct permission for the folder, and is there something wrong in apache update that causes permisisons to be set incorrectly?

Thanks,
Mike
 

greetingsc

Well-Known Member
May 18, 2004
45
0
156
It seems the problem wasn't the folder permissions, but for some reason httpd.conf had 'Group daemon' instead of 'Group nobody'

Mike
 

DaveUsedToWorkHere

Well-Known Member
Dec 28, 2001
686
1
318
It seems the problem wasn't the folder permissions, but for some reason httpd.conf had 'Group daemon' instead of 'Group nobody'

Mike
Interesting. What happens if you run /scripts/rebuildhttpdconf? Does 'daemon' come back?

FYI: You can save manual httpd.conf edits using /usr/local/apache/bin/apache_conf_distiller --update
 

greetingsc

Well-Known Member
May 18, 2004
45
0
156
I ran /scripts/rebuildhttpdconf and 'Group daemon' came back. I had to manually change it back to 'Group nobody' and restart apache.

Thanks for the help,
Mike

P.S. I put in a ticket to make sure this gets fixed, support request id #305874.
 

Cristi4n

Well-Known Member
PartnerNOC
Jul 2, 2006
73
0
156
I just had the same problem.
Maby it will help you debug:
Centos 5.2 final x64.
I have upgraded to cPanel 11.24.4-C32443 and then I rebuilt Apache 2.2 with php 5.2.8. The daemon group came up.
I had a modified httpd.conf.
 

mitgib

Well-Known Member
Apr 9, 2006
59
0
156
I just had the same problem.
Maby it will help you debug:
Centos 5.2 final x64.
I have upgraded to cPanel 11.24.4-C32443 and then I rebuilt Apache 2.2 with php 5.2.8. The daemon group came up.
I had a modified httpd.conf.
I'd been seeing this problem as well, this thread helped me alot, but what nobody has mentioned, after changing httpd.conf run

Code:
/usr/local/cpanel/bin/apache_conf_distiller --update
So the changes stick