VPN Not Working? Troubleshooting and When to Change Providers

“VPN not working” can describe five different failures: it will not connect, it connects but there is no internet, it is too slow, it repeatedly disconnects, or only one website or streaming service fails. Identify the symptom before reinstalling anything. First confirm ordinary internet access without the VPN, check the provider's service status and subscription, then test another server and protocol. Next compare one device with another and one network with another.

This four-way isolation—device, network, server, provider—usually shows where the fault lies. A problem on one phone points to the app or operating system. A problem on every device only at a hotel points to the network. A single blocked site points to IP reputation or service policy. Repeated failures across devices, networks, servers, and current apps are a reasonable signal to change providers.

Last verified: 2026-08-05

Identify the symptom in 60 seconds

Symptom	What it means	Next guide
Connection never completes or shows an error	Tunnel is not established	VPN not connecting
VPN says connected but nothing loads	Routing, DNS, kill switch, or network conflict	Continue with Branch 2 below
Internet works but is consistently much slower	Distance, server load, protocol, Wi-Fi, or hardware	VPN too slow
Tunnel connects and later drops	Network changes, sleep, server route, app, or MTU	VPN keeps disconnecting
Only one site or app fails	IP reputation, cookies, DNS, account region, policy	VPN blocked by websites
Netflix shows VPN/proxy detection	Netflix-specific IP and region checks	Netflix detects VPN

Do not run all troubleshooting branches at once. Change one variable, record the result, and restore any temporary security change.

Branch 1: VPN will not connect

Confirm these basics:

internet works with the VPN disconnected;
the subscription is active and login succeeds on the provider website;
automatic date and time are correct;
the provider has no reported outage;
another server connects;
another protocol connects;
the device is not behind an unfinished captive portal.

A firewall, antivirus web shield, school network, workplace filter, hotel network, ISP, or national block can interfere with VPN protocols. Do not permanently turn off the firewall. Briefly testing a documented exception can isolate the cause, after which protection should be restored.

When only one network blocks the VPN, use a provider-supported TCP or obfuscation mode. When no network works on that device, update or reinstall the official app after saving settings and logs.

Branch 2: connected, but no internet access

A connected status means the tunnel handshake completed, not that DNS and routing are healthy. Check in this order:

Disconnect normally and confirm internet returns.
Reconnect to another nearby server.
Open an IP-address page by domain name and by a known app. If domains fail but some apps work, DNS is suspect.
Return custom DNS to automatic and let the VPN manage it.
Check whether the kill switch remains active after a failed connection.
Disable split tunneling temporarily; a bad exclusion can create mixed routes.
Restart the app, then the device, then the router.
Try another protocol.

If the device has IPv6 but the provider does not route it as expected, an app may fail or reveal a mixed location. Use the provider's documented IPv6 setting, not an arbitrary registry or terminal command copied from a forum.

On iPhone, iPad, and Mac, Apple advises checking VPN and third-party security software when network connectivity is affected and comparing another network. On Windows, a network reset is a late step because it can remove adapters and require VPN or virtual-switch reinstallation.^[1]^[2]

Branch 3: VPN is too slow

First establish a fair baseline on the same device and network. A VPN cannot exceed a congested Wi-Fi link or slow ISP line. Compare:

without VPN;
nearest server with the default protocol;
second nearby server;
wired versus Wi-Fi where possible;
native app versus router connection.

Distance increases latency, and busy servers or routes reduce throughput. Multi-hop, Tor, obfuscation, and TCP modes add overhead by design. Turn off optional multi-hop for the speed test, but do not weaken encryption or certificate checks.

If only a router is slow, its processor may be the limit. If every device is slow across nearby servers at multiple times, the provider's network or peering may be a poor fit.

Branch 4: connection keeps dropping

Record when it drops:

immediately after the screen sleeps;
when moving between Wi-Fi and cellular;
at a regular time interval;
only on one server;
during heavy upload or video;
after the router renews the connection.

Battery optimization can suspend a mobile VPN app. Wi-Fi roaming and network changes can invalidate the tunnel. A regular interval suggests session timeout, router/NAT behavior, or a scheduled network event. Enable documented auto-reconnect and verify kill-switch behavior.

