VPN Connected but No Internet on Android: Fix Guide (2026)

Seeing “Connected” in your VPN app but having no internet is frustrating—and surprisingly common on Android. The good news is that this usually has a clear cause: DNS settings, Wi-Fi login pages, restrictive networks, or a protocol mismatch.

This guide is designed to be calm and practical. You will run a 1-minute diagnostic test first, then follow fixes grouped by cause. Most people resolve it within a few steps.

You do not need advanced tools. You only need the Settings app, a browser, and a bit of patience.

If you use NimbusVPN, you also have two protocol options (WireGuard and XRay (VLESS/Reality)) plus Split Tunneling, which can help in some cases—but this guide applies to most Android VPN apps.

Quick Summary

• First, confirm whether the internet works without the VPN.
• Fix Date & Time (automatic) if it is wrong.
• Temporarily disable Private DNS to rule out DNS conflicts.
• On hotel Wi-Fi, complete the login page before turning on the VPN.
• If Wi-Fi is restrictive, try switching protocols (WireGuard ↔ XRay (VLESS/Reality)).
• If only one app is broken, use Split Tunneling instead of changing everything.
• When in doubt: reconnect VPN, toggle airplane mode, or reboot once.

Why “VPN connected but no internet” happens

A VPN connection has two layers:

1. The VPN tunnel connects (your app shows “Connected”).
2. Traffic inside that tunnel successfully reaches the internet (websites load).

When you see “Connected but no internet,” it usually means the first layer is fine, but something breaks in the second layer—most often DNS resolution or blocked traffic on the current network.

Common triggers include:

• Incorrect device time (breaks secure connections)
• Private DNS settings conflicting with VPN DNS routing
• Wi-Fi networks that require a login page (captive portals)
• Restrictive Wi-Fi that blocks certain VPN patterns
• A server location that is too far or temporarily unstable
• App-specific routing and compatibility issues

Quick diagnostic checklist (1-minute test)

Do this before changing a lot of settings:

1. Disconnect the VPN.

   • Open a browser and load a simple site.
   • If the internet does not work without VPN, the VPN is not the main problem. Fix Wi-Fi/mobile data first.

2. Reconnect the VPN.

   • Try loading the same site.

3. Try two different apps.

   • Browser + a second app (for example, a messaging app).
   • If one works and the other does not, it is likely an app-specific routing issue.

4. Switch networks quickly (if possible).

   • Test on mobile data vs Wi-Fi.
   • If it works on one network but not the other, the network is restrictive or misconfigured.

Now follow the cause-based fixes below.

Troubleshooting by cause

1. Wrong Date & Time

If your device time is off, secure connections can fail (especially HTTPS). A VPN may connect, but apps cannot establish trusted connections.

Fixes:

• Set time automatically: Settings → System → Date & time → enable Set time automatically.
• Also enable Set time zone automatically.
• Reboot the phone and reconnect the VPN.

Protocol to try first: WireGuard (protocol is usually not the root cause here).

2. Private DNS conflicts

Private DNS can override DNS resolution in ways that clash with VPN routing. This can look like “connected but nothing loads” or “some sites do not resolve.”

Fixes:

• Temporarily disable Private DNS: Settings → Network & internet → Private DNS → Off.
• Reconnect the VPN after changing it.
• If you need Private DNS later, turn it back on and test carefully.

Protocol to try first: WireGuard.

3. Captive portal networks (hotel Wi-Fi)

Many hotel and airport networks require you to accept terms or log in on a web page. VPN traffic may be blocked until that step is completed.

Fixes:

• Disconnect VPN.
• Open a browser and visit any HTTP site (some portals redirect better on HTTP).
• Complete the login/accept page.
• Confirm normal internet works.
• Reconnect VPN.

Protocol to try first: WireGuard first; switch to XRay (VLESS/Reality) if the network blocks typical VPN patterns.

4. Restrictive Wi-Fi networks

Some networks block VPN traffic patterns, limit unknown protocols, or interfere with encryption. Your VPN may show “Connected” but traffic does not pass reliably.

Fixes:

• Switch protocol (WireGuard ↔ XRay (VLESS/Reality)).
• Try another nearby server location (do not jump far yet).
• If available, switch Wi-Fi band (2.4 GHz ↔ 5 GHz) or use Ethernet on Android TV boxes.
• Test on a phone hotspot to confirm the Wi-Fi network is the problem.

Protocol to try first: XRay (VLESS/Reality) on restrictive networks.

5. Server location issues

A very distant server, a temporary routing problem, or an unstable path can result in timeouts even while the VPN shows “Connected.”

Fixes:

• Pick a nearby server location first.
• If it is still broken, try another nearby location (not across continents).
• Disconnect and reconnect the VPN after switching server.
• If you are on unstable Wi-Fi, test on mobile data once.

Protocol to try first: WireGuard.

6. VPN protocol compatibility

Sometimes a protocol works on one network but fails on another. The VPN tunnel may show “Connected,” but the network may be interfering in ways that prevent normal traffic flow.

Fixes:

• Switch protocol:
  • If you are on WireGuard, try XRay (VLESS/Reality).
  • If you are on XRay (VLESS/Reality), try WireGuard.
• Keep the server location the same while switching protocols (change one variable at a time).
• Reconnect after every change.

Protocol to try first: WireGuard on normal networks; XRay (VLESS/Reality) on restrictive networks.

7. App-specific routing problems

If some apps work but others do not, the VPN connection is not fully “down.” This is usually a routing, DNS, or compatibility issue specific to those apps.

Fixes:

• Clear cache for the affected app (Settings → Apps → Storage → Clear cache).
• Use Split Tunneling:
  • Exclude the problematic app from VPN, or
  • Include only the apps that need VPN.
