What 403 means
The server understood the request and refuses to carry it out. If you were logged in, you don’t have permission. Logging in again won’t help, because the server already knows who you are or doesn’t care.
When servers send it
For permission checks, blocked IP addresses or countries, web application firewalls, hot-link protection, and directories with listings turned off.
Common causes
- Your account’s role doesn’t allow this action.
- A file permission problem on the server (the web server user can’t read the file).
- No index file in a directory, with directory listing switched off.
- A firewall or bot protection rule blocking your IP, country or user agent.
- Cloud storage (such as an S3 bucket) that isn’t public, or a signed URL that has expired.
- A CSRF check failing in some frameworks.
How to fix it as a developer
- Check the user’s roles and the resource’s access rules.
- On the server, check file permissions: usually 644 for files and 755 for folders. The chmod calculator explains these.
- Check the firewall or CDN security logs for a blocked request.
- Some APIs return 404 instead of 403 to hide that a resource exists. That’s allowed by the spec.
How to fix it as a visitor
- Check you’re logged into the right account.
- Turn off a VPN, as some sites block VPN addresses.
- If you think you should have access, contact the site owner.
Related codes
- 401 Unauthorized: You need to log in, or the credentials you sent are missing, wrong or expired.
- 404 Not Found: There’s nothing at this URL, or the server won’t say whether there is.
- 451 Unavailable For Legal Reasons: The content is blocked for legal reasons, such as a court order or government censorship.
- 429 Too Many Requests: You’ve sent too many requests in a given time. Slow down and try again later.
Where it’s defined
403 Forbidden is defined in RFC 9110, section 15.5.4. It’s a 4xx code, the client error class: something is wrong with the request, so sending it again unchanged won’t help.
Other 4xx codes
400 Bad Request · 401 Unauthorized · 402 Payment Required · 404 Not Found · 405 Method Not Allowed · 406 Not Acceptable · 408 Request Timeout · 409 Conflict · 410 Gone · 413 Content Too Large · 414 URI Too Long · 415 Unsupported Media Type · 418 I’m a teapot · 422 Unprocessable Content · 429 Too Many Requests · 431 Request Header Fields Too Large · 451 Unavailable For Legal Reasons · 499 Client Closed Request
Or search them all in the HTTP status code list.