What is 403 error “Forbidden”
Have you just come across a page announcing the message “403 Forbidden” or “403: Access denied” or “403 Forbidden – NGINX”? Let’s explain it all.
What does a 403 error mean?
The HTTP 403 error code is a code returned by the server to the client (your browser) when the client requests a page, a resource, … When all goes well, the server returns code 200.
When the requested page displays the message “Error 403 Forbidden” or one of its variants, the server signals that it has understood the request but does not wish to respond. That is, it will not return the requested web page, file or resource.
In contrast to the 404 error and or the 410 error which correspond to a problem on the server, the 403 error is not really an error but information: content to such and such a page or resource is denied.
Why is access to content denied?
A 403 error can be quite legitimate, for example if I am trying to access a directory containing sensitive files that are blocked from access on the server. This is what happens if you are looking to access the /wp-includes directory on a WordPress site.
In this case, nothing to do. It is normal that this content is not directly accessible on the Internet.
Inappropriate browser configuration
You may have a problem on the client side, that is, on your web browser. Here are some things to look at:
- check your web browser’s cache
- pause your adblocker or allow the requested site on that tool
- pause your antivirus: if the site is blacklisted in the antivirus, it will be blocked and you may get a 403 error when visiting it
Mis-settings on the server
The 403 error corresponds to an access rights issue, which may or may not be legitimate.
In the case where the requested resource should not be blocked, we need to go and modify the access rights on the server:
- the read/write/modify right, which corresponds to 3 digits, each digit corresponding to a set of rights for a set of users.
For example, WordPress, the most used CMS in the world, and therefore the one that suffers the most malicious attacks, says that the access rights to be set are 644 for files and 755 for directories.
- the setting of the .htaccess file if you’re on an Apache server (NGINX servers don’t have an .htaccess file). You need to have rights at level 755 on this file to avoid errors.
- If you are on WordPress, it may be from one of the many plugins you use. If the error persists after all previous fixes, try disabling your plugins.
Requirement to be logged in to access content
In this case, the server does not return a 403 error but a 401 error. It knows that it is possible to access the requested resource, but you have to be authenticated to the site to do so.
Netflix nsez 403
If you stumble upon a message on Netflix with the “Error NSEZ-403 Something went wrong. Sorry, we’re having trouble with your request. You will find lots to explore on the home page.” message, it generally means you could have a connectivity problem. You can try the following solutions.
For Mac or windows computer
Try to sign in your Netflix account on a different device (your smartphone for example) but using the same network as your computer. For example, if you use the wifi from your home with your computer, use the same wifi to connect with your smartphone.
- If you don’t success to sign into your Netflix account and you see an error message, try again later.
- If you don’t see any error message when sign in, you have to contact the Netflix support as there is a problem somewhere.
Other devices (smartphone, tablets, …)
Go to the Netflix website with a computer.
- Visit the url http://www.netflix.com/clearcookies using the same network as the one used with your first devices.
- Try to sign in on the computer
- You see the NSEZ-403 error. You can’t connect into our account. You can try again later.
- You don’t see the error, contact the support.