What “VPN not working” usually means
When a VPN doesn’t work after you “connect to the Internet,” it often means the VPN tunnel is not actually carrying your traffic, or something prevents the tunnel from routing requests correctly. The VPN client may show “connected,” yet websites can still fail to load, or some apps work while others don’t.
A simple model: tunnel, routing, and name resolution
Think of VPN connectivity as three parts:
- The tunnel: the secure connection that should carry traffic.
- Routing: how your device decides where VPN-protected traffic goes.
- Name resolution (DNS): how your device turns domain names into IP addresses.
VPN problems usually happen when one of these parts doesn’t complete or becomes inconsistent with your network. Because there are many device and ISP variations, you should treat results as diagnostic signals rather than proof of a single cause.
Common causes when you can’t browse
1) VPN connects, but traffic isn’t routed
Sometimes the tunnel is up, but traffic still follows your normal (non-VPN) path, or the device can’t apply the VPN routes. This can present as: most browsing fails, while occasional connections may work.
2) DNS is pointing somewhere unreachable
If DNS queries are sent outside the tunnel or resolve to addresses your network can’t reach, you may see “site can’t be reached,” timeouts, or only certain domains failing. This is especially common when networks use custom DNS, ad-blocking DNS services, or strict local DNS settings.
3) Local network settings conflict
Conflicts can include a previously configured proxy, a “VPN allowed/disallowed” policy in the OS, captive portal limitations on Wi‑Fi, or restrictive firewall rules. Even if you only changed your VPN, these factors can still block the tunnel or the resulting traffic.
4) Wi‑Fi/captive portal or unstable networks
Some public networks require a web login before traffic is allowed. In those cases, the VPN may not be able to establish properly, or it may connect but not reach required endpoints.
5) App-level differences
Browsers, system services, and apps can handle network settings differently. If only one browser fails, it points more toward DNS/proxy/browser settings than a full VPN failure. If everything fails, it points more toward tunnel/routing.
Differences and limits to consider
A key exception is that “connected” in the app doesn’t always guarantee usable browsing. Also, if you can browse on one device but not another on the same network, the issue is likely device-specific (settings, DNS, firewall, OS network rules).
If you recently changed anything—new Wi‑Fi, new router, new DNS, updated OS, or installed security software—the failure may be caused by that change rather than the VPN itself. Without specific logs or error messages, it’s not possible to state which exact cause applies; the goal is to narrow down the layer that breaks.
Practical checks you can do now
- Verify the VPN client state: confirm it says connected and that you don’t see repeated connect/disconnect cycles.
- Test multiple targets: try a few websites and also an IP address (if you know one). If IP works but domains don’t, DNS is likely.
- Restart network components: disconnect the VPN, toggle Wi‑Fi/mobile data off and on, then reconnect.
- Look for proxy settings: check whether your OS/browser has a manual proxy configured and temporarily disable it for testing.
- Test on another network: if possible, switch to a different Wi‑Fi or mobile data. If the VPN works elsewhere, the local network restrictions are a prime suspect.
- Check firewall/security tools: temporarily reviewing whether security software is blocking VPN-related connections can identify a conflict.
If you still can’t determine the reason, the most useful next step is to note the exact symptoms (for example, DNS errors vs. timeouts vs. “no internet”), and whether they occur on multiple networks and devices.