• If the issue happens only on one Wi-Fi, test another network to isolate the cause.

Protocol to try first: Keep current protocol; use Split Tunneling first.

8. DNS filtering or router issues

Some routers and networks filter DNS or block certain DNS requests. This can break browsing while other traffic partially works.

Fixes:

• Disable Private DNS temporarily (even if you think it is unrelated).
• Restart the router (home Wi-Fi) or reconnect to the network.
• Try a different network (mobile hotspot) to confirm it is router-specific.
• Switch protocol if the network is restrictive.

Protocol to try first: WireGuard, then test XRay (VLESS/Reality) if Wi-Fi appears restrictive.

9. Battery restrictions on Android

On some phones, aggressive battery optimization can pause network activity in the background. This can feel like “VPN connected but apps cannot load” after the phone sleeps.

Fixes:

• Set VPN app battery usage to Unrestricted (wording varies by Android version).
• Disable extreme power saving modes temporarily.
• Reconnect the VPN after changing battery settings.
• Test by locking the screen for 1–2 minutes and retrying a site.

Protocol to try first: WireGuard.

10. Temporary network state bugs

Android networking can sometimes get “stuck,” especially after switching Wi-Fi networks, toggling airplane mode, or moving between mobile data and Wi-Fi.

Fixes:

• Disconnect VPN, then toggle airplane mode on/off.
• Turn Wi-Fi off/on.
• Reboot the phone once (it is often the fastest reset).
• Forget and re-add the Wi-Fi network if the problem is repeatable on that Wi-Fi.

Protocol to try first: Keep current protocol; this is often a device/network state issue.

Protocol switching (WireGuard vs XRay)

Switching protocols can help when the current network is interfering with how a VPN tunnel carries traffic. It is most useful when:

• the VPN connects but traffic does not pass on one specific Wi-Fi network,
• you see frequent disconnects or handshake problems,
• the network seems restrictive or filtered.

Protocol switching is less likely to help when the root cause is:

• wrong device time,
• Private DNS conflicts,
• a captive portal you have not completed,
• a router or DNS filtering problem.

A good workflow is:

1. fix Date & Time,
2. disable Private DNS temporarily,
3. complete captive portal login,
4. then switch protocols if needed.

NimbusVPN gives you both WireGuard and XRay (VLESS/Reality) so you can test without changing apps.

When Split Tunneling helps

Split Tunneling can solve “connected but no internet” cases where only certain apps fail, or where one app is sensitive to VPN routing.

Examples where Split Tunneling is useful:

• A streaming app fails while everything else works
• A banking app shows repeated login prompts
• You only need VPN for one travel-related app

Two simple approaches:

• Include mode: route only one or two apps through the VPN (everything else direct).
• Exclude mode: keep VPN for most apps but bypass one problematic app.

If you are troubleshooting, start small: add or exclude one app, reconnect, test, then adjust.

Android TV note

The same issue can happen on Android TV: the VPN shows “Connected,” but apps do not load. The troubleshooting logic is similar:

• Check Wi-Fi login pages (hotel Wi-Fi captive portals are common on TVs)
• Disable Private DNS temporarily (if available on your device)
• Try switching protocols (WireGuard ↔ XRay (VLESS/Reality))
• Reboot the TV box (often clears stuck network state)

NimbusVPN supports Android TV with a remote-friendly UI, so the same protocol and Split Tunneling logic applies.

FAQ

Why does VPN say connected but nothing loads?

Because the VPN tunnel is up, but traffic inside it is failing—often due to DNS conflicts, captive portal Wi-Fi, restrictive networks, or wrong device time.

Why does VPN work on mobile data but not Wi-Fi?

The Wi-Fi network may be restrictive, require a captive portal login, or have DNS filtering. Try completing the login page, disabling Private DNS, and switching protocols.

Can Private DNS break VPN connections?

Yes. Private DNS can conflict with VPN DNS routing and cause “connected but no internet.” Temporarily turn it off to test.

Should I switch VPN protocol?

If Date & Time and Private DNS are fine, and the issue is network-specific, protocol switching can help. Try WireGuard on normal networks and XRay (VLESS/Reality) on restrictive ones.

Does Split Tunneling fix this issue?

It can, especially when only one app fails. Excluding that app (or including only the apps that need VPN) often resolves compatibility issues.

Can hotel Wi-Fi block VPN?

Yes. Many hotels require a login page first, and some restrict VPN patterns. Complete the captive portal login, then try WireGuard, and switch to XRay (VLESS/Reality) if needed.

Why do some apps work but others do not?

That usually points to app-specific routing, DNS behavior, or the app being sensitive to VPN connections. Split Tunneling is often the best fix.

Does restarting the phone really help?

Yes, more often than people expect. It resets the network stack and clears temporary stuck states, especially after switching networks.

How NimbusVPN fits

NimbusVPN can help you troubleshoot this issue on Android with practical controls:

• Two protocol options: WireGuard and XRay (VLESS/Reality)
• Split Tunneling to route only specific apps through the VPN
• Works on Android TV (remote-friendly)
• Useful for privacy on shared Wi-Fi and travel scenarios (used responsibly)
• Makes it easier to test one change at a time (protocol vs routing)

If you want a VPN app that lets you switch protocols and use Split Tunneling when only one app is the problem, NimbusVPN is a practical option.

Get NimbusVPN on Google Play

Privacy Policy and Terms are available on our website.

Related articles to write next

• Split Tunneling on Android: 6 Practical Presets (2026)
• WireGuard vs XRay (VLESS/Reality) on Android: Which One to Use? (2026)
• VPN for Android TV: Setup Guide (2026)