
How this article was prepared
VPNScout reviews official documentation and public security guidance, then checks material claims during editorial updates. We do not describe a product as hands-on tested unless the article includes the test conditions and results.
Most VPN problems can be isolated without reinstalling the app or resetting every network setting. First confirm whether the ordinary internet connection works, then identify whether the failure affects the tunnel, all traffic, one app, one network, or only one VPN server. Change one setting at a time and test after every change.
This guide is a diagnostic hub. Use the quick table to reach the most relevant detailed instructions, or follow the complete sequence when the cause is unclear. Do not remove a work or school VPN profile, disable managed security controls, or change a router you do not own without authorization.
| Symptom | Best next guide | First check |
|---|---|---|
| VPN says Connected but nothing loads | VPN connected but no internet | Disconnect the VPN and test the underlying connection |
| VPN works on Wi-Fi but not cellular | VPN not working on mobile data | Confirm mobile data works with the VPN off |
| VPN repeatedly drops on Android | VPN keeps disconnecting on Android | Check Auto-connect, battery controls, and network changes |
| VPN stops after the screen locks | VPN stops when the screen turns off | Run a timed lock and unlock test |
| Public IP does not change | VPN connected but IP not changing | Compare the exact IP before and after connecting |
| Google still shows the old location | Google still shows my location | Review device location, cookies, account history, and IP geolocation |
| Browser works but other apps fail | VPN works in browser but not apps | Check whether you are using only a browser extension |
| VPN fails on hotel Wi-Fi | VPN not working on hotel Wi-Fi | Complete the hotel's verified captive portal |
| VPN is unexpectedly slow | VPN Speed Loss Calculator | Compare repeatable tests on the same server and network |
| You are unsure whether the tunnel works | How to check if your VPN is working | Compare IP, IPv6, DNS, and reconnection behavior |
Write down the device, operating-system version, VPN app version, server location, protocol, network type, and exact error. Note whether the problem began after an update, network change, sleep cycle, or configuration change. A reproducible symptom is more useful than a long list of random fixes.
Do not publish your full IP address, account details, configuration keys, or raw diagnostic logs. Share sensitive logs only through the provider's official support channel.
Temporarily disconnect the VPN and open two trusted websites. If neither works, troubleshoot Wi-Fi, mobile data, the router, or the internet provider first. If ordinary access immediately returns, continue with VPN-specific checks. On unfamiliar public Wi-Fi, remain disconnected only as long as needed to complete the test.
One server or route may be unavailable, congested, or blocked by the current network. Try the provider's recommended connection and one nearby alternative. If one server fails while another works, record the failed location and report it rather than changing unrelated device settings.
Use the VPN IP Change Checker before and after connecting. A different public IP is a useful first signal that browser traffic is using another exit point. It does not prove that every app, DNS request, IPv6 connection, or split-tunneled service follows the same route.
Start with the VPN app's Automatic or recommended protocol. If the connection still fails, test another maintained protocol offered by the provider. Network firewalls, routers, carriers, and captive portals can handle protocols differently. Avoid obsolete protocols and configuration files from unofficial websites.
Custom DNS, ad blocking, threat filtering, antivirus web inspection, parental controls, and another local VPN-style app can interfere with name resolution or routing. Return the VPN DNS setting to Automatic and pause optional filtering only long enough to identify a conflict. Restore useful security controls after the test.
A kill switch is designed to stop ordinary internet traffic when the VPN tunnel fails. Android can also offer Always-on VPN and Block connections without VPN. If the VPN drops and internet access stops, the protection may be working as designed. Disable blocking only briefly for diagnosis, then restore it if preventing leaks is part of your setup.
Compare home Wi-Fi, mobile data, and another trusted network. If the VPN fails only on one network, focus on that network's portal, DNS, firewall, router, carrier, or access policy. If it fails everywhere, focus on the app, profile, account, device, or provider service.
Install stable operating-system and VPN-app updates from verified sources. Fully close the app, restart the device, and test default settings. Reinstall only if the problem survives those lower-impact steps. Save any account details and custom configuration first.
A network reset may remove saved Wi-Fi networks, VPN profiles, cellular settings, Bluetooth pairings, or custom DNS. It is not a good first fix. Review the device manufacturer's current documentation and record anything you will need to restore.
Check account status, system date and time, the underlying connection, and whether the current network requires a browser login. Then try a recommended server and supported protocol. A workplace, school, hotel, or country may restrict VPN traffic, so follow applicable network rules and local law.
The likely areas are DNS, the selected server, the protocol, a kill switch, a captive portal, or another security tool. Follow the dedicated no-internet troubleshooting sequence rather than repeatedly reinstalling.
The service may block a shared VPN address, require the original region, remember an account location, or conflict with filtering. Test another server, temporarily return split tunneling and DNS to defaults, and check the service's terms. A VPN does not create a right to access content or bypass an organization's controls.
Run several tests under comparable conditions. Use the same device, nearby test endpoint, activity, and time window. Compare medians rather than the best single result with the VPN Speed Loss Calculator. Server distance, congestion, protocol, Wi-Fi quality, mobile signal, router processing, and the test service can all affect the result.
Moving from Wi-Fi to cellular changes the network interface and often the public IP. Review Auto-connect, battery controls, Data Saver, and supported mobile protocols. Test Wi-Fi only, mobile data only, and a controlled handoff to identify the trigger.
Google documents Android VPN controls under Settings, Network and internet, VPN, although manufacturer menus vary. Review the selected VPN app, Always-on VPN, Block connections without VPN, battery usage, background data, Data Saver, and manufacturer sleeping-app lists. Do not remove an administrator-managed work profile.
Review the provider's Auto-connect setting and recognized entries under Settings, General, VPN & Device Management. Test Low Power Mode only as a diagnostic variable, update iOS and the official app, and remove a VPN profile only when you know who installed it and how to restore it.
Quit other VPN clients, proxies, and network filters that may compete for routes. Test the official app with default DNS and protocol settings. On managed computers, contact the administrator before changing certificates, profiles, firewalls, or security extensions.
Consider another provider only after confirming that the underlying connection works and the same provider repeatedly fails across multiple servers, protocols, and networks. Compare current app support, protocol choices, kill-switch behavior, documentation, independent assessments, and support quality. Our VPN comparison page explains the tradeoffs and why NordVPN is our current best overall recommendation.
This hub organizes our detailed troubleshooting articles into a least-disruptive diagnostic sequence. It uses operating-system documentation, provider support material, and observable checks such as connection state, public IP, network isolation, and repeatable speed measurements. We do not claim that one sequence covers every device, carrier, employer configuration, or VPN implementation.
Disconnect it briefly and confirm whether the ordinary internet connection works. Then reconnect to a recommended nearby server before changing advanced settings.
No. First test the network, another server, the recommended protocol, DNS defaults, and a restart. Reinstallation can remove useful evidence and custom settings.
A kill switch or operating-system blocking mode may be preventing traffic from falling back to the ordinary connection. Reconnect the VPN and review that protection setting.
No. A VPN depends on an existing internet connection. It cannot repair a carrier outage, weak Wi-Fi, broken router, expired account, or service-wide failure.
Repeat the original failure sequence, confirm the VPN remains connected, compare the public IP, load several trusted sites, and retest after sleep or a network change when relevant.
Troubleshoot from the outside in: verify the underlying internet connection, isolate the affected network or app, test another server, confirm the IP, try a maintained protocol, review DNS and blocking controls, then update and restart. Reinstall or reset the network only after safer targeted checks fail.