newbie! 403 error forbidden

Installing, Configuring, Troubleshooting server daemons such as Web and Mail
Post Reply
rwd19
Posts: 1
Joined: 2011/08/11 09:10:03

newbie! 403 error forbidden

Post by rwd19 » 2011/08/11 09:21:58

The problem i am having is error '403; You don't have permission to access / on this server.'

Someone has been messing around with the httpd.conf file and permissions. To be more precise the 'chown' command. My knowledge is extremely limited on ssh so anyone with a little patience that could point me in the right direction would be greatly appreciated.

It is an unmanaged server obviously due to the costs, so the support team cannot help me in regards to this problem, the server has been working fine for a good few months up until the httpd.conf file was messed around with.

The list of affected domains are as follows;

http://trustednewsnetwork.com/
http://gmn-network.com/
http://gmn-network.org/
http://i-webcasting.com/
http://aryasamajonline.org/
http://aryasamajlondon.org/
http://aradhna.org/
http://omniexpress.org/
http://spoken-elt.com/
http://complaintsmedia.com/
http://vishwani.com/
http://manbhaavan.com/
http://news-x-change.com/
http://nripioblog.com/
http://gdn-network.org/
http://bbcblog.co.uk
http://tokillarat.com
http://alternativetohotel.com


Any help would be greatly appreciated as i said before!

Thanks in advance guys!

foxb
Posts: 1927
Joined: 2006/04/20 19:03:33
Location: Montreal/QC

newbie! 403 error forbidden

Post by foxb » 2011/08/11 13:17:05

You need to provide more information on the subject... for ex at least your httpd config/logs and maybe current ownership of the related folders.

Since you have limited knowledge on the subject you might consider hiring part time sysadmin to deal with issues like these...

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: newbie! 403 error forbidden

Post by TrevorH » 2011/08/11 13:30:45

If it's just the top level directory that's had its ownership changed then running

[code]
rpm --setperms httpd
[/code]

might fix it by resetting the permissions on the various files owned by the httpd package back to their default values.

Post Reply