Fix Android Connected to WiFi but No Internet (6 Real Solutions)

Short answer: forget the Wi-Fi network and rejoin it. That one move rebuilds the DHCP lease, clears the local DNS cache and re-runs Android’s connectivity check, and it clears most connected-but-no-internet cases in under 30 seconds. If it does not hold, work through a captive portal sign-in (the usual culprit on a hotel or cafe network), then Private DNS, then the router, in that order. Skip the Wi-Fi fixer apps in the Play Store; Android does not let them touch any of this.

Connected, no internet

Four things have to work. Your phone only shows you one of them.

The Wi-Fi icon reports the radio handshake and nothing else. The three steps after it are invisible right up until one of them quietly fails.

1Radio linkYour phone associates with the access point. Signal bars, network name, the word Connected. This part is working.
2AddressThe router’s DHCP server has to hand over an IP address, a gateway, and a DNS server. An expired or refused lease breaks everything downstream.
3Name lookupA resolver has to turn a domain into an address. If Private DNS points at a server the network cannot reach, Android marks the whole network offline.
4ReachabilityAndroid quietly requests connectivitycheck.gstatic.com/generate_204. An empty 204 back means you are online. Anything else, or nothing, and you get the warning triangle.

Read it this way: steps 2, 3 and 4 are where connected-but-no-internet lives. The fixes below are ordered by how often each layer is the guilty one, not by how technical they sound.

Full bars. The network name sitting there with the word Connected under it. And a browser that spins, gives up, and offers to reload. It is a special kind of irritating because nothing looks wrong. Your phone is telling the truth, just not the whole truth: joining a network and reaching the internet are two different events, and only the first one gets an icon.

Here are the six fixes for Android Connected to WiFi but No Internet, in the order that clears the most cases fastest, along with a short map of which layer each one actually repairs. Most people never need to get past the second fix.

Person at a desk holding an Android phone next to a Wi-Fi router that shows a connection but no internet access — The setup where this fault is most maddening: router two feet away, full signal, nothing loading.

Why Android says connected when nothing loads

The Wi-Fi icon reports exactly one fact: your phone has associated with the access point. Handshake done, encryption agreed, signal measured. Between that and a web page there are three more steps, and not one of them has an indicator of its own. Your phone needs an IP address from the router’s DHCP server. It needs a DNS resolver that answers when asked. And it needs a path out past the router to the wider internet.

Android checks that last part on its own, quietly, every time you join a network. It sends a plain HTTP request to connectivitycheck.gstatic.com and expects an empty response with status 204. A real 204 means the path is clear. A 200 or a redirect means something intercepted the request, which is how Android knows to pop the hotel sign-in prompt. Silence means the request never got out, and that is when you get the warning triangle. The exclamation mark next to your Wi-Fi icon is not a complaint about Wi-Fi. It is the score from a test your phone ran without telling you.

That probe is a workaround for a gap the standards world has since closed. The IETF’s RFC 8910, a Proposed Standard, lets the router hand your phone the sign-in URL directly through DHCP, so nothing has to be guessed from a failed request. Adoption on real hardware is still thin, which is why the guess is what you run into at the airport.

The 60-second fix sequence

Run these in order. They are sorted by how often each one is the answer, not by how clever they are, and the first two resolve the large majority of cases without touching the router.

Step 1: Forget the network and rejoin

Open Settings, then Network and internet, then Internet. Tap the network you are on, choose Forget, then reconnect and enter the password again. This is blunt and it works, because it destroys three things at once: the DHCP lease, the saved network profile and the local DNS cache. Your phone then asks the router for a fresh address, and Android re-runs its connectivity check on a clean slate. Have the password to hand before you tap Forget, because the phone will not show it to you afterwards.

Step 2: Look for a captive portal

Cafes, hotels, airports and campus networks route you to a sign-in page before they let anything through. If that page never appears, open a browser and type http://example.com by hand. Two details matter. Use http rather than https, because a portal cannot cleanly intercept an encrypted request, and avoid Google domains, which Android reserves for its own probe. If a login screen appears, you were never online at all. Sign in and the warning triangle clears itself within a few seconds.

