The request was a legal request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference. This is usually due to a scripting or file permissions issue.
403 Forbidden or No Permission to Access
A 403 Forbidden error means that you do not have permission to view the requested file or resource. While sometimes this is intentional, other times it is due to misconfigured permissions.
The top reasons for this error are permissions or .htaccess error.
The 403 Forbidden error means that your file has bad permissions. Directories and folders must be 755. Executable scripts within the cgi-bin folder must be 755. Images, media, and text files like HTML should be 755 or 644.
See our article on How to change permissions (chmod) of a file for information on how to change file permissions.
Hidden Files (Dot Files)
If you see “client denied by server configuration” in your Error Logs, then this usually means bad file permissions, but could also mean that the visitor is trying to look at a hidden file, like the .htaccess file. You cannot look at that file in your browser, or any file name that starts with a dot.
e.g. http://domain.com/.htaccess will always result in a 403 error.
The account may have IP Deny rules. Check in cPanel and make sure you are not blocking your own connecting IP.
You may have changed the Index Manager to No Indexing. This will cause a 403 error if their is no correct index page to load.
The error could be caused by our mod_security rules. Please contact ZabwinoHosting for further help.