Errors / HTTP errors

403 Forbidden openresty

The site's server (OpenResty, a build of nginx) refused the request, often through a hosting company's firewall.

Whoever matches the rule cannot use the site.

Seeing it on someone else’s site?

The site or its host is blocking this request; a VPN, a country block or a security rule are the common reasons.
Only the site's owner, or their host, can lift it.

Why it happens, if it is your site

OpenResty is nginx with Lua scripting, used by many hosts, CDNs and web application firewalls; its 403 is often a security rule at the host, not the site's own code.
The same causes as nginx: file permissions, a missing index file, a deny rule.

How to fix it

If you own the site, ask the host which rule blocked the request (give them the time and the address), or check their WAF settings.
Otherwise, check permissions and index files as for nginx.

Whose problem it is

Usually the server that answers the request.

Does your site have it?

Free, no account. We open your page and four more in a clean Chrome and list every error like this one, with the page and the click that caused it. How the free page check works.

Often seen with

403 ForbiddenThe server understood the request and refuses to let you see this.
403 Forbidden (nginx)nginx found the path but is not allowed to serve it.
403 Forbidden on CloudflareCloudflare, in front of the site, decided this request should not reach it.