Quick definition and what “not working” usually means
A VPN doesn’t “work” when it fails to connect, stays connected but doesn’t route traffic as expected, or can’t access sites/services that should be reachable. The right response depends on which of those you’re seeing: connection failure, no improvement, or content still not loading.
A simple model: connection, routing, and access
Think of VPN troubleshooting as three layers:
- Connection: the client establishes a secure tunnel to the VPN server.
- Routing: your device’s internet traffic is directed through that tunnel.
- Access: the websites/services you want accept your traffic flow (and the VPN-related signals they see).
If the problem happens at layer 1, focus on connectivity. If layer 2 fails, the tunnel may exist but traffic isn’t being sent through it. If layer 3 fails, the VPN can be “working” while the specific service still blocks or limits that traffic.
Step-by-step checks you can do
1) Confirm it’s actually connected
Open the VPN app and verify the status indicator shows a connected state. If it connects and then immediately drops, treat it like a connection-layer issue.
Also check whether the device is on Wi‑Fi or mobile data and whether it was stable long enough to establish the tunnel. If you switched networks recently, retry after reconnecting to the network.
2) Restart the VPN session
A common first move is to disconnect the VPN, then connect again. If there’s an option to “refresh,” “reconnect,” or “update connection,” use it.
If you’re using a custom setup (manual DNS, custom routes, or special network permissions), temporarily revert to defaults to see whether the issue was caused by a configuration mismatch. If you cannot revert, record the current settings so you can restore them later.
3) Try a different server location
When a specific server is unreachable or restricted, switching to another location can restore the connection or routing. Use the nearest or a commonly reachable region first, because long-distance paths often add latency (and can make timeouts look like “not working”).
4) Adjust the VPN protocol (if your app offers it)
Many VPN clients allow selecting a protocol or connection mode. If one protocol fails to connect or keeps stalling, try another protocol option. Because app naming varies, follow what your client labels as alternatives rather than guessing.
5) Check for local network interference
Some networks behave differently: captive portals (like hotel Wi‑Fi login pages), strict firewall rules, or DNS filtering can prevent stable VPN use. If you can, test on a different network (for example, your mobile hotspot). If it works there, the root cause is likely local to the original network.
6) Verify DNS and general name resolution
If you can’t load websites but the VPN appears connected, DNS resolution may be misaligned. Without changing advanced settings, you can often test by waiting a few moments and reconnecting, or switching DNS-related options to the client’s standard behavior.
Differences and limits: when troubleshooting may not solve it
A VPN can be connected and routing traffic, yet some services may still block access. This can happen if a site detects VPN traffic patterns, if an account has location-based restrictions, or if the service relies on signals the VPN can’t fully change. In those cases, “VPN not working” is really “access not granted,” and changing servers or protocols may help—but it’s not guaranteed.
Also, be careful not to treat symptoms like buffering, slow speeds, or timeouts as proof the VPN is broken. Those can reflect congestion on the chosen server path, high latency, or general internet issues on either your side or the destination side. Your best clue is whether the VPN connects reliably and whether other sites behave consistently.
Practical use: a quick decision checklist
If you want to narrow it down fast, answer these in order:
- Does the VPN reliably show connected or does it drop immediately?
- After connecting, do multiple websites load, or only some?
- Does switching server location improve things?
- Does the problem disappear on a different network?
- If available, does switching protocol change the outcome?