Fix "Access Denied" and "You need permission"

Why a site says Access Denied or that you need permission, from a firewall reference number to a parental-control or work device block, and how to fix each one as a visitor or site owner.

· 6 min read · By the Spot Downtime team

“Access Denied”, “You don't have permission to access this resource” and “You need permission to access this site” all mean something decided you shouldn't see the page. The fix depends on what decided that, and the wording of the message usually tells you.

Which block is it?

What you seeWho blocked youJump to
“Access Denied. You don't have permission to access … on this server.” and a Reference #18.…The site's CDN firewall (Akamai)Firewall blocks
“Error 1020: Access denied” or “Sorry, you have been blocked” with a Ray IDThe site's Cloudflare firewall rulesFirewall blocks
“Forbidden. You don't have permission to access this resource.”The web server itself (Apache, nginx)Server configuration
A shared document or SharePoint site with a Request access buttonThe owner hasn't shared it with your accountShared files and sites
A block page with a button to ask a parent, or ERR_BLOCKED_BY_ADMINISTRATORParental controls or your work or school deviceBlocked on your side

Firewall blocks: a reference number or Ray ID

Big sites sit behind a CDN that screens every visit for bots and attacks. When it doesn't like a request, it answers with its own page before the site ever sees you. The site is up; your visit was scored as risky. Common reasons:

  • A VPN, proxy or Tor exit whose IP address other people have abused.
  • Browser extensions that change headers, block scripts or spoof your user agent.
  • Stale or corrupted cookies for the site, often after a password change or a long-open tab.
  • Visiting from a country the site has chosen to block.
  • Too many requests in a short time, like refreshing a ticket page over and over.

How to fix it

  1. Turn off your VPN or proxy and reload.
  2. Clear cookies for just that site, or try a private window.
  3. Disable extensions, or try another browser.
  4. Switch networks: mobile data instead of Wi-Fi gives you a different IP address.
  5. Wait 10 to 30 minutes if you were refreshing a lot. Rate limits expire.
  6. Still blocked? Send the site the reference number or Ray ID. It lets their team find the exact rule that blocked you.

Server configuration: “Forbidden”

A plain “Forbidden” page with the server's name at the bottom is an HTTP 403 from the web server. As a visitor there is nothing to fix; the owner has to. If it's your site, these are the usual causes:

  • File permissions. The web server user can't read the files. Directories usually need 755 and files 644.
  • No index file. nginx logs directory index of "/var/www/html/" is forbidden when a folder has no index.html or index.php and directory listing is off.
  • A deny rule. Require all denied in Apache, a leftover Deny from all in .htaccess, or deny all; in an nginx location.
  • Your own firewall. A security plugin, WAF or geo-block that started catching real visitors.

The error log says which one it is:

# Apache
sudo tail -n 50 /var/log/apache2/error.log
# nginx
sudo tail -n 50 /var/log/nginx/error.log

Every cause in more depth: 403 Forbidden. Not sure whether it's a permission or a login problem? 401 vs 403 covers the difference.

Shared files and sites

Google Docs, Google Drive, SharePoint and OneDrive show a permission page when a link hasn't been shared with the account you're signed in to. Check you're on the right account (work vs personal is the usual mix-up), then use Request access so the owner gets an email. If the owner set the link to “only people in this organisation”, only they can open it up.

Blocked on your side

Sometimes the block comes from your own device or network, not the site:

  • Parental controls. A child account managed with Google Family Link or similar shows a block page with a button to ask a parent. The parent approves the site from their own device.
  • Work or school devices. Chrome shows ERR_BLOCKED_BY_ADMINISTRATOR when an admin policy blocks the site. Open chrome://policy to see the policies in force, and ask IT to allow it.
  • Network filters. Office, school and public Wi-Fi often filter whole categories of sites. Mobile data gets around it; a different network is the test.

Is it blocked for you, or for everyone?

If you run the site, a block that only hits some visitors is easy to miss: it works from your office and fails for customers on another continent. Check it from several countries at once:

Check a website from multiple locationsSee the status code your site returns from servers around the world, in one go.

For a site you don't run, Is it down? checks whether it answers at all, and shows what other people are reporting.

Catch a 403 before your customers do

A deploy that breaks permissions or a WAF rule that misfires turns your home page into “Forbidden” while the server looks healthy. Website monitoring treats a 403 as down, confirms it from 3 regions and alerts you, and a keyword check catches a block page served with a 200.

Get new guides by email

Practical posts on monitoring, outages, error fixes and on-call, when they're published. No spam.

Unsubscribe from any email with one click. See our privacy policy.

Keep reading