Skip to the content

403 Forbidden

The server understood the request and refuses to carry it out. Logging in again makes no difference.

Class
4xx Client error. The request is the problem: a wrong address, missing credentials, data the server can't accept.
Defined in
RFC 9110

Share this tool:TwitterFacebookLinkedInWhatsAppEmail

What causes it

When the rules don't allow it: the account lacks the right, the IP address or the country is blocked, a firewall took the request for an attack, or the server won't list a directory that has no index page. Web servers also answer 403 when file permissions keep them from reading the file.

What to do about it

As a visitor, check that you are logged in with the right account. If you are, only the owner of the site can change it.

As the owner of a site that answers 403 for its own pages, look in the error log of the server. The usual causes are file permissions that the web server can't read (directories want 755 and files 644), a missing index file, and a rule in the firewall or in the .htaccess file.

Not to be confused with

401 UnauthorizedNo valid credentials: logging in can solve it.
404 Not FoundWhat some servers send instead, to hide that the page exists.
451 Unavailable For Legal ReasonsRefused for a legal reason.

How Google treats it

Google handles a 403 like a 404 and drops the page from its index. It says not to use the code to slow crawling down.

All codes are on the list of HTTP status codes, which can be searched by number and by word.

See all 12