Chrome Not Working? The Fastest Safe Troubleshooting Path

Quick answer: Chrome not working on WiFi is usually caused by bad DNS resolution, a proxy or VPN intercepting traffic, or router/firewall filtering that blocks Chrome’s web requests. Start by switching Chrome and your device to a public DNS like 1.1.1.1 or 8.8.8.8, then disable any VPN or proxy and test the same site on mobile data to confirm the WiFi path is the problem.

Quick Fix Checklist

• Turn off any VPN or proxy and retry Chrome on WiFi.
• Change DNS to 1.1.1.1 or 8.8.8.8 on the device or router.
• Restart the router and reconnect to the WiFi network.
• Test Chrome on mobile data to see whether the issue is WiFi-specific.
• Check firewall, parental controls, or security filtering on the router.
• Try another WiFi network to rule out ISP or router filtering.

Causes

When Chrome fails only on WiFi, the problem is usually in the network path between your device and the internet, not in Chrome itself.

Cause	What it means	Fix
DNS failure	Chrome cannot translate website names into IP addresses on that WiFi network.	Switch to a public DNS server and flush the local DNS cache.
VPN or proxy	Traffic is being routed through a tunnel or proxy that breaks Chrome requests.	Disable VPN/proxy and retest on the same WiFi.
Router firewall or filtering	The router is blocking certain domains, ports, or secure connections.	Review router security, parental controls, and content filters.
ISP or carrier filtering	Your internet provider is blocking or misrouting some web traffic.	Test another network and contact the ISP if the issue follows the connection.
WiFi routing problem	The WiFi link works, but traffic is not being routed correctly to the web.	Restart the router, renew the IP lease, or change DNS at the router.

Step-by-Step Fix

1. Test Chrome on mobile data. If Chrome works on mobile data but not WiFi, the issue is tied to the WiFi network, router, DNS, or ISP path.
2. Disable VPN and proxy settings. Turn off any VPN app, then check system proxy settings and make sure no manual proxy is enabled.
3. Change DNS to a public resolver. Set DNS to 1.1.1.1 and 1.0.0.1 or 8.8.8.8 and 8.8.4.4 on the device, or better, on the router so every device uses the same working DNS.
4. Restart the router and reconnect. Power the router off for 30 seconds, turn it back on, then reconnect the device to refresh routing and DHCP.
5. Check router firewall and filtering. Look for parental controls, safe browsing filters, DNS filtering, ad blocking, or access control rules that may block Chrome traffic.
6. Renew the WiFi lease. Forget the WiFi network, reconnect, and if possible renew the IP address so the device gets a clean route from the router.
7. Try a different WiFi network. If Chrome works elsewhere, the original router or ISP path is the source of the block.

Still Not Working

1. Flush DNS and reset the network stack. Clear the device DNS cache and renew the network configuration so Chrome stops using stale routing data.
2. Set DNS at the router level. If only one device is affected, the router may still be handing out bad DNS; set the router’s WAN or DHCP DNS to a public resolver.
3. Check IPv6 behavior. Some WiFi networks fail on IPv6 while IPv4 works; temporarily disable IPv6 on the router or device to test.
4. Inspect ISP filtering or outage reports. If multiple devices fail on the same WiFi and other networks work, ask the ISP whether DNS, routing, or security filtering is affecting web access.
5. Use a hotspot test. Connect the device to a phone hotspot; if Chrome works there, the router or ISP path is confirmed as the issue.

Frequently Asked Questions

Why does Chrome not work on WiFi but other apps do?
Chrome depends heavily on DNS and secure web routing, so a WiFi DNS, proxy, or filtering problem can break browsing while other apps still connect.

Should I change DNS on the router or the device?
Router-level DNS is better because it fixes the WiFi network for every device, but device-level DNS is a fast test.

Can a VPN cause Chrome not working on WiFi?
Yes. A VPN can reroute or block web traffic, especially if the tunnel is unstable or the VPN DNS is failing.

How do I know if the router is blocking Chrome?
If Chrome fails on one WiFi network but works on mobile data or another WiFi, router filtering, firewall rules, or DNS settings are likely involved.

Could my ISP be the reason Chrome is not working on WiFi?
Yes. ISP DNS issues, routing faults, or filtering can stop Chrome from loading sites even when the WiFi signal is strong.