WiFi Connected But No Internet on Android? Here's How to Find Out Why

Posted on08 September 2026

Short answer: When Android shows Wi-Fi connected but nothing loads, there are five likely causes in this order: a captive portal sign-in page you never saw, a problem in Android System WebView affecting only in-app browsers, a Private DNS setting pointing at an unreachable provider, a VPN that connected but did not finish routing, or the router itself. Test Chrome against an app that shows web content — if Chrome works and the app does not, the network is fine and WebView is the problem.

Your phone says it's connected to Wi-Fi. The icon is full. And nothing loads.

Most advice for this starts with "restart your router," which sometimes works and teaches you nothing. If it keeps happening, or it happens on one app but not another, the useful question isn't *how do I make it go away* — it's *which part of the chain is actually broken*. There are about five candidates, and you can tell them apart in a couple of minutes.

Find the broken link in the chain

DeviceGPT for Android · free · no root

Install

First, rule out the boring one: the sign-in wall

If you're on café, hotel, airport, campus or hospital Wi-Fi, the network has probably attached you but is holding you at a login page you never saw. This is a captive portal. Your phone is genuinely connected — to the router. The router just won't pass you through to anywhere else until you accept terms or enter a room number.

The tell: Android usually shows a small "Sign in to network" notification, but it's easy to swipe away, and on some builds it doesn't appear at all. Open any plain `http://` site (not https) and see whether you get redirected somewhere unexpected.

If that's it, you're done. If you're on your own home Wi-Fi, it isn't it — keep going.

Second: is it the whole phone, or one app?

This is the split that matters most, and almost nobody checks it.

Open Chrome and load a site. Then open a different app that shows web content — a news app, a banking app, anything with an in-app browser. If Chrome works and the other app doesn't, the network is fine and you've found something much more specific: Android System WebView.

WebView is the component apps use to display web pages inside themselves without opening a browser. It's a separate piece of software from Chrome, updated separately through the Play Store, and it has its own DNS resolver, its own connection pool, and its own TLS handling. That's not a detail — it means WebView can fail while Chrome, and every network test you run, says everything is fine.

When that happens the usual advice sends you round in circles, because every tool you reach for is testing the stack that works.

To fix it: Play Store → search "Android System WebView" → Update. Then force-stop the app that was failing and reopen it. On some devices you may also need to update Chrome itself, since recent Android versions share code between them.

Third: DNS

DNS turns `example.com` into an IP address. If it's broken, everything looks connected and nothing resolves.

Two common causes on a phone:

Private DNS. Android has a Private DNS setting (Settings → Network & internet → Private DNS). If it's set to a specific provider and that provider is unreachable — or blocked on the network you're using — every lookup fails while Wi-Fi shows connected. Setting it to "Automatic" is a fast way to test.

A VPN that's half-up. A VPN that has connected but not finished routing will do exactly this. Toggle it off and retry before you blame anything else.

Fourth: the site is up, but only sometimes

A site that fails intermittently is the hardest to diagnose, because one successful check convinces you it's fine and one failed check convinces you it's down. Neither is evidence. You need several attempts, and you need to know how many passed.

This is where "it works on my phone" arguments usually die: someone tested once, got lucky, and closed the case.

Fifth: it really is the router

If Chrome fails too, DNS is default, no VPN is running, and other devices on the same network also can't load anything — now restart the router. It's last on this list, not first, because it's the one thing that's already been tried before anyone searches for this.

Doing all of that in one place

Checking these by hand works. It's also fiddly, and the WebView-versus-Chrome distinction is the part people miss because it needs two apps and a bit of luck to notice.

DeviceGPT has a tab called App Doctor built for exactly this. You type in a website and it:

tests it four times, not once, so a site that fails intermittently can't hide behind one

lucky attempt

tests through both the normal Android connection and the in-app browser stack, so it

can tell you when WebView is the problem and Chrome is fine — the case that sends people in circles

shows your DNS servers, whether Private DNS or a VPN is active, and whether the

network is holding you at a captive portal

reports how many attempts passed and the average latency, rather than a single green tick

It's free, it doesn't need root, and the scan stays on your device.

The short version

What you see	Likely cause	Check
Café/hotel Wi-Fi, nothing loads	Captive portal	Open any `http://` site, look for a redirect
Chrome works, other apps don't	Android System WebView	Update WebView in the Play Store
Everything fails, connected icon full	DNS or Private DNS	Set Private DNS to Automatic
Started right after connecting to a VPN	VPN half-routed	Toggle the VPN off
Fails sometimes, works sometimes	Needs repeat testing	Test 4+ times, count the passes
All devices on the network fail	Router	Restart it — last, not first

---

Frequently asked questions

What is Private DNS?

An Android setting (Settings, Network and internet, Private DNS) that routes your DNS lookups through a specific encrypted provider. If that provider is unreachable, or blocked on the network you are using, every lookup fails while Wi-Fi still shows as connected. Setting it to Automatic is a fast way to test.

Why does my wifi say connected but no internet?

Five common causes: a captive portal sign-in page you never saw, a fault in Android System WebView affecting only in-app browsers, a Private DNS provider that cannot be reached, a VPN that connected but did not finish routing, or the router. Test Chrome against an app that shows web content — if Chrome works and the app does not, the network is fine.