CORS HTTP Origin: Network OSI layer 7 · Application Last updated 18 Nov 2026

CORS: Private Network Access preflight blocked (public site calling localhost/intranet)

Chrome blocks a public website from reaching a private IP, localhost or intranet service without explicit permission.

Exact message you may see Private Network Accesshas been blocked by CORS policy: Permission was denied for this request to access the `unknown` address spacePermission was denied for this request to access the `local` address space
Seen on: HTTP Browser Chrome

Meaning

Requests from a public origin to a more private address trigger a PNA preflight with Access-Control-Request-Private-Network: true. The server must answer Access-Control-Allow-Private-Network: true plus normal CORS headers, and the page must be served over HTTPS.

Common causes

  • Public page calling 192.168.x.x or localhost
  • Server not sending Allow-Private-Network
  • Mixed content with the private target
  • Chrome PNA enforcement enabled
  • Device/router API called from the web

⚡ Quick fix

  1. Return Access-Control-Allow-Private-Network: true on the preflight
  2. Serve the page over HTTPS
  3. Proxy through a public backend instead

Detailed fix by platform

Express

  1. app.options("*", (req, res) => { res.set("Access-Control-Allow-Private-Network", "true"); res.sendStatus(204); });

How to diagnose

  1. Target — Private address?
  2. PNA header — Returned?
  3. Page — HTTPS?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

405 — 405 Method Not Allowed on OPTIONS (CORS preflight) (HTTP)405axios — Axios "Network Error" with no response (CORS, DNS, offline or mixed content) (HTTP)axiosCORS — CORS Error: No 'Access-Control-Allow-Origin' header is present (API)CORSCORS — CORS: wildcard '*' not allowed when the request's credentials mode is 'include' (HTTP)CORSCORS on errors — CORS error hides the real failure: Access-Control-Allow-Origin is missing on 4xx/5xx responses (HTTP)CORS on errorsCORS preflight — CORS: Response to preflight request doesn't pass access control check: no HTTP ok status (HTTP)CORS preflightCT — NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED — certificate not logged in Certificate Transparency (SSL / TLS)CTERR_SSL_KEY_USAGE_INCOMPATIBLE — Chrome: ERR_SSL_KEY_USAGE_INCOMPATIBLE — the certificate's key usage doesn't allow the negotiated cipher (SSL / TLS)ERR_SSL_KEY_USAGE_INC…CORS

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.