Step 3: Set Private DNS back to Automatic

Settings, Network and internet, Private DNS. This one deserves more suspicion than it usually gets. If you pinned a custom DNS hostname and the current network cannot reach it, Android does not fall back and carry on. It marks the entire network as having no internet access, which is precisely the symptom you are trying to fix. Set it to Automatic and try again. Android’s own advanced network settings guide walks through the same screen if you want the official version. If you want encrypted lookups back afterwards, one.one.one.one gets you Cloudflare and dns.google gets you Google, though Automatic already upgrades to encrypted DNS wherever the network supports it. Per Android developer documentation, encrypted DNS transport has shipped since Android 9, and current builds carry DNS over HTTP/3 as well.

Step 4: Toggle airplane mode

Swipe down, tap Airplane mode on, count to five, tap it off. It looks like folklore and it is not. The toggle tears down and re-initialises the whole radio stack, Wi-Fi included, which forces a fresh association and a fresh connectivity check without wiping any saved network. Cheapest thing on this list. Try it before anything that costs you passwords.

Line illustration of a person tapping connectivity toggles on an Android settings screen showing Wi-Fi and Bluetooth — Steps 1 through 4 all live in Settings. None of them need an app.

When the phone is fine and the network is not

Before you go further, run one test that saves a lot of guessing. Check whether another device on the same Wi-Fi can load a page, and whether this phone can load one over mobile data. If every device is stuck, stop blaming the phone. If only this phone is stuck, the two steps below will not help and you should go back to step 1.

Step 5: Restart the router, then the modem

Pull power from the ISP modem first and leave it off for a full 2 minutes. That is long enough for the upstream session to drop properly instead of being handed back the same broken state. Bring the modem up, wait for its lights to settle, and only then power the router back on. Doing it in that order matters: a router that boots before the modem has finished negotiating will come up with no route and hand out addresses that lead nowhere, which produces the exact fault you are trying to clear.

Step 6: Network reset, as the last resort

Settings, System, Reset options, Reset Wi-Fi mobile and Bluetooth. This wipes every saved Wi-Fi network, every Bluetooth pairing and your mobile data preferences, then puts the networking stack back to defaults. It is genuinely effective when the saved configuration itself is corrupt, which is what you should suspect if no Wi-Fi network anywhere works but mobile data is fine. Your photos, apps and accounts are not touched. The cost is an evening of retyping passwords, so treat it as the end of the list rather than a shortcut.

Before you reset: collect the Wi-Fi passwords you actually need first, starting with home and work. Android will not show you a saved password after the reset has run, and car stereos and smartwatches will need pairing again too.

Which fix to try first, by symptom

The fix order above is the safe default, but a specific symptom often points straight at the guilty layer and lets you skip ahead. Match what you are seeing to the closest row, then run that fix first. If it does not clear within 60 seconds, drop back to step 1 and work through the sequence properly.

Which fix first?

Pick the line that matches what you are seeing. The symptom tells you which layer broke, and that decides the order.

Start hereForget the network, then rejoinEvery other device is fine, so the router is fine. The broken piece is phone-side state: a stale DHCP lease or a cached resolver entry. Forgetting the network throws both away and rebuilds them from scratch.

Start hereOpen http://example.com in a browserHotel and airport networks wait for you to load a plain HTTP page before they redirect. If Android’s own probe is blocked, the prompt never fires. Forcing an unencrypted request usually drags the portal into view.

Start hereSet Private DNS back to AutomaticA custom Private DNS hostname that the current network cannot reach makes Android declare the whole connection dead. It is the single most common self-inflicted version of this fault.

Start herePower-cycle the modem, then the routerThis is not an Android problem at all. Pull power from the modem, give it two minutes to renegotiate with the ISP, then bring the router back up after it.

Start hereRun a network resetWhen no saved network works but cellular does, the phone’s saved network configuration is corrupt. A reset wipes Wi-Fi, Bluetooth and mobile preferences, and nothing else.

