---
title: "HTTP 403 Forbidden — What It Means & How to Fix It"
description: "HTTP 403 Forbidden: The server understood the request but refuses to authorize it. Common causes, fixes and how to monitor it."
url: https://uptrack.app/http/403
---

# HTTP 403 Forbidden

The server understood the request but refuses to authorize it. Unlike 401, the client's identity is known — they simply do not have permission to access this resource.

## What does HTTP 403 mean?

The server understood the request but refuses to authorize it. Unlike 401, the client's identity is known — they simply do not have permission to access this resource.

## Common causes

1. 1  
The authenticated user does not have the required role or permission to access the resource.
2. 2  
IP-based access control or a Web Application Firewall (WAF) is blocking the request based on the client's IP address or geographic location.
3. 3  
File system permissions on the server prevent the web server process from reading the requested file or directory.

## How to fix it

1. 1  
Check the user's roles and permissions. Ensure the account has the required access level for the resource.
2. 2  
If blocked by a WAF or IP whitelist, add the client's IP address to the allow list or adjust firewall rules.
3. 3  
On the server, verify file permissions (e.g., chmod 644 for files, 755 for directories) and ensure the web server user owns or can read the files.

## Monitor for HTTP 403 errors

If a public page suddenly returns 403, it usually means a misconfigured firewall rule or permissions change. Uptrack detects this within 30 seconds and alerts you once several locations confirm it, so you can revert before users are locked out.

## Catch HTTP errors before your users do

Start free, or choose a plan, for 30-second monitoring and alert confirmation.

[See plans](https://uptrack.app/pricing)

from $3/mo · 30-day money-back guarantee

## Other HTTP status codes

- [HTTP 404 Not Found](https://uptrack.app/http/404)
- [HTTP 401 Unauthorized](https://uptrack.app/http/401)
- [HTTP 405 Method Not Allowed](https://uptrack.app/http/405)
- [HTTP 400 Bad Request](https://uptrack.app/http/400)
- [HTTP 408 Request Timeout](https://uptrack.app/http/408)
- [HTTP 409 Conflict](https://uptrack.app/http/409)
- [HTTP 410 Gone](https://uptrack.app/http/410)
- [HTTP 413 Payload Too Large](https://uptrack.app/http/413)
- [HTTP 415 Unsupported Media Type](https://uptrack.app/http/415)
- [HTTP 422 Unprocessable Entity](https://uptrack.app/http/422)
- [HTTP 429 Too Many Requests](https://uptrack.app/http/429)
- [HTTP 451 Unavailable For Legal Reasons](https://uptrack.app/http/451)
- [HTTP 500 Internal Server Error](https://uptrack.app/http/500)
- [HTTP 304 Not Modified](https://uptrack.app/http/304)
- [HTTP 502 Bad Gateway](https://uptrack.app/http/502)
- [HTTP 503 Service Unavailable](https://uptrack.app/http/503)
- [HTTP 302 Found](https://uptrack.app/http/302)
- [HTTP 504 Gateway Timeout](https://uptrack.app/http/504)
- [HTTP 301 Moved Permanently](https://uptrack.app/http/301)
- [HTTP 520 Web Server Returns Unknown Error](https://uptrack.app/http/520)
- [HTTP 522 Connection Timed Out](https://uptrack.app/http/522)
- [HTTP 204 No Content](https://uptrack.app/http/204)
- [HTTP 201 Created](https://uptrack.app/http/201)
- [HTTP 200 OK](https://uptrack.app/http/200)

## Keep reading

- [HTTP 451 Unavailable For Legal Reasons](https://uptrack.app/blog/http-451-unavailable-for-legal-reasons)
