Quick answer: Chrome mobile data not working on Android is usually caused by a bad DNS setting, VPN/proxy, carrier APN issue, or a firewall/filter blocking Chrome traffic on mobile data. Turn off VPN/proxy, set DNS to Automatic, and test Chrome on both mobile data and Wi‑Fi to isolate the failing network path.
Quick Fix Checklist
- Turn off any VPN, proxy, or private DNS setting in Android.
- Switch Chrome from mobile data to Wi‑Fi, then back to mobile data to compare behavior.
- Open a different site in Chrome to see whether only some domains fail.
- Check your carrier APN and make sure mobile data is enabled for Chrome traffic.
- Disable any firewall, data saver, or carrier filtering feature that may block browser traffic.
- Set Android network settings to automatic DNS if you changed them manually.
Causes
When Chrome works on Wi‑Fi but not on mobile data, the problem is usually in the mobile network path rather than the browser itself. The table below shows the most common network causes.
| Cause | What it means | Fix |
|---|---|---|
| Private DNS or custom DNS | Chrome cannot resolve sites correctly over the carrier network | Set DNS to Automatic or disable Private DNS |
| VPN or proxy | Traffic is routed through a server that blocks or breaks mobile data requests | Turn off VPN/proxy and retest |
| Carrier APN issue | Your mobile data profile is not routing browser traffic correctly | Reset APN to default carrier settings |
| Firewall or data saver | Android or a security app is limiting Chrome on cellular data | Allow Chrome on mobile data and disable restrictive filtering |
| ISP/carrier filtering | The carrier is blocking or throttling certain domains or protocols | Test another network or contact the carrier |
Step-by-Step Fix
- Test Chrome on Wi‑Fi and mobile data separately. Open the same website on Wi‑Fi, then turn Wi‑Fi off and try again on mobile data. If Chrome fails only on mobile data, the issue is with the carrier path, APN, DNS, or filtering.
- Turn off VPN, proxy, and Private DNS. In Android network settings, disable any VPN and set Private DNS to Automatic or Off. If you use a proxy, remove it and retry Chrome.
- Check Chrome on a second site. Try a well-known site and one different domain. If only some sites fail, the carrier or DNS may be blocking specific routes or domains.
- Reset the APN to your carrier default. Go to Mobile Network settings, open Access Point Names, and choose the default APN from your carrier. A wrong APN can break browser traffic even when signal bars look normal.
- Disable data saver and firewall filtering. Turn off Data Saver, battery-based network restrictions, and any security app firewall that can block Chrome on cellular data. Then retest on mobile data.
- Flush the network path with Airplane mode. Turn Airplane mode on for 10 seconds, then off. This forces Android to rebuild the mobile data route and can clear a stuck carrier session.
- Set DNS back to automatic and retest. If you use a custom DNS app or manual DNS, switch it off. Bad DNS is one of the most common reasons Chrome loads on Wi‑Fi but not on mobile data.
Still Not Working
- Run an advanced DNS test. Compare Chrome with and without Private DNS, and try a known reliable resolver only if your carrier allows it. If one DNS works and another fails, the issue is DNS routing or filtering.
- Try another SIM or another carrier network. If Chrome works on a different SIM, the original carrier is likely filtering or misrouting mobile browser traffic.
- Reset network settings. This clears saved Wi‑Fi, mobile data, VPN, proxy, and APN configuration that can keep Chrome from reaching the internet over cellular data.
- Check for carrier-side restrictions. Some plans block tethering, secure DNS, or certain ports. Contact the carrier and ask whether browser traffic, DNS, or HTTPS filtering is active on your line.
- Test with a different browser on mobile data. If other browsers also fail, the problem is almost certainly carrier, APN, DNS, or firewall related rather than Chrome-specific.
Frequently Asked Questions
Why does Chrome work on Wi‑Fi but not on mobile data on Android?
That usually points to a carrier APN, DNS, VPN/proxy, or filtering issue on the cellular route.
Can Private DNS stop Chrome mobile data from working?
Yes. A bad or blocked DNS resolver can prevent Chrome from loading sites over mobile data even when signal is strong.
Should I reset APN if Chrome only fails on mobile data?
Yes. A wrong APN is one of the fastest ways to fix browser traffic that fails only on cellular data.
Does a VPN affect Chrome on Android mobile data?
Yes. VPNs and proxies can break routing, DNS, or certificate checks and make Chrome fail on mobile data.
How do I know if my carrier is blocking Chrome traffic?
If Chrome fails on mobile data across multiple sites and works on Wi‑Fi or another SIM, the carrier is the most likely cause.