403 Forbidden
“403 Forbidden: You don’t have permission to access this resource” on a WordPress site: causes and what to check
# Common log entries
You don't have permission to access this resource.
The web server returns 403 Forbidden when it refuses to deliver a page or file. On a WordPress site, the usual reasons are file or folder permissions the server will not read, or a deny rule in .htaccess. Apache shows the line “You don’t have permission to access this resource.”
Which of these do you see?
The site’s root folder or index.php has permissions the server will not read, or .htaccess denies every request.
A security rule in .htaccess blocks the admin paths.
Folders under wp-content lost read permission, or a hotlink rule matches your own domain.
Common causes
References
- Changing File Permissions (Advanced Administration Handbook)
- Apache HTTPD / .htaccess (Advanced Administration Handbook)
Rather not fix it yourself? Let WP119 handle it automatically.
Wrong file permissions are handled automatically: the system resets them to safe, working values. A corrupted .htaccess is handled automatically: the system rebuilds the rewrite rules. Fixes are made on a copy of your site in the recovery station and written back only after re-verification passes. In your site’s database, the protected tables (members, comments, orders and form submissions) are copied as structure only. In SSH and FTP mode, the system creates a pre-recovery backup on your host before writing back and restores from it if verification after write-back fails. If the recovery cannot be completed, the recovery fee is refunded in full.
- Initial assessment: Site URL entry
- Copy to the recovery station: Work on a copy
- Diagnosis: Item-by-item checks
- Recovery and verification: Home and inner pages
- Write-back or delivery: Only after verification passes
Use WP119 when your own site returns 403 Forbidden because of file permissions or .htaccess rules.
Check my site →