Skip to article

VPN Connected but No Internet? 5 Fixes to Get Back Online

A connected VPN does not always mean you can browse. Follow these quick checks for the kill switch, DNS, server, and protocol to restore access on Windows, Mac, Android, or iPhone.

A VPN client can show “Connected” while your browser says there is no internet. The status usually confirms that a tunnel or proxy connection was established; it does not prove that DNS is working, that every app is using the expected route, or that your local network is still providing access. Start by checking whether the internet works without the VPN, then work through the kill switch, DNS, server, and protocol settings. These checks apply to Windows, macOS, Android, and iPhone, although menu names vary between clients and operating-system versions.

1. Check whether the local connection works

First separate a VPN problem from a Wi-Fi, mobile-data, or router problem. Disconnect the VPN using its normal disconnect control, then open a familiar website or try another app that needs internet access. If nothing works with the VPN disconnected, changing VPN servers will not fix the underlying issue. Reconnect to Wi-Fi, check whether mobile data is enabled, and restart the router only if you control it and other devices are also affected.

If ordinary internet works without the VPN, reconnect and test more than one destination. Try a website by name and an app that you know usually works. If one app fails but others work, the cause may be that app’s settings, its own connection state, or the way the client routes its traffic. If every app fails only while the VPN is on, focus on the VPN connection and system network settings.

On a laptop, also check whether a browser is configured to use a separate proxy. A manually configured proxy can conflict with a VPN client or continue to direct browser traffic somewhere else after the VPN disconnects. On a phone, temporarily disable any other VPN, firewall, content filter, or network-monitoring app. Most mobile operating systems allow only one active VPN connection at a time, and two tools that both try to manage network traffic may interfere with one another.

  • ✅ Confirm that the same Wi-Fi or mobile connection works with the VPN disconnected.
  • ✅ Test more than one app or website after reconnecting.
  • ❌ Do not assume a “Connected” label proves that DNS and all app traffic are working.
  • ❌ Do not run two VPN clients at once while troubleshooting.

If access fails only on one Wi-Fi network, compare it with another trusted connection, such as your own mobile hotspot. A public or managed network may require you to accept a sign-in page before it allows general internet access. Disconnect the VPN, complete the network’s normal sign-in process, and then reconnect. Do not enter account credentials into an unfamiliar sign-in page or install a certificate just because a network prompt requests it.

2. Review the kill switch and routing settings

A kill switch is intended to block some or all network traffic when a VPN connection is unavailable. Depending on the client and operating system, it may remain active after you disconnect, after a connection attempt fails, or while the app is still running in the background. This can look like a general internet outage even though the client is doing what its setting is designed to do.

Open the VPN app and look for options such as Kill Switch, Block connections without VPN, Always-on VPN, or Block connections without VPN in the operating system’s network settings. Names and behavior differ by platform. If you are troubleshooting, turn the relevant setting off temporarily, disconnect the VPN, and check whether ordinary internet access returns. If it does, reconnect and decide whether to restore the protection after confirming that the VPN works correctly. Do not leave a security setting disabled by accident if you rely on it.

Also check split tunneling or application-routing rules. A rule may send a browser outside the tunnel while routing another app through it, or exclude an app that you expected to use the VPN. On desktop clients, inspect the selected mode, such as rule-based routing, global routing, or bypass mode. On mobile, review any app-specific exclusions. Return to a simple default routing mode for one test, rather than changing several rules at once.

When a client has imported a subscription or configuration, confirm that the selected profile is current and that the route list has loaded. Avoid editing server addresses, ports, or protocol fields by guesswork. A malformed configuration can produce a connection indicator without providing a usable route. If you are traveling and need an overview of the service and its supported platforms, QingVPN VPN for China Travel is the relevant starting point; for this troubleshooting step, use the settings shown by your own client and account.

Bottom line: If disabling a kill switch restores access, the block is likely related to the client’s protection or routing state. Re-enable protection only after you have tested a working connection and understand which traffic the setting blocks.

3. Refresh DNS and the device’s network state

DNS translates a website name into the address a device needs to reach it. A VPN may use its own DNS resolver, while the device or local network may have another DNS setting. If the tunnel connects but name lookups fail, websites may appear offline even when some network traffic can still pass. A stale network state after switching between Wi-Fi, mobile data, and VPN connections can cause similar symptoms.

Start with the least disruptive steps: disconnect and reconnect the VPN, then turn Wi-Fi off and on or briefly switch airplane mode on and back off. If that does not help, close and reopen the affected app. Restarting the device can clear temporary network state, but it should not be the first response if you have not yet checked whether the local connection itself works.

