Skip to content
OrbixPanel OrbixPanel Tutorials

Fix a 403 Forbidden error

A 403 Forbidden means the server found the request but refuses to serve it. Unlike a 404 (not found), the resource is there — the server is saying “you’re not allowed.” A few things cause it.

The usual causes

1. File/folder permissions. The web server can’t read the file. Files should be 644, folders 755 — never 777. If permissions are wrong (or the file is owned by the wrong user), you get a 403. → Fix permission errors

2. No index file. Visiting a folder with no index.html/index.php and directory listing disabled returns 403. Add an index file, or point the URL at a real file. See where files go.

3. A deny rule. An .htaccess (PHP) or server config rule is explicitly blocking the path — e.g. a Require all denied, an IP block, or a rule protecting a directory. Check for a recently added rule.

4. Empty web root. If you deployed but the files landed in a subfolder (or not at all), the root is empty → 403. Make sure files are directly in the web root.

5. Blocked by security rules. A firewall/WAF or fail2ban ban can return a 403/denial for a flagged IP. If it’s only you getting blocked, check whether you were banned.

How to pin it down

  1. Is it the whole site or one path? Whole site → likely empty root or a global deny. One path → permissions or a rule on that path.
  2. Check permissions on the file/folder.
  3. Look for an index file.
  4. Check for a recent .htaccess/config change.
  5. Read the server log — it says why it denied the request.

Running OrbixPanel? The File Manager sets correct ownership, avoiding the most common 403 cause. OrbixPanel.com → — the free, self-hosted, AI-powered hosting control panel.