VPN is connected, but the internet does not work — what to do
If the VPN shows the status “Connected” but there is no internet, one of four layers is almost always to blame: DNS, traffic routing inside the client, a blocked VPN server IP address, or the client itself is stuck halfway through the handshake. Start checking with the simplest things: DNS and pinging the server.
The situation is more confusing than it seems: the “Connected” status in the interface only means that the tunnel has been brought up. Whether packets will go through it, whether DNS will resolve, and whether the provider will cut off the server IP are separate questions.
Below is a short symptom map and a quick checklist. If you first want to make sure the problem is with the VPN and not with a specific site, run a check through Freedom Checker.
Short answer
- The “Connected” status does not mean “the internet works” — it is only the tunnel status.
- The most common cause is the client DNS or a server IP blocked by your operator.
- Check whether the server can be pinged, whether the site opens by IP, and whether behavior changes when you switch protocols.
- Changing the server or protocol (WireGuard → VLESS, OpenVPN UDP → TCP) helps in most cases.
- If it stopped working for everyone on the same day, it looks like blocking, not a client failure.
Why the VPN connected but there is no internet: main causes
In the “tunnel is up, but traffic is not moving” scenario, four separate mechanisms are involved. It is useful to tell them apart because they are fixed in different ways.
1. DNS does not resolve
This is the most common cause. The tunnel exists, but the client did not replace the system DNS, or replaced it with a server that is itself unreachable. On Windows and Android, this often looks like “loading forever,” while a direct ping by IP works.
Solution: in the client settings, enable “use VPN DNS” or set public DNS servers manually (for example, 1.1.1.1 and 8.8.8.8 — if they are available over the specific protocol). For some Russian operators, 1.1.1.1 is unstable, so the VPN service’s own DNS is better.
2. The server IP is blocked by your operator
The server may be “alive” globally, but a specific mobile or home provider has already added it to a filter. This produces the classic picture: the handshake completed, keys were exchanged, but after that there is zero traffic. On the client side this looks like “Connected”; on the server side, the session often does not even open.
The fix is to change the server in the same country or change the country. If you have several VPN apps, checking another one in parallel is faster than trying locations one by one.
3. Routing conflict and split tunneling
If split tunneling is enabled in the client (sending only part of the traffic through the VPN), the apps you need may be excluded from the tunnel and try to connect directly. Corporate TLS inspectors, antivirus tools with a MITM filter, and nonstandard Windows Defender Firewall rules can also cause this.
4. The client is stuck on the handshake
This is the most basic case: the interface has already displayed “Connected,” but in reality the process is hanging. Restarting the app helps more often than it should. On Android, this is compounded by an aggressive battery optimizer that kills the VPN service in the background.
How to tell what exactly broke
| Symptom | Possible cause | What to check |
|---|---|---|
| Sites do not open by domain, but open by IP | DNS does not work through the tunnel | Change DNS to 1.1.1.1 / 8.8.8.8 or the service DNS |
| Loads for a long time, then “Server not responding” | The server IP is blocked by the operator | Change location or server; enable obfuscation |
| Right after connecting, the internet disappears completely | Killswitch + failed tunnel | Disable the killswitch temporarily, reconnect |
| One site works, another does not | Partial filtering or DNS cache | Clear the DNS cache, check the site without VPN |
| VPN works on a PC, does not work on a phone | Battery saver / OS restrictions | Remove restrictions for the VPN app |
| It stopped working for everyone at the same time | System-level blocking of a protocol or subnet | Change protocol (WireGuard → VLESS / Reality) |
How to check right now
To avoid guessing what exactly broke, it is convenient to first check whether the site you need opens without VPN and whether it is available through other VPN routes. Freedom Checker shows the availability of sites and services from different operators and through different protocols.
If the site opens for everyone without VPN but not through your VPN, the problem is DNS/the server. If the site is blocked for everyone, but is available through alternative VPN routes, you should change the protocol or service.
Failure or blocking?
A simple sign of a failure: the problem started after an app update, router reboot, or network change. The problem is reproducible only for you.
A sign of blocking: the same VPN server stopped working at the same time for you, for your neighbor, and in the service’s support chats; changing the location inside the same service does not help; changing to a masking protocol (VLESS Reality, Hysteria, AmneziaWG) does help — this means they are filtering not by IP, but by the protocol signature.
What to pay attention to
- First check the internet without VPN — this separates provider problems from tunnel problems.
- Ping the VPN server IP before connecting — if it is unreachable, the rest does not make sense.
- On mobile internet, DNS breaks more often; on home internet, IP routing does.
- Changed your router or firmware? Check MTU — an oversized packet can be cut without notification.
- A killswitch on an unstable connection gives “no internet” even during brief drops.
- If you use several VPNs at the same time, they conflict in routing tables.
- The situation may differ by operator, region, and time of checking.
Conclusion
“VPN is connected, but there is no internet” is not one problem, but four different problems: DNS, routing, IP blocking, and a stuck client. You can separate them by symptom and localize them quickly in 2–3 minutes.
Before blaming the VPN, make sure the site is available at all and that the problem is not on the operator’s side.