You look at the status bar and the Wi-Fi icon is full. The router lights are green. Then you open YouTube, Gmail or the Play Store and get a blank screen or a “No internet connection” message. You switch to mobile data and everything loads instantly.
If that sounds familiar, you are dealing with one of the most confusing problems on Android: apps not working on Wi-Fi while the phone still shows it as connected. Since Android 17 started rolling out to Pixel phones on June 16, 2026, this has become a very common complaint, with reports coming from owners of devices ranging from the Pixel 7 to the Pixel 10 series.
The good news is that this problem is usually fixable in a few minutes, and most of the time the fix is on the router, not the phone. This guide walks through the real causes and 9 fixes, in the order that is most likely to work.
Quick Answer
Quick Answer: The most commonly reported fix is turning on IPv6 in your router settings, then restarting both the router and the phone. If IPv6 is already on, try the opposite (set it to Auto or turn it off), switch your Private DNS provider, and make sure you are not running two routers back to back (double NAT). If nothing works, reset network settings as a last step. Do not factory reset your phone first, because affected users report that it did not help.
Why This Is Happening
This is not one single bug. Several different problems produce the same symptom: Wi-Fi shows connected, but some or all apps cannot reach the internet. Here are the causes worth checking.
1. Your router has IPv6 turned off
The leading theory behind the Android 17 reports is that the system leans on IPv6 for some Google services. When the router does not offer IPv6, those requests can fail even though the connection looks healthy.
Clue/Sign: Google apps (YouTube, Gmail, Play Store, Google Photos) fail on Wi-Fi, but many other apps still work, and everything works on mobile data.
2. IPv6 is on but broken on the ISP side
Turning IPv6 on is not a guaranteed fix. If your router advertises IPv6 but your internet provider does not deliver it properly, apps can hang while waiting for a connection that never completes. Some users on other Android phones have reported that disabling IPv6 on the router was the only thing that worked.
Clue/Sign: The problem got worse after you enabled IPv6, or it only started after your ISP changed something on their side.
3. A DNS problem
If the DNS server your phone or router uses is slow or returning bad answers, apps fail to find the servers they need. The phone’s Private DNS setting can also interfere.
Clue/Sign: Changing the DNS provider fixes it instantly, or the problem appears on one Wi-Fi network but not on a hotspot from another phone.
4. Double NAT (two routers in a row)
Many homes have an ISP modem and a second Wi-Fi router plugged into it. Both devices hand out private addresses, which can break how some apps connect. Reports of workarounds involving double NAT and VPNs point in this direction.
Clue/Sign: You have more than one router or modem in the chain, and a VPN makes the problem disappear.
5. A VPN, ad-blocker or DNS filter app
Apps that reroute your traffic can block or delay connections for specific apps.
Clue/Sign: Apps start working the moment you turn the VPN or filter off.
6. A stale network state after an update
After a big system update, saved Wi-Fi settings and cached connection data can get out of sync.
Clue/Sign: Turning Wi-Fi off and on fixes it for a few minutes, then it comes back.
9 Fixes for Android Apps Not Working on Wi-Fi
Fix 1: Confirm it is the Wi-Fi, not the app
Before changing anything, find out where the problem lives. Switch off Wi-Fi and open the app on mobile data. Then connect to a different Wi-Fi network, or use a hotspot from another phone. Finally, check whether another device on your home Wi-Fi has the same problem.
Test: If the app works on mobile data and on another network, the problem is your home network setup. If other devices on your Wi-Fi are fine, the problem is specific to your phone.
Fix 2: Toggle Wi-Fi and Airplane mode
Turn Wi-Fi off, wait 10 seconds, and turn it back on. If that does not help, turn Airplane mode on for 15 seconds and off again. This forces the phone to rebuild its network connection.
Test: Open the app that was failing. If it loads, the cause was a stale connection. If the problem returns within minutes, keep going, because the real cause is still there.
Fix 3: Restart the phone and power-cycle the router
Restart the phone fully. Then unplug the router from power, wait at least 30 seconds, and plug it back in. Restarting both matters, because only restarting the phone leaves the router’s network state unchanged.
Test: Wait for the router lights to settle, reconnect the phone, and open YouTube or Gmail.
Fix 4: Turn on IPv6 in your router
This is the fix reported most often. Open your router’s admin page in a browser (the address is usually printed on the router label, commonly 192.168.1.1 or 192.168.0.1) and sign in. Look under Internet, WAN, Network or Advanced settings for an IPv6 option. Set it to Auto or enable it, save, and let the router reboot.
After the router restarts, turn Wi-Fi off and on again on your phone.
Test: Open a Google app on Wi-Fi. You can also visit test-ipv6.com on your phone to see whether IPv6 is working on your connection.
Fix 5: If IPv6 is already on, try the opposite
IPv6 is not the whole story. If you already have it enabled and the problem persists, set IPv6 to off (or back to Auto if it was manually configured) and test again. Users have reported success both ways, because the real issue depends on how your ISP and router handle it.
Test: Change one setting at a time, restart the router, and test after each change. Changing several things together makes it impossible to know what worked.
Fix 6: Change your DNS
On the phone, open Settings, go to Network and internet, then Private DNS. If it is set to Automatic, try a provider hostname such as dns.google or 1dot1dot1dot1.cloudflare-dns.com. One Pixel 8 user reported that forcing Cloudflare’s Private DNS hostname worked around the issue. If you have a custom provider set and things are broken, switch back to Automatic.
You can also change the DNS on the router itself to 1.1.1.1 or 8.8.8.8, which fixes it for every device in the house.
Test: Reconnect to Wi-Fi after the change and open the failing app.
Fix 7: Remove double NAT
If you have an ISP modem plus your own router, the cleanest fix is to put the ISP device into bridge mode so only one device is routing. If that is not possible, connect your router’s WAN port to the modem and, where available, use the modem’s “DMZ” or “IP passthrough” option for your router. The exact name differs between brands, so check your modem’s manual.
Test: After the change, restart both devices and test the app. If your problem was double NAT, a VPN was probably also a temporary workaround for you.
Fix 8: Turn off VPN, ad-blocking and DNS filter apps
Disable any VPN, private DNS app, ad blocker or “secure browsing” tool, then test again. Check Settings, then Network and internet, then VPN to make sure nothing is running in the background.
Test: If the app works with the VPN off, review that VPN’s settings or try a different server before turning it back on.
Fix 9: Reset network settings (last resort)
On a Pixel, go to Settings, System, Reset options, then choose Reset Wi-Fi, mobile and Bluetooth. This clears saved Wi-Fi networks, paired Bluetooth devices and mobile settings, so you will need to re-enter your Wi-Fi passwords. The menu names vary slightly on other brands.
Test: Reconnect to your Wi-Fi and open the failing app. Also check for a pending system or security update under Settings, System, Software updates, since fixes for connectivity bugs usually arrive that way.
Troubleshooting Table
| What you see | Most likely cause | Try this first |
|---|---|---|
| Only Google apps fail on Wi-Fi | Router IPv6 turned off | Fix 4 |
| Worked until you enabled IPv6 | IPv6 not delivered by ISP | Fix 5 |
| Works on mobile data and hotspot only | Router or DNS issue | Fixes 3, 6 |
| Two routers or modem plus router | Double NAT | Fix 7 |
| Works only with a VPN on | Double NAT or routing issue | Fixes 7, 8 |
| Fixed for a few minutes after toggling Wi-Fi | Stale connection state | Fixes 2, 3, 9 |
| All devices on the Wi-Fi are affected | Router or ISP problem | Fixes 3, 4, 5 |
Pro Tips
- Change one thing at a time. Restart, test, then move on. It is the only way to learn which setting actually fixed the problem.
- Write down your router’s original settings before changing IPv6 or DNS, so you can undo them quickly.
- Use mobile data as a diagnostic tool. If an app works there and not on Wi-Fi, you have already ruled out the app and the phone’s basic function.
- Keep your router firmware updated. Manufacturers regularly fix IPv6 and DNS handling bugs in new firmware.
- Check your other devices. If a laptop or another phone on the same Wi-Fi also struggles, skip the phone fixes and go straight to the router.
If your Wi-Fi also drops at regular times, see our guide on why WiFi drops at the same time every day. For general slowness after a restart, read router restarted but internet is still slow, and if your router lights look wrong, check router blinking red light with no internet. Android 17 users with mobile network trouble can also read our fix for 5G switching to LTE.
Common Mistakes
- Factory resetting the phone first. Affected users who tried this and even factory reset the router reported that it did not solve the problem. Try the targeted fixes before wiping anything.
- Only restarting the phone. The router also needs a power cycle, or the problem can come straight back.
- Changing IPv6, DNS and NAT settings all at once. You will never know which change helped, or which one broke something else.
- Forgetting to save and reboot the router after changing settings. Many routers apply IPv6 changes only after a restart.
- Blaming the app. If it works on mobile data, the app is fine. Reinstalling it rarely helps in this situation.
Frequently Asked Questions
Why do Google apps fail while other apps work on Wi-Fi?
Reports suggest Google services are hit hardest because they appear to prefer IPv6 on Android 17. Some third-party apps have also been affected, so it is not exclusive to Google apps.
Is this an Android 17 bug or a router problem?
It looks like a mix of both. The phone update seems to expose a router or network setup that previously worked well enough, which is why some users never see the problem at all on the same phone model.
Is it safe to enable IPv6 on my router?
Yes, IPv6 is the standard, current internet addressing system, and most modern routers support it. If your internet provider does not support it, the router may simply not use it, and in that case Fix 5 may be the better option.
Will Google fix this with an update?
Google has not given a guaranteed timeline in the reports I found, so install the latest system and security updates when they appear and test again. The router and DNS fixes above work without waiting.
Does this only affect Pixel phones?
The Android 17 reports mostly come from Pixel owners, but similar symptoms with IPv6 and DNS have been reported on other Android phones and networks. The fixes here apply to any Android device.
The Wi-Fi says “connected, no internet” on every app. Is that the same problem?
It can be. If every app fails and other devices fail too, the cause is more likely your router or ISP. Start with Fixes 3, 4 and 5.
Final Thoughts
When Android apps stop working on Wi-Fi while mobile data works fine, the problem is almost always how your phone and your router handle IPv6, DNS or double NAT. Start with the quick restarts, then make the IPv6 change on your router, and work down the list one fix at a time. If you find the setting that fixed it for you, tell us in the comments, because router brands differ and your answer may help the next person.