VPN connects, but the internet stops working

A VPN can show connected while traffic still goes nowhere. The tunnel may be alive, but DNS may be failing, the server may not route traffic, the kill switch may be blocking everything, Windows may be using an old proxy, or the current network may block that VPN protocol.

Do not buy another VPN plan or delete the profile yet. Use one browser tab and one harmless site you can reload, such as a search engine home page or news site. Avoid banking, work admin panels, streaming apps, and anything that may block VPNs for its own reasons.

Before changing settings, note the VPN app name, server location, protocol if shown, whether the kill switch is on, and whether the internet works immediately after disconnecting the VPN. Those details matter more than the VPN brand name.

On Windows, press Win + X, open Terminal or PowerShell, and run:

ping 1.1.1.1
nslookup example.com

Read the result before changing anything:

• If ping 1.1.1.1 works but nslookup example.com fails, the tunnel probably has a DNS problem.
• If both fail while the VPN is connected, the VPN route, server, protocol, firewall, or kill switch is the first suspect.
• If both work but websites still do not load, check browser proxy, security software, browser extensions, or an app-specific VPN rule.
• If the tests work on one VPN server but not another, stop changing Windows and treat it as a server/provider/protocol issue.

Change one thing at a time:

1. Pick a nearby server from the same provider and retest.
2. If the app offers WireGuard, OpenVPN, IKEv2, or Automatic, switch to one different protocol and retest.
3. Go to Settings -> Network & internet -> Proxy and turn off manual proxy for one test if it is enabled and you do not intentionally use it.
4. If the VPN has a kill switch, pause it only for a short controlled test, reload one harmless site, then turn it back on.
5. Use split tunneling only for a low-risk browser test if the app supports it. Do not split work apps, torrent clients, password managers, or anything sensitive just to make a page load.

If a nearby server works, keep it and report the failed server if it keeps happening. If one protocol works, use it for now and check provider guidance later. If only DNS fails, try the VPN app’s automatic DNS option or a provider-supported DNS setting before changing router-wide DNS. If the kill switch is the only thing blocking traffic, do not leave it off permanently; ask whether the app has a stuck firewall or network-adapter rule.

If you ask for help, send the VPN status screen with server and protocol, whether the kill switch is on, the two command results, Windows Proxy settings if manual proxy is enabled, and whether the same VPN works on mobile data or another Wi-Fi network. Hide account pages, subscription screens, payment details, private keys, recovery codes, and private IP details.

Stop here if the VPN is required by work or school, the VPN is being used to bypass a platform rule or region lock, you are on a captive-portal network, or the VPN is configured on the router. In those cases, do not bypass policy or change router firmware, DNS, or firewall rules from a single-device test.

Related Price2Click guides: use the plain-English VPN explainer if you need the basic model first, start with VPN protocol choices if the tunnel connects inconsistently, use VPN speed testing if pages load but feel slow, and compare providers only after the connection path itself is clean with our VPN comparison guide.