The server understood the request and refuses it. Either the files cannot be read — wrong permissions, or a folder with no index page — or a rule says no: a deny line in .htaccess, a security plugin, or a web application firewall such as ModSecurity. The error log names the rule.
Forbidden You don't have permission to access this resource.
How 4 other clients word the same error
nginx
403 Forbidden nginx
OpenLiteSpeed
403 Forbidden Access to this resource on the server is denied!
IIS
HTTP Error 403.14 - Forbidden: The Web server is configured to not list the contents of this directory.
curl -I
HTTP/2 403
| Error | 403 Forbidden |
| Usually fixed by | The site owner or host |
| Status | 403 (RFC 9110 §15.5.4) |
| Means | The server refuses — not a missing page (404), not a sign-in (401) |
| Folders need | 755 (enter and list); files 644 (read) |
Check the site from outside
Enter the address: we load it from our network and show the status code, how long it took, and the error if it failed.
What it means
Unlike 401, signing in does not help with a 403: the server knows what is being asked for and will not give it. Sometimes that is the file system — the web server cannot read the file or enter the folder — and sometimes a rule, written by the site or by a firewall, decided to block this request.
Why it happens
- Wrong permissions or ownership: a folder without execute permission, a file the web server cannot read.
- A folder with no index.php or index.html, where listing the files is turned off.
- A deny rule in .htaccess or the server configuration — by IP address, country or path.
- A security plugin or web application firewall (ModSecurity, Imunify360, Wordfence) blocking the request or the visitor’s address.
- Hotlink protection refusing images requested from another site.
What the error log says
Apache, a deny rule
AH01630: client denied by server configuration: /home/user/public_html/wp-admin
Apache, no index file
AH01276: Cannot serve directory /home/user/public_html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
Apache, a folder it cannot enter
AH00529: /home/user/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable and that '/home/user/public_html/' is executable
nginx, no index file
directory index of "/var/www/site/" is forbidden
nginx, file permissions
open() "/var/www/site/index.html" failed (13: Permission denied)
nginx, a deny rule
access forbidden by rule
ModSecurity
ModSecurity: Access denied with code 403 (phase 2). Matched phrase "wp-config" at REQUEST_URI.
How to fix it
- Check the error log at the time of the request — the lines below name the cause.
- Set folders to 755 and files to 644, owned by the account’s user.
- Make sure the folder has an index file, or allow listing if that is intended.
- Look for deny rules in .htaccess, and for the request in the security plugin’s or firewall’s log (cPanel: ModSecurity Tools).
If you are visiting the site
- If the page opens for others, your address may be blocked: try another network or turn off a VPN. Otherwise the site owner has to change the rule or the permissions.
See it for yourself
curl -sI https://example.com/private/
ls -ld /var/www/site /var/www/site/index.php
If curl gets the 403 too, the cause is on the server; if only you do, a rule is blocking your address.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- RFC 9110: HTTP Semantics — rfc-editor.org
- httpd/modules/http/http_protocol.c at 2.4.x — github.com
- httpd/modules/aaa/mod_authz_core.c at 2.4.x — github.com
- nginx/src/http/ngx_http_core_module.c at master — github.com
- Troubleshoot ASP.NET Core on Azure App Service and IIS — learn.microsoft.com