upcp is changing httpd.conf to 600 this break many fantastico installation

[internetfab]

lol and Im on stable and have got the same issue...

 

[chirpy]

Did you upgrade to EDGE 10.4.* at any stage? If you did, then you will have this problem because downgrading back to STABLE does not undo the new security changes.

 

[internetfab]

Yes that's what I feared would be the problem..
Does EDGE solve the httpd.conf cannot be read in users cpanel? Thinking about taking it back to EDGE since stable doesnt erase the changes from edge install.

Had upgraded it to EDGE to see if it would solve my problems with SSHD failing (centos 3.5) and hanging after asking for password. It did not, so I downgraded to stable.

 

[chirpy]

The recommendation is to simply chmod 644 httpd.conf until the issues are worked out I believe if you've done that.

 

[techark]

You have made a decision to use the Edge release, thus you have taken the choice to use a NON STABLE TESTING RELEASE! You report bugs, cPanel fixes them and eventually releases a Current > Release then Stable build. You need to expect that such issues will arise when you make a decision to use Edge on production systems.

You can not fault cPanel for your own ignorance, and you can not fault them for improving security. They have workarounds, and they have a proper means of reporting such issues ( bugzilla.cpanel.net ). Also, contact the vendor of any 3rd party software that doesn't work as that is far from cPanels responsibility.

I am on stable so get your facts straight before shooting from the hip and calling some one ignorant.
Did you even read my post before you decided to jump in?

I do not call Cpanel addon domain support 3rd party software do you? I do not care about fantastico issues I care that my clients cannot control their addons and parked domains nor sub domains from cpanel any longer.

 

[chirpy]

If you are on STABLE and have never gone to EDGE v10.4 then you should not be suffering the httpd.conf problem, which is what this thread is about. Fantastico is a 3rd party product and as much as people do indeed like it, it is none of cPanel's concern. That falls on Kosmo's head over at http://www.netenberg.com

If you are suffering from a problem with httpd.conf being chmod 600, then a temporary solution has been provided to you.

 

[haze]

I am on stable so get your facts straight before shooting from the hip and calling some one ignorant.
Did you even read my post before you decided to jump in?

I do not call Cpanel addon domain support 3rd party software do you? I do not care about fantastico issues I care that my clients cannot control their addons and parked domains nor sub domains from cpanel any longer.

Then you have problems far beyond that of this thread. Contact your vendors support department as this is probably totally unrelated to the the issues discussed in this thread.

 

[lloyd_tennison]

Fantastico was fixed DAYS ago, so quit talking about them. The cron solves the addon and subdomain feature for now.

So this is a non-issue at the moment, hopefully that will be fixed with that soon promised release build.

 

[kris1351]

Actually going to the new current breaks the fantastico link

 

[kris1351]

mv /usr/local/cpanel/3rdparty/fantastico/xskin.html /usr/local/cpanel/base/frontend/x/cells/fantastico.html

http://www.netenberg.com/forum/viewtopic.php?t=2931

Seems to be related to only certain installs of Fantastico. Still have two servers this didnt work for.

 

[tjb]

cron job to fix this

Hello all, I am very new to apache and cpanel. Could someone tell me the cron command to Add a cron to chmod httpd.conf 644 after every upcp

and can i add this to my account in cpanel or where to i install the cron job

thank you for any help.

 

[Andrew87]

Adding a domain through WHM or a parked domain through cPanel causes httpd.conf to change to 600 and then cPanel reports errors if you downgrade to stable or release. Even with Current or Edge, parked domains do not work properly.

 

[henker]

Does more than breaks Fantastico it also means users cannot manage addon or parked domains from cpanel any longer. They just get the cannot read httpd.conf premission errors when they try.
This is silly.

In addition, it looks like neither /scripts/postupcp nor /scripts/postwwwacct is executed after creation of an account, so there's no way to chmod httpd.conf to 664.
A cron running every minute chowning httpd.conf to 664 is going to be trouble...
I admit we had one server upgraded from stable->edge to resolve the boxtrapper issues and went back to stable. Decided to remove cpanelpro. Boxtrapper has been a pita since day 0.
And yes, Fantastico still borks if httpd.conf has 600.

 

[easyhoster1]

And now front page user cant upload, as it needs to read httpd....we will just need to play with chmod for now..