A 403 Forbidden Error occurs when a web server forbids you from accessing the page you’re trying to open in your browser. Most of the time, there’s not much you can do. But sometimes, the problem might be on your end. Here are some things you can try.
The 403 Forbidden Error happens when the web page (or another resource) that you’re trying to open in your web browser is a resource that you’re not allowed to access. It’s called a 403 error because that’s the HTTP status code that the webserver uses to describe that kind of error.
You usually get this error for one of two reasons. The first is that the owners of the webserver have properly set up access permissions and that you’re really not allowed access to the resource. The second reason is that the owners of the webserver have improperly set up permissions and you’re getting denied access when you really shouldn’t be.
Just like with 404 errors and 502 errors, website designers can customize how a 403 error looks. So, you might see different-looking 403 pages on different websites. Websites might also use slightly different names for this error. For example, you might see things like:
- 403 Forbidden
- HTTP 403
- HTTP Error 403 – Forbidden
- HTTP Error 403.14 – Forbidden
- Error 403
- Forbidden: You don’t have permission to access [directory] on this server
- Error 403 – Forbidden
The vast majority of the time, there’s not much you can do to fix things on your end. Either you’re really not allowed to access the resource, or there’s an error on the server-side of things. Sometimes, it’s a temporary error; sometimes it isn’t. Still, there are some things you can try.
Refreshing the page is always worth a shot. Many times the 403 error is temporary, and a simple refresh might do the trick. Most browsers use Ctrl+R on Windows or Cmd+R on Mac to refresh, and also provide a Refresh button somewhere on the address bar.
It doesn’t fix the problem very often, but it takes just a second to try.
The most common reason for a 403 error is a mistyped URL. Make sure that the address you are trying to access is for a web page or file, not a directory. A regular URL would end in .com, .php, .org, .html, or just have an extension, while a directory URL would usually end with a “/”.
Most servers are configured to disallow directory browsing for security reasons. When they’re properly configured, you’re redirected to another page. When they’re not, you might see a 403 error.
It’s also possible the page with the error has been cached in your browser, but the actual link was changed on the website. To test out this possibility, you’ll have to clear your browser cache and cookies.
Clearing the cache won’t affect your browsing experience much, but some websites may take a couple of extra seconds to load as they re-download all the previously cached data. Clearing cookies means you’ll have to sign in again to most websites.
To clear the cache in your browser, you can follow this extensive guide which will teach you how to clear your cache in all the popular desktop and mobile browsers including Google Chrome, Firefox, Microsoft Edge, and Safari.
If you’re trying to access a website that requires you to log in before you can see the content, then that might be causing the issue. Typically, servers are configured to show you an error letting you know you must be logged in to access the content.
But some improperly configured servers might throw a 403 error instead. Try to log into the website (if possible) and see if the error goes away.
If none of the simple solutions we’ve talked about so far work, you can always wait a while and come back later. Since most of the time, 403 Errors are caused by issues with the website in question, it’s likely someone is already working on the problem.
Another option is to contact the website owner directly. Look up their contact information on the website and contact them about the page in question. If there is no contact form, you can try and reach the website on their social media.
If you can confirm that the website in question is working for others but not for you, then it’s possible that the public IP address your ISP provided you (or your whole ISP) has been blocked for some reason. You can try contacting them and letting them know about the problem. It’s not a very likely solution, but they might be able to help.
Some websites block VPN users and will show a 403 Forbidden message if you try connecting to them through a VPN. If you suspect this is the problem, you can disconnect from your VPN and then try connecting to the website. (If you’re not familiar with VPNs, you probably aren’t using one at the moment.)
Individual websites may not ban every VPN server out there, so you might want to try switching to a different server provided by your VPN service of choice—or switching to another VPN service entirely.