Try another nearby server and protocol before changing MTU. MTU tuning is advanced and a wrong value can create partial failures that are harder to diagnose.

Branch 5: one website or service fails

If everything else works, do not reinstall the VPN. Verify that the site works without it, then:

change server within the same country;
force-close the app or use a clean browser profile;
check public IP and DNS;
verify account country and device location;
remove overlapping browser proxies or Private Relay for the test;
contact the VPN provider with the exact service and server.

Banks and payment services may intentionally reject VPN data-center IPs. Streaming services can change their detection without notice. A U.S., U.K., or Australian IP does not prove account eligibility.

Isolate network, device, app, server, and provider

Use this matrix:

Test	Result	Likely area
Same device works on mobile data, fails on Wi-Fi	Network/router/filter	Wi-Fi or ISP path
Other device works on same Wi-Fi	Device/app	Local client or OS
All devices fail on one server	Server	Maintenance or bad route
All servers fail on all devices on one network	Network block	Router, ISP, captive portal, restrictions
All servers fail across two networks and devices	Provider/account	Outage, subscription, widespread incompatibility
Only one app fails	Endpoint/app	IP block, cache, account, split tunnel

This is more informative than repeated reinstalls. Save the server name, protocol, time, network type, app version, OS version, and exact error before contacting support.

Safe checks before reinstalling

Perform these first:

Update the official VPN app.
Check subscription and service status.
Reboot app and device.
Change one server.
Change one protocol.
Test another network.
Test another device.
Restore automatic DNS.
Inspect kill switch and split tunneling.
Export or save logs if the app provides them.

Reinstall only when the app is corrupted, its virtual adapter is missing, an update failed, or provider support recommends it. Uninstalling can erase diagnostics. On managed work devices, contact IT rather than removing a corporate profile.

When reinstalling will not help

Reinstallation does not change:

a website's blocked IP list;
a provider server outage;
an expired subscription;
hotel or national protocol blocking;
router CPU limits;
the distance to a server;
account-region or payment rules;
poor ISP routing;
a provider that lacks your required platform.

Match the remedy to the layer. Reinstalling a Fire TV app will not fix a blocked streaming IP, and resetting Windows will not make a distant server low-latency.^[2:1]

When to change VPN providers

Switch after you establish a repeated, structural mismatch:

no usable protocol works on the networks you regularly use;
required apps or operating systems are no longer supported;
the service has too few suitable server locations;
speed remains inadequate after baseline, server, protocol, and device checks;
disconnects recur across devices and networks;
the sites central to your use reject most of the provider's addresses;
support cannot explain the feature, policy, or incident;
renewal cost no longer matches the service you receive.

Use the best VPN guide to choose by requirement rather than brand. Test the replacement before a long commitment and retain the old service until the critical workflow is verified.

FAQ

Why does my VPN say connected when there is no internet?

The encrypted tunnel may be established while DNS, routes, the kill switch, or upstream server access is failing. Change server, restore automatic DNS, and inspect kill-switch state.

Should I reset network settings immediately?

No. It can erase saved Wi-Fi, VPN, APN, and virtual-adapter settings. Use it only after simpler isolation steps and with a backup of required configurations.

Can antivirus software stop a VPN?

Yes, a firewall or web shield can block the app or protocol. Test only a temporary documented exception and restore protection; do not leave security software disabled.

Why does the VPN fail only at a hotel or school?

The network may require a captive portal, block UDP or common VPN signatures, or permit only selected traffic. Complete the portal and try an official TCP or obfuscation mode.

Does changing DNS fix every connected-without-internet problem?

No. DNS is one possible cause. Random public DNS can create leaks or region mismatches. Return to automatic/provider DNS first.

How do I know the provider is at fault?

The case is strongest when the failure repeats on multiple updated devices, networks, servers, and protocols while ordinary internet works.

Can I keep two VPN apps installed?

Yes, but simultaneous network extensions, always-on modes, kill switches, and browser proxies can conflict. Fully disconnect one before testing the other.