On Windows, you can use the client’s reconnect option and then restart the computer if needed. If you are comfortable with command-line tools, Windows includes commands such as ipconfig /flushdns to clear the local DNS cache. Run only commands you understand, and avoid copying broad network-reset scripts from an unknown source. On macOS, disconnect the VPN, reconnect to the network, and check the active DNS settings in Network settings; exact labels can vary by release. A restart is a reasonable next step if the settings look correct but name resolution still fails.

On Android and iPhone, first check whether a custom Private DNS setting, encrypted DNS app, content blocker, or device-management profile is active. Such settings can change how names are resolved independently of the VPN. If you change one for testing, record its original value so you can restore it. Do not set an arbitrary DNS address from an online post: a resolver can affect privacy, filtering, and access, and an unrelated address may not respond at all.

Use a browser’s normal refresh after reconnecting, and test a second website rather than repeatedly loading the same page. If a site works by an address but not by its name, that points toward name resolution, but it does not by itself identify which DNS setting is responsible. Restore any temporary DNS changes once the test is complete, then change only one setting at a time so you can tell which action made a difference.

4. Reconnect to a different server or network

A particular route may be unavailable from your current network, may not suit the destination you are testing, or may have a temporary connection problem. Disconnect cleanly, select another available server, and connect again. If the client offers locations or route names, choose a different option rather than repeatedly reconnecting to the same one. A route change is a diagnostic test, not a guarantee that every website or app will work.

Compare results in a consistent way: use the same device, local network, app, and destination for each test. If a second route works, the first route or its interaction with the local network may have been the issue. If all routes fail on one Wi-Fi network but work on mobile data, investigate the Wi-Fi network, its sign-in requirements, or any restrictions configured by its administrator. If routes fail on every network, move on to the client and protocol checks rather than continuing to switch locations.

Give the client time to finish disconnecting before starting a new connection. Repeated rapid changes can leave the device with a stale route or a partially updated network state. If the app shows that the server list has not refreshed, update the subscription or configuration using the client’s supported method, then select a route from the refreshed list. Keep your subscription link private; it may contain access credentials and should not be pasted into a public forum or an unfamiliar diagnostic website.

Record the useful details before contacting support: device and operating-system version, client name, whether the local internet works without the VPN, whether every app is affected, and whether another network or route changes the result. Do not include passwords, full subscription links, or screenshots that expose account credentials.

5. Check the protocol, client, and permissions

A VPN or proxy client must support the protocol and configuration it is asked to use. Protocols such as Shadowsocks, VMess, Trojan, Hysteria2, and WireGuard are not interchangeable names for the same connection. A client that supports one protocol may not support another, and a manually altered protocol field can make an otherwise valid profile unusable. Check the configuration source and the client’s documentation instead of guessing which protocol to select.

Confirm that the profile was imported into a compatible client and that the client has permission to create a VPN connection. On Windows and macOS, check that the app is allowed to install or use its network extension or tunnel component when the operating system requests permission. On Android and iPhone, accept the system VPN permission prompt for the client you intend to use. If you previously denied the request, review the operating system’s app permissions or VPN settings and grant access only to the app you trust.

Update the client through its official distribution channel if you suspect that it is outdated or damaged. Before reinstalling, make sure you can retrieve the correct configuration again; removing an app may erase locally saved profiles. Avoid installing unofficial builds or importing a configuration converted by an unknown service. If the same subscription works on another compatible device on the same network, compare the affected device’s client version, permissions, DNS settings, and routing mode rather than changing the account details.

  1. Disconnect the VPN and verify that ordinary internet access works.
  2. Disable other VPN or traffic-filtering apps for the test, and review the kill switch.
  3. Reconnect using a refreshed, compatible profile and one different available route.
  4. Check DNS and system VPN permissions, changing one setting at a time.
  5. Test the same app and destination again, then note the result before restoring any temporary setting.

This sequence helps narrow the cause without resetting the entire device or replacing settings that were working. If the client still reports a connection but no apps can access the internet, share the non-sensitive test results with the provider or network administrator. State whether the issue affects one network or all networks, and whether it began after an operating-system, client, or configuration change. This information is more useful than a screenshot of the connected status alone.

Bottom line: Test the local connection first, then isolate routing, DNS, route selection, and client compatibility one at a time. A connection label is only one clue; the comparison between VPN on and off is what tells you where to look next.
First Month Free