A 403 error means the server understands the request but is refusing access. The most common causes are incorrect file permissions, missing index files, restrictive .htaccess rules, or blocked IP access.
Common symptoms
- Only one directory returns 403
- The site worked before a file upload or restore
- Admin paths fail while the homepage works
Troubleshooting steps
- Ensure folders are generally set to
755and files to644unless your application documents a different requirement. - Confirm the target directory contains an
index.phporindex.htmlfile if directory listing is disabled. - Review
.htaccessfor deny rules, IP restrictions, or malformed directives. - If a security plugin or WAF was recently enabled, disable it temporarily to isolate the issue.
- Check whether the affected path is protected by password directories or hotlink controls.
Additional notes
- Permissions that are too open can also trigger server protections in some environments.
- A 403 on uploads or admin paths often indicates an application-level rule rather than account suspension.
When to contact support
Contact support if the site permissions and index files are correct but the server still returns 403.