chmod 777

[HH-Steven]

Ok, didnt know where to put this, so i suppose general will do.

Whenever i update cpanel, rebuild apache or anything else like that all my accounts get chmodded to 644 which results in a 403 forbidden error message upon viewing the accounts.

Simple solution yes - chmod 755 /home/*/public_html

But it still doesnt stop these errors showing up in the first place, how do i go about that?

Ive tried /scripts/enablefileprotect but it doesnt make a difference.

Any help is greatly appreciated, thanks

[haze]

You have to be kidding me, 777 ? Check your error logs.. for the love of god! Your approach is like taking a baseball bat to a computer because your can't open the cd-drawer.

[dgbaker]

777 is a hackers dream come true. You effectively allow any user anywhere to modify any file without challenge.

I would recommend hiring a sysadmin to fix the true reason behind the 403 instead of opening your server to attachs and hacks.

[HH-Steven]

Yeah, sorry about that, i meant 755, thats what you get for posting in a rush.

Was merely using 777 as an example of what i had to do.

Anyway, is there any solution to this?

[Etheral]

do you get any errors in apache logs after a build?

[HH-Steven]

Yes, only the one, but its repeated over and over :

[13-Jan-2005 14:12:03] PHP Warning:  Unknown(): Unable to load dynamic library './ixed.lin.4.3.8$ cannot open shared object file: No such file or directory in Unknown on line 0

[Donna]

two things...

#1 run
/scripts/fixeverything

#2
Make sure under WHM's tweak settings that you have it set to use sourceguardian as the main php decoder

[HH-Steven]

OK, well /scripts/fixeverything didnt help and i see no option for sourceguardian in whm - tweaksettings

[HH-Steven]

Ok, just checked my logwatch email on the off chance it might list something and i noticed the following :

WARNING: Kernel Errors Present
hda: drive_cmd: error=0x04 { DriveStat...: 1Time(s)
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }...: 1Time(s)

hdb: drive_cmd: error=0x04 { DriveStat...: 1Time(s)
hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }...: 1Time(s)

Ive got a feeling thats whats causing it, how can i fix that? or would it be a DC issue?

[dezignguy]

I'm fairly sure that's just a S.M.A.R.T. error... and isn't anything to worry about.

However, it's suggested that you google it (google.com) and read up on it.

[chirpy]

If you only get those errors on boot and only once, then they're probably nothing to worry about as dezignguy says. If you get reams of them regularly, then your disk is probably on its last legs.