Does this kind of error message send shock waves down your spine? A client of mind went into a frenzy when she saw this message on her site. She panicked and shot me an e-mail asking for help.
It was the first time that I am dealing with such an error and it took me quite awhile to get the problem fixed. Being of a non-technical background I had to google around for relevant details then attempt a trial and error fix it on the site.
I tried everything from removing all the files to reinstalling a new blog on the site. It still didn’t work till I checked out all the permission files . I realised that her public_html file permission was wrongly set to 705 instead of 755. Just by changing the numbers on that permission file removed the 403 error.
It was really a relieve for me when I finally solved that complex puzzle. It show with a little determination and self-learning one can achieve what you may assume impossible to do.
What I learned from this project?
- Make sure that your files are frequently backed up on server or your local hard disk.
- Do not try to alter codes or files on your server if you are not fluent with the programming knowledge as a single chance of a code may cripple your site.
- List down what changes you have implemented on your site so that it is easier for you to refer when you want to know what changes you have done which may have improved or hampered the productivity of your site.


![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=0f9d62c8-3cf0-45a8-9087-c48f69d75090)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=ea11daf3-5cec-4c21-943c-e99aed8e7044)


![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=ca801455-ce01-4e4d-823e-79e24602ec0e)

![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=3c5ea35f-0d02-4802-bf10-d9465205cd21)



