403 Forbidden Errors Suddenly Appear!

HostHK

Verified User
Joined
Jan 1, 2010
Messages
13
Hello all!

One of my users has suddenly started experiencing 403 Forbidden errors. It seems strange as this has never been an issue and has been brought about after the user deleted all files and reuploaded.

The 403 error appears when attempting to access any file within his account. Even plain blank file with a .html extension. Nothing appears to work.

I have removed their .htaccess file and there are no custom mods to the httpd conf.

The problem exists also with the HTTPS, depsite the fact the private_html folder is completely empty.

I have also ensured that the public_html dir is chmod to 755 as well as the test files being set to 644 or 755.

Finally, a restart of apache seems not do anything either.

Any ideas anyone?
 
Check the owner of the public_html and of those files, cause is not related to permission but probably is related on owner.

Regards
 
The 403 error appears when attempting to access any file within his account. Even plain blank file with a .html extension. Nothing appears to work.

What do apache logs say there? Do you have any extra limiting mods for Apache? And frontend+backend realization?
 
Hi all,

Scripts are running as Apache.

I see nothing in th error or access logs relating to the user's account.

No custom modules installed and I'm still very much stuck... :(
 
Last edited:
So you might want to hire somebody then. Because without either logs or access to your box, there is nothing we can do you for you.
 
Hi everyone,

I appreciate the response, and should I continue to struggle with this issue much longer, I may have to find some real help.

SeLLeRoNe, do you have skype or a preferred contact E-Mail. If you prefer not to disclose such info via the forums, I'de be happy to receive your PM.
 
It seems strange as this has never been an issue and has been brought about after the user deleted all files and reuploaded.

There is always the first time. The question is how long your user will wait for a solution.
 
There is always the first time. The question is how long your user will wait for a solution.

To be honest, its not a big deal. The customer has purchased from us a VPS server with DirectAdmin, which is running smoothly. We offer a backup solution on a shared hosting server offering some form of fail over...

Therefore, not exactly urgent, but important none the less..

Has no one ever seen this problem before?
 
A 403 can be a number of things:
#1 - permissions.
Does the mentioned individual have specific permissions to view that directory and page?

#2 - no index
I've seen this a few times where autoindex is turned off. This should result in a 403

#3 - mod_security rules
In this case, something will show up in the actual server error logs usually (not site logs).
 
Back
Top