How to Fix Chrome 403 Forbidden Error

A 403 Forbidden error comes from the website, not from Chrome. The site’s server received your request, understood it, and refused to give you the page. That is the definition in HTTP’s standard, RFC 9110: “the server understood the request but refuses to fulfill it.” Chrome shows its own version as “Access to site was denied” and “You don’t have authorization to view this page”, and many sites show their own 403 page instead.

Whose problem is it? The site decides who gets in, so most fixes are on the site’s side. The few things you can change are what you send to it: the address, your sign-in, your cookies, and the network address you come from.

Step 1: Check the address

Make sure the address is the page you meant. Try the site’s home page and navigate from there.

Step 2: Sign in

A 403 can mean the site wants you signed in, or that the account you are signed in with is not allowed to see the page. Google’s download errors help gives the same advice for a “Forbidden” download: go to the website, check whether you need to sign in or provide some other authentication, and if you cannot, contact the website or server owner. RFC 9110 adds that if you did send sign-in details, the server considers them insufficient.

Step 3: Delete that site’s cookies

If you are signed in and still blocked, delete the cookies for just that site and sign in again (Google’s steps):

  1. Select More (three dots) > Settings.
  2. Select Privacy and security > Third-party cookies > See all site data and permissions.
  3. Search for the site, select Delete next to it, and confirm.
  4. Reload the page and sign in again.

To test quickly without deleting anything, open the page in an Incognito window (Ctrl + Shift + N, or ⌘ + Shift + N on a Mac).

Step 4: Test without a proxy

RFC 9110 notes that a request can be forbidden for reasons unrelated to sign-in. One thing you can change is where your request comes from: with a proxy, Microsoft explains, your traffic goes through the proxy server instead of coming directly from your PC (Microsoft’s proxy help). If you use a proxy you do not need, turn it off (see our proxy guide) and reload.

Step 5: Turn off extensions

To rule out an extension, open chrome://extensions, turn them all off, reload, then turn them back on one at a time. This is the order Google’s connection and loading errors help recommends.

Step 6: Contact the site

If none of that works, the block is a decision on the site’s side. Chrome’s error page for 4xx errors says: “If the problem continues, contact the site owner.” RFC 9110 notes a server may explain why in the page it sends back, so read the 403 page itself for a reason or a contact link.

If it is your website

Your server, or a service in front of it, decided to refuse the request. Open DevTools (F12, or ⌘ + Option + I on a Mac), go to the Network panel, reload, and find the request with status 403. Check its response, then the logs of your server and of anything in front of it.

Frequently asked questions

Is a 403 error a Chrome problem?

No. 403 is a status code the website’s server sends. Other browsers get the same answer from the same site unless something you send is different, such as cookies or your network address.

What is the difference between 403 and 404?

RFC 9110 defines 404 as the server not finding the page, and 403 as the server understanding the request and refusing it.

Why do I get 403 on a download?

Chrome shows “Failed – Forbidden” on the Downloads page. See our guide to Chrome download error messages.