WebsiteTrouble Blog · Website Errors
403 Forbidden: What It Means and How It Gets Fixed
Your own website says you do not have permission. What a 403 Forbidden error really points at, from file permissions to jumpy security rules.
Few error messages feel as personal as this one. You try to open your own website and it tells you, in so many words, that you do not have permission. Forbidden. Owners read that and think they have been hacked or locked out of their own property. Sometimes it is serious. More often it is a permission setting that drifted, a security rule doing its job too hard, or a file that landed in the wrong place.
A 403 is your server answering the door and refusing to open it. Here is what it is usually refusing, and why.
What a 403 actually means
The server found the page. That separates a 403 from a 404, where the page is simply not there. With a 403, the page exists and the server has decided the visitor may not see it. That decision comes from rules, and rules can be wrong. I place the 403 in the full family of errors in my plain-English guide to website error messages, and it is one of the more fixable ones once you know which rule fired.
Cause one: file permissions
Every folder and file on your site carries permissions that control who can read it. When a site gets migrated, restored from a backup, or worked on by hand, those permissions can come back wrong. A folder set too strict will 403 everything inside it, which is why a permissions problem often takes down whole sections of a site at once instead of one page.
Cause two: the security guard got jumpy
Security plugins and server firewalls watch for suspicious behavior, and normal life can look suspicious. Logging in from a new city, failing your password a few times, editing a file with words the firewall dislikes, any of these can get your own IP address blocked. If your site works fine for everyone except you, this is your prime suspect. It is a close cousin of being locked out of WordPress, and the way back in is similar: prove it is you, then fix the rule, not just the block.
Cause three: a missing front door
If a folder has no index page and the server is set not to list its contents, visitors get a 403 instead of a page. This shows up after redesigns and migrations, when a section's main page did not make the trip. The folder is full, the site looks complete from the inside, and the public gets refused at that one address.
- 403 on the whole site points at permissions, a firewall rule, or a server-level setting.
- 403 on one section points at that folder's permissions or a missing index page.
- 403 only for you points at your IP address being blocked.
- 403 right after a migration points at the move, almost every time.
What not to do
Do not start loosening permissions across the whole site until pages load. Setting everything wide open will clear the error and hand the keys to anyone who comes looking, and lax permissions are one of the doors real hacks walk through. The fix is the correct permission on the right folder, not no permissions anywhere.
How I fix it
On a screen share we start with where the 403 appears and for whom, because that pattern narrows the cause fast. Then we check the server's error log, which usually names the rule or the folder outright. Fix that, reload, and confirm the page loads for a logged-out visitor, not just for you. If a firewall rule caused it, we adjust the rule so your next trip or typo does not lock you out again.
A 403 standing between your customers and your site is lost business by the hour, and it is squarely website error help territory. Bring the exact address where it happens and we will trace the rule that fired, live.
Rather have it fixed today?
This is the kind of problem I fix live on a screen share, while you watch. A standard fix is $99 for the first hour, same-day emergency help is $299 for the first hour, and every fix carries a 30-day warranty.