DNS Leak Checker
Running live test…

VPN Connected But No Internet – How to Fix It

One of the most frustrating VPN problems is connecting successfully to a VPN server only to find that your internet stops working entirely. Your VPN client shows as connected, the status indicator is green, but every website times out and no data loads. This problem affects users of every major VPN provider on every operating system and is almost always fixable without reinstalling your VPN. Use the status check below to confirm your current connection state, then follow the step-by-step diagnosis guide below.

Not sure if your DNS is leaking? Find out in seconds.

Run a Free DNS Leak Test Now

Why Does a VPN Connect But Break Internet Access?

When your VPN connects successfully but kills your internet access, it almost always means that your traffic is being routed through the VPN tunnel but something is preventing it from reaching the destination. The VPN handshake — the initial connection between your device and the VPN server — completed successfully, which is why the app shows as connected. But the actual data flow after that handshake is being blocked somewhere between your device and the wider internet.

The most common cause is a DNS conflict. When you connect to a VPN, the VPN client takes over your DNS settings to route all DNS queries through its own servers. If this transition fails or creates a conflict with your existing DNS configuration, your device cannot resolve domain names — meaning it knows you want to visit google.com but cannot look up the IP address to connect to. The result is a connected VPN with no functioning internet.

The second most common cause is a routing table conflict. Your operating system maintains a routing table that tells it which network interface to use for different types of traffic. When a VPN connects, it adds new routes to this table directing all traffic through the VPN tunnel. If those routes conflict with existing entries — particularly on networks with unusual configurations like corporate networks or hotel Wi-Fi — the result is a routing loop that prevents any data from getting through.

A third common cause is the VPN's kill switch being triggered incorrectly. A kill switch is a safety feature that blocks all internet traffic if the VPN connection drops, to prevent your real IP from being exposed during reconnection. However, some kill switch implementations are overly aggressive and block traffic even when the VPN is technically connected, particularly during the brief window when the VPN is establishing the data tunnel after the initial handshake.

Network-level causes include ISPs that actively throttle or block VPN traffic, firewall rules on corporate or institutional networks that prevent VPN data from passing through, and incompatibilities between your VPN protocol and the specific network you are connected to. VPN protocols like OpenVPN on port 1194 are commonly blocked on restricted networks — switching to a different protocol such as WireGuard or setting OpenVPN to run on port 443 (the standard HTTPS port) often resolves these situations.

Device-level causes include corrupted VPN driver files, outdated network adapter drivers on Windows, conflicting network software such as other VPN clients running simultaneously, antivirus or firewall software that intercepts VPN traffic, and IPv6 configuration issues where the VPN handles IPv4 correctly but leaves IPv6 traffic in a broken state. Understanding which category your problem falls into is the first step to fixing it — the diagnostic steps below cover all of these scenarios systematically.

