Chrome: This site can’t be reached — ERR_NETWORK_ACCESS_DENIED (blocked by firewall or antivirus)
Something on your computer — usually the Windows firewall or antivirus — denied Chrome network access.
Network access denied Meaning
The browser itself has no permission to use the network, or a rule blocks it for this destination. It often appears after a security-software update, a Windows reset, or when Chrome was added to a block list.
Common causes
- Windows Defender Firewall or third-party firewall blocking chrome.exe
- Antivirus web protection rule
- Group policy or parental-control rule
- Chrome profile or installation corrupted
- Proxy/VPN software blocking the process
⚡ Quick fix
- Allow Chrome through the firewall (Allow an app through Windows Defender Firewall)
- Temporarily disable antivirus web protection to test
- Reinstall Chrome if only that browser is affected
Detailed fix by platform
Windows
- Control Panel → Windows Defender Firewall → Allow an app → tick Chrome for private and public
netsh advfirewall show allprofilesto check profiles
Chrome
- Test with Edge or Firefox; if they work the block is specific to Chrome's permissions
How to diagnose
- Browser — Do other browsers work?
- Software — Firewall/antivirus rules for chrome.exe?
- Policy — Managed device?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- captive portal Browser: This network requires you to sign in — captive portal (hotel, airport, café Wi-Fi) blocking HTTPS sites
- DNS_PROBE_FINISHED_NO_INTERNET Chrome: No internet — DNS_PROBE_FINISHED_NO_INTERNET (DNS probe finished, no internet)
- DNS_PROBE_FINISHED_NXDOMAIN Chrome: This site can’t be reached — server IP address could not be found. DNS_PROBE_FINISHED_NXDOMAIN
Most viewed in Browser
Other ways to find it
Where this error sits
Origin: On your device. Errors that are often confused with or caused by this one (click to open):
🧠 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.
Report a correction or suggest an improvement
Last updated 15 Oct 2026