What you are seeing	Most likely layer	Try this first
Only this phone is offline, other devices are fine	DHCP lease or DNS cache on the phone	Forget the network and rejoin
Public Wi-Fi, sign-in page never appears	Captive portal probe blocked	Open http://example.com in a browser
Broke immediately after you changed a setting	Private DNS hostname unreachable	Set Private DNS to Automatic
Every device in the house is offline	Modem, router or the ISP itself	Power-cycle the modem, then the router
No Wi-Fi network works, mobile data does	Corrupt saved network configuration	Network reset
Connects fine, then drops after a few minutes	Power saving or band roaming, not this fault	See our guide to Wi-Fi that keeps disconnecting

What not to do

The Play Store is full of apps promising to fix, boost or repair your Wi-Fi. They cannot. Android’s permission model does not let an ordinary app renew a DHCP lease, change the system resolver, rewrite a saved network profile or re-run the connectivity probe. Those are privileged operations reserved for the system. What the apps do instead is toggle Wi-Fi off and on, show you a signal graph, ask for location permission they do not need, and serve ads. Every one of those actions is available to you in a single swipe.

The one exception: a read-only Wi-Fi analyzer is a legitimate tool for diagnosing a weak or congested channel. It still cannot fix a DHCP or DNS failure, which is what connected-but-no-internet almost always is. Different problem, different tool.

Frequently asked questions

Why does my phone say Connected but there is no internet?

Joining a Wi-Fi network and reaching the internet are separate events. Association happens at the radio layer, which is what the icon reports. After that your phone still needs a DHCP lease, a DNS resolver that answers, and a clean path upstream. Any one of the three can fail on its own while the signal stays at full strength.

Does turning Private DNS off expose my browsing?

It stops encrypting your DNS lookups, so whoever runs the network can see which domains you request. It does not change what you browse or expose the contents of an HTTPS page. Set it to Automatic rather than Off, so encryption comes back the moment the network supports it.

Will a network reset delete my photos or apps?

No. It clears saved Wi-Fi networks, Bluetooth pairings and mobile data preferences. Photos, apps, messages and accounts are untouched. The only real cost is retyping Wi-Fi passwords, so collect the ones you need first.

Why does the hotel sign-in page never load?

The portal is waiting for a plain HTTP request it can hijack, and modern browsers default to HTTPS. Type an http:// address by hand and avoid Google domains, which Android reserves for its own connectivity probe.

My laptop works on the same Wi-Fi. Why not my phone?

That result narrows it down usefully. The router, the modem and the ISP are all fine, so the fault is phone-side. Start with Forget and rejoin, then check Private DNS. Skip the router steps entirely.

Do Wi-Fi booster or fixer apps help?

No. Android’s permission model blocks a normal app from renewing a DHCP lease, changing the system resolver or re-running the connectivity check. The most they can do is toggle Wi-Fi off and on, which you can do yourself in one swipe.

Bottom line

Connected-but-no-internet is almost always a 60-second fix on Android. Forget and rejoin, check for a captive portal, set Private DNS to Automatic, and toggle airplane mode. If those fail, restart the router or do a full network reset. Skip the third-party fixer apps.

And sometimes the honest answer is that the Wi-Fi is not worth rescuing. If the line drops every evening, or there is no fixed connection to fall back on, the quickest route online is the phone’s own hotspot, which turns cellular data into a small Wi-Fi network for your other devices. For something more permanent, a 5g wireless internet delivers home internet over the same cellular towers, with a router that converts the signal to Wi-Fi indoors. In places where fibre never arrived or the cable line is unreliable, that is often the steadier option rather than the compromise.

Sixty-second triage: forget and rejoin, then http://example.com, then Private DNS to Automatic, then airplane mode. Still nothing? The problem is upstream of your phone.

How we put this guide together

The picks and steps in this guide reflect what works on current Android builds. Our editors test apps on Pixel 8a and Galaxy S24 hardware running Android 15 and Android 16, cross-check against vendor documentation, and update each guide when behavior changes.