VPN Connected But No Internet – Step by Step Fix

  1. 1

    Disconnect and Reconnect the VPN

    The simplest fix is often the most effective. Disconnect from the VPN completely, wait 10 seconds, then reconnect to the same server. This forces the VPN client to re-establish the tunnel and re-apply all network settings from scratch, which resolves temporary routing conflicts and DNS transition failures in most cases.

  2. 2

    Try a Different VPN Server

    If reconnecting to the same server does not work, try connecting to a different server in the same country or a completely different region. Individual VPN servers can experience congestion or configuration issues that cause connectivity problems. A different server often resolves the issue immediately, confirming that the problem is server-side rather than on your device.

  3. 3

    Disable the VPN Kill Switch Temporarily

    If your VPN has a kill switch enabled, temporarily disable it and try connecting again. A misconfigured kill switch can block traffic even when the VPN is connected, particularly on VPN clients with an "always-on" or "permanent" kill switch mode. Once you confirm connectivity is restored with the kill switch off, re-enable it and test again — if the problem returns, the kill switch implementation in your current VPN client may need an update.

  4. 4

    Flush Your DNS Cache

    Open your command prompt or terminal and flush the DNS cache. On Windows, run: ipconfig /flushdns. On Mac, run: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. This clears any stale or corrupted DNS entries that may be preventing domain name resolution after the VPN takes over your DNS settings.

  5. 5

    Change the VPN Protocol

    In your VPN client settings, switch to a different protocol. If you are using OpenVPN UDP, try OpenVPN TCP. If you are using WireGuard, try IKEv2 or OpenVPN. Protocol incompatibilities with specific networks are a common cause of "connected but no internet" issues, particularly on restricted networks like hotel Wi-Fi, corporate networks, or mobile data connections.

  6. 6

    Disable IPv6 on Your Device

    VPN connectivity issues are frequently caused by IPv6 conflicts where the VPN handles IPv4 correctly but does not route IPv6 traffic properly. On Windows, go to Network Adapter settings and uncheck the IPv6 protocol for your active adapter. On Mac, go to System Preferences → Network → Advanced → TCP/IP → Configure IPv6 and set it to Off. Test the VPN connection after making this change.

  7. 7

    Check for Conflicting Network Software

    Other VPN clients, proxy software, or network security tools running simultaneously can conflict with your VPN's routing. Check your system for other VPN clients and disable or uninstall them before connecting. Corporate endpoint security software and some antivirus programs also intercept network traffic in ways that conflict with VPN routing tables.

  8. 8

    Reset Your Network Stack

    On Windows, open Command Prompt as Administrator and run: netsh winsock reset, then netsh int ip reset, then restart your computer. This resets the core Windows networking components to their default state and resolves many persistent routing table conflicts that survive individual VPN reconnections. On Mac, go to System Preferences → Network and delete and re-add your network connection.

  9. 9

    Try a Different Network

    Connect to a completely different network — switch from Wi-Fi to mobile hotspot, or from your home network to a different Wi-Fi network. This determines whether the problem is specific to your current network configuration or whether it follows the device. If the VPN works on a different network, the issue is related to your primary network's firewall, routing, or ISP settings.

  10. 10

    Reinstall the VPN Client

    Corrupted VPN client files, outdated drivers, or misconfigured installation settings can cause persistent connectivity failures. Completely uninstall your VPN client, restart your device, then download the latest version from the official website and reinstall. This resolves issues caused by partial updates or installation corruption that individual settings changes cannot fix.

  11. 11

    Check for ISP VPN Blocking

    Some ISPs — particularly in certain countries or on specific network types — actively block VPN traffic at the provider level. If none of the above steps have resolved the issue, contact your ISP and ask whether VPN traffic is restricted on your connection. In these cases, the only solution is to use a VPN protocol that disguises VPN traffic as regular HTTPS — a feature called obfuscation that is available on NordVPN (Obfuscated Servers), ExpressVPN (Lightway), and a few others.

  12. 12

    Check Your VPN DNS Leak Test Results

    Even if you restore internet connectivity, run a DNS leak test to confirm that your VPN is correctly handling DNS after the reconnection. A "connected but no internet" issue that was resolved by a reconnection sometimes leaves DNS in a partially broken state where some domains resolve and others do not. Use the free DNS leak test on our homepage to verify.

After fixing your connectivity, run a DNS leak test to make sure your VPN is routing all traffic correctly

Run DNS Leak Test

VPN Connected But No Internet – By Device

Windows

The most common Windows-specific cause is the TAP adapter driver that OpenVPN-based clients use. If this driver becomes corrupted or conflicts with a Windows update, the VPN can connect but fail to pass traffic. Reinstalling the TAP driver or switching to WireGuard (which uses a different driver model) resolves this in most cases. Windows Defender Firewall sometimes blocks VPN traffic after updates — check firewall rules if other fixes have not worked.

Mac

On macOS, network extension permissions are a common issue. After a macOS update, VPN clients that use network extensions may lose their system approval and need to be re-approved in System Preferences → Privacy & Security → Network Extensions. Apple Silicon Macs (M1/M2/M3) have occasionally had compatibility issues with VPN clients designed for Intel Macs — ensure your VPN client is updated to a native Apple Silicon build.

Mobile (iOS and Android)

On mobile, the most common cause is the device's battery optimisation settings aggressively killing the VPN app in the background. On Android, go to battery settings and disable optimisation for your VPN app. On iOS, ensure the VPN profile is correctly installed in Settings → General → VPN & Device Management. Mobile VPN connections are also more susceptible to protocol issues when switching between Wi-Fi and mobile data.

Router-Level VPN

If the VPN is configured at the router level rather than on individual devices, connectivity issues affect all devices on the network simultaneously. Check your router's VPN client settings and verify the server credentials are current — many VPN providers rotate server addresses periodically. A simple router restart often resolves temporary routing table issues without requiring any configuration changes.

A DNS leak does not directly cause a loss of internet connectivity, but the underlying DNS misconfiguration that causes the leak can also cause browsing failures. When a VPN takes over your DNS settings and the transition fails partially, some DNS queries may resolve correctly while others fail entirely, resulting in intermittent connectivity where some websites load and others do not. After resolving a VPN connectivity issue, always run a DNS leak test to verify that your DNS is routing correctly through the VPN tunnel. A partially working DNS configuration can make it appear that the internet is functional while silently exposing your browsing activity to your ISP.

Not sure if your DNS is leaking? Find out in seconds.

Run a Free DNS Leak Test Now

Related Guides

VPN Not Working?Diagnose why your VPN isn't protecting youVPN Fix: WindowsFix VPN issues on Windows 10/11VPN Fix: MacResolve macOS VPN connection problemsVPN Fix: iPhoneFix VPN on iOS step-by-stepVPN Fix: AndroidSolve Android VPN issuesVPN Leak TestTest DNS, IP, and WebRTC leaks in one goDNS Leak CheckerTest your DNS, IP & WebRTC privacy

Frequently asked questions

Why does my VPN show as connected but internet doesn't work?

When your VPN client shows a green connected status but websites do not load, the VPN handshake with the server has completed successfully but data is not flowing through the tunnel. The most common causes are DNS resolver conflicts where your device cannot look up domain names through the VPN's DNS servers, routing table errors where traffic is directed to a dead end instead of through the tunnel, or the VPN's kill switch blocking traffic during a brief reconnection window. Start by disconnecting and reconnecting the VPN to force a clean re-establishment of all network settings, then work through the step-by-step guide above if the issue persists.

Does disabling the kill switch fix the no internet problem?

Temporarily disabling the kill switch is one of the most effective diagnostic steps because it determines whether the kill switch itself is causing the blockage. A kill switch works by creating firewall rules that block all non-VPN traffic — if these rules are applied incorrectly or persist from a previous session, they block all internet access even when the VPN is connected. If disabling the kill switch restores connectivity, the issue is specifically with how the kill switch interacts with your network configuration. Re-enable the kill switch after testing and update your VPN client to the latest version, which may include fixes for kill switch behaviour.

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

Mobile data networks often use different network configurations than Wi-Fi, including carrier-level NAT, different MTU sizes, and sometimes active protocol filtering that blocks VPN traffic. Some mobile carriers block specific VPN protocols like OpenVPN on port 1194 but allow WireGuard or IKEv2. Try switching your VPN protocol in the app settings — WireGuard typically has the best compatibility with mobile data networks. Additionally, check your phone's battery optimisation settings as aggressive power saving can kill the VPN connection in the background on Android devices.

Can my ISP block my VPN and cause no internet?

Yes — some ISPs actively block or throttle VPN traffic, particularly in countries with internet censorship or on specific network types like university and corporate connections. When an ISP blocks VPN traffic, the VPN client may still show as connected because the initial handshake succeeds, but subsequent data cannot pass through the ISP's filters. The solution is to use VPN obfuscation, which disguises VPN traffic as regular HTTPS traffic. NordVPN offers obfuscated servers, ExpressVPN uses its Lightway protocol for this purpose, and most premium VPNs have a stealth or camouflage mode designed to bypass ISP-level blocking.

Why does my internet work fine after disconnecting the VPN?

If your internet works immediately after disconnecting the VPN, the VPN tunnel itself is the problem rather than your underlying network connection. This confirms that your ISP connection is functional and that the issue lies in how the VPN is routing, encrypting, or handling DNS for your traffic. The most likely causes are a congested or misconfigured VPN server, a protocol incompatibility with your current network, or stale routing rules from a previous VPN session. Try connecting to a different VPN server or switching protocols before investigating further.

What VPN protocol is least likely to cause connectivity issues?

WireGuard is the most reliable VPN protocol for maintaining connectivity across different network types. It uses fewer lines of code than OpenVPN, establishes connections faster, and handles network switching — such as moving between Wi-Fi and mobile data — more gracefully. NordVPN's implementation of WireGuard, called NordLynx, adds a double NAT system for additional privacy. IKEv2 is also highly reliable, particularly on mobile devices where it handles network changes well. OpenVPN on port 443 (TCP) is the best choice when other protocols are blocked because it mimics regular HTTPS traffic.

Why does my VPN only break internet on one specific network?

Network-specific VPN failures are almost always caused by the network's firewall configuration, router settings, or ISP-level traffic management. Corporate and institutional networks frequently block VPN protocols on specific ports, hotel Wi-Fi networks may have captive portals that interfere with VPN tunnel establishment, and some home routers have built-in security features that conflict with VPN routing. The diagnostic approach is to try a different VPN protocol on the problem network — if WireGuard fails, try OpenVPN TCP on port 443. If all protocols fail on one network but work elsewhere, the network is actively blocking VPN traffic.

Does a DNS leak affect whether my internet works through a VPN?

A DNS leak does not directly cause a loss of internet connectivity, but the underlying DNS misconfiguration that causes the leak can also cause browsing failures. When a VPN takes over your DNS settings and the transition fails partially, some DNS queries may resolve correctly while others fail entirely, resulting in intermittent connectivity where some websites load and others do not. After resolving a VPN connectivity issue, always run a DNS leak test to verify that your DNS is routing correctly through the VPN tunnel. A partially working DNS configuration can make it appear that the internet is functional while silently exposing your browsing activity to your ISP.

Stop leaks for good

A VPN with private DNS on every server, a kill switch and WebRTC protection closes every leak this site tests for.

Get NordVPN →

30-day money-back guarantee · We may earn a commission