VPN Connected but No Internet? How to Fix It

You open the VPN app, it says connected, and then nothing loads. Pages spin, apps show an offline message and messages will not send. This is one of the most confusing VPN problems because the app seems to be doing its job while the internet has stopped.

The reason is that "connected" only describes the link between your device and the VPN service. Your pages still need name lookups, correctly sized packets and a network that lets the traffic through. This guide works through the usual causes in the order that finds them fastest. If the app will not connect at all, start with the guide on a VPN that is not connecting instead.

What "connected" does and does not mean

When the VPN connects, your device builds an encrypted tunnel to the VPN service and sends your traffic through it. The status light only confirms that the tunnel exists. It does not confirm that everything inside it works.

Four things must all work for a page to load:

1. A route. Your device must send traffic into the tunnel and the service must forward it onwards.
2. A name lookup. Your device turns a site name into an address using DNS. If this fails, the site looks unreachable even though the connection is fine.
3. Packets that fit. Each packet must be small enough to cross every link without being dropped.
4. A matching address family. Traffic can travel over IPv4, IPv6 or both. If a site is reached by an address type the tunnel does not carry, the page can hang.

The sections below test each of these in turn. Keep a note of what changes after every step, because that tells you where the fault sits.

Step 1: Rule out the basics

Spend two minutes on the simple causes first.

• Check your pass. Open My Pass and confirm it has not expired. An ended pass can leave an app looking half connected. Renewing from My Pass adds new days on top of any that remain.
• Turn the VPN off and test. If the internet also fails without the VPN, the problem is your Wi-Fi or mobile data, not the VPN. Restart the router or move to another network.
• Look for a login page. Hotel, airport, cafe and school networks often show a sign-in page before they pass traffic. Open a plain page such as a site that uses http, accept the terms, then connect the VPN again.
• Check the clock. A device clock that is far off breaks secure connections. Set date and time to automatic.
• Disconnect and reconnect. Close the app fully, then connect again. A tunnel can go stale after the device sleeps or switches between Wi-Fi and mobile data.

If the basics did not help, move to the network checks.

Step 2: Separate DNS from everything else

DNS is the most common cause of "connected but no internet". It is the system that turns a name like example.com into a numeric address. The guide to how DNS works explains it in detail; for troubleshooting, one idea is enough: if your device cannot ask a working DNS server, every name fails.

A quick test that needs no special tools:

1. With the VPN connected, open a command window on a computer. On Windows use Command Prompt, on macOS use Terminal.
2. Run a ping to a public numeric address, for example ping 8.8.8.8.
3. Run a ping to a name, for example ping example.com.

Read the result:

Numeric address	Name	Likely meaning
Replies	Replies	Network and DNS both work; look at MTU or the app itself
Replies	Fails	DNS problem
Fails	Fails	The tunnel is not carrying traffic; check the network, permissions and pass

Some networks block ping, so a failed ping alone is not proof. Treat it as a clue and compare it with what the browser does.

If DNS is the problem, try these in order:

• Disconnect and reconnect so the app asks for fresh DNS settings.
• Flush the local DNS cache. On Windows, run ipconfig /flushdns. On macOS, the command depends on the version, so search for the current one for your release.
• On Android, check the Private DNS setting, covered in the Android section below.
• Check that no other app or router setting forces a custom DNS server that the tunnel cannot reach.

A related concern is a DNS leak, where lookups bypass the tunnel. That is a privacy question rather than an outage, and the guide on DNS leaks covers it.

Step 3: Test for an MTU problem

MTU stands for maximum transmission unit, the largest packet a link carries without splitting it. A typical home connection carries packets of about 1,500 bytes. A VPN wraps each packet in extra data, so the room left for your actual content shrinks. If a packet is too big for the path and the network does not tell your device, it is silently dropped. The classic RFC on path MTU discovery describes how this is meant to be handled, and why filtered messages cause trouble.

The telltale signs are distinctive:

• Small pages and chat messages load, while large pages, uploads or video stall.
• A site opens its first screen and then hangs.
• Some sites work perfectly and others never finish loading.
• Sign-in works but loading the next page freezes.

You can probe this from a computer. Pick a payload size and tell ping not to fragment.

• Windows: ping example.com -f -l 1400
• macOS: ping -D -s 1400 example.com
• Linux: ping -M do -s 1400 example.com

If 1400 works, try a larger value; if it fails with a message about fragmentation, try a smaller one such as 1300. Add 28 to the payload for the packet size on the wire. Finding the largest size that works tells you the path limit.

What can you do about it? Check whether your VPN app has a setting for packet size or MTU. Not every app shows one, and you should leave other settings at their default unless support suggests otherwise. Changing the MTU of a network adapter by hand is an advanced step that can affect your other connections, so if the app has no such option, write to support with your test results instead of editing system settings. Switching to another network can also help, because the limit depends on the path.

Step 4: Check IPv6

The internet is moving from IPv4 addresses to the longer IPv6 addresses described in RFC 8200. Many networks give devices both. If your network offers IPv6 but the tunnel only handles IPv4, a site that prefers IPv6 may hang while your device waits, or the traffic may leave outside the tunnel.

How to test it:

1. Note which sites fail and which work. Some sites are IPv4 only, so they work, while IPv6-ready sites fail.
2. As a short test, turn IPv6 off for your network adapter or on your router, then reconnect the VPN and try again.
3. If sites return, IPv6 handling is the cause. Turn IPv6 back on after the test and tell support what you found.

Do not leave IPv6 off permanently as a fix without understanding the effect. It is a diagnostic, not a recommended setting. On phones you usually cannot switch it off per app, so switching networks is the practical test there.

Step 5: Android-specific checks

Android has a few settings that cause exactly this symptom. Menu names vary by version and maker, so use these as search terms in Settings.

• Private DNS. If it is set to a specific provider hostname, lookups may fail when the tunnel is up. Try the automatic setting, then reconnect.
• Data Saver or battery saver. These can restrict background data for the VPN app. Allow the app to use data freely and exclude it from battery optimisation.
• Always-on VPN and blocking connections without VPN. If this is on and the tunnel is not carrying traffic, Android blocks everything. Turn it off to test.
• Wi-Fi assistant or adaptive connectivity. Features that switch networks on their own can interrupt the tunnel.
• Hotspot or tethering. If you share the connection, other devices may not be routed through the VPN the way your phone is.

Android's own page on connecting to a VPN shows where these settings live. The Android troubleshooting guide adds more detail.

Step 6: Other apps and security software

Other software can interfere with traffic inside the tunnel.

• Another VPN, proxy or security app. Two apps cannot both own the tunnel. Close every other VPN and turn off any manual proxy setting.
• Firewall or antivirus web protection. Some security suites inspect or block traffic from new network adapters. Try pausing the web-protection feature briefly to test, then switch it back on.
• Ad blockers and custom DNS apps. Tools that filter by DNS can fail when the VPN changes the DNS route.
• Router parental controls. A filter at the router can block names or ports even though the VPN looks fine.

If turning one of these off fixes the problem, add an exception rather than leaving protection disabled.

A worked example

Mei is at an airport on her laptop. The VPN says connected, but every page shows an error.

1. She turns the VPN off: the airport page appears asking her to accept terms. She accepts, and the plain internet works.
2. She reconnects the VPN: the status says connected, but pages still fail.
3. She runs ping 8.8.8.8, which replies, and ping example.com, which fails. That points to DNS.
4. She disconnects, reconnects and runs ipconfig /flushdns. Names resolve and the pages load.

If the ping to the name had worked but big pages hung, she would have tried the MTU test next. The order matters: it moves from the cheapest check to the most technical.

Limits and when to contact support

Some networks restrict VPN traffic, and no guide can promise a working connection on every network. Public networks in particular can filter or throttle what passes through. If one network fails and another works, that is useful information, not a fault in your device.

Write to xpassvpn@gmail.com if your pass is active, a restart and a second network did not help, and you have the results of the ping tests. Include your device, operating system, the network type and what each test showed. Never include your password. To check that the tunnel is actually doing its job once it works, use the guide on checking that your VPN is working.

Summary

A VPN that shows connected but loads nothing usually has a problem inside the tunnel, not with the tunnel itself. Rule out the basics, then test DNS, then packet size (MTU), then IPv6, then device settings and other software. Change one thing at a time and write down what happens. For more ways to keep the connection steady, see the guide on improving connection stability, and visit the help center if you need a guide for your device.