A VPN can show “Connected” while websites fail to load, apps report that they are offline, or only some services work. The connection indicator usually confirms that the client has established a tunnel or proxy route; it does not prove that your device has working internet access, that DNS is resolving correctly, or that every app is using the route. Start with the checks below in order. Each one is designed to isolate a different part of the connection without changing several settings at once.
Before troubleshooting, note whether the problem affects every website or just one app, and whether it began after changing networks, routes, client settings, or system permissions. If you can, keep the VPN disconnected briefly to check whether ordinary internet access works. Reconnect before using services that require the VPN, and avoid sharing passwords, subscription links, or account details while asking for help.
1. Check the underlying network first
A VPN depends on an internet connection beneath it. If Wi-Fi is connected to a router that has lost its upstream connection, the VPN app may retain a connected status even though there is no usable path to websites. Captive portals can cause a similar symptom: a hotel, airport, school, or public hotspot may require you to accept terms or sign in before normal traffic is allowed.
Disconnect the VPN temporarily and open a familiar website. If that also fails, troubleshoot the Wi-Fi or mobile data connection before changing VPN settings. Check that airplane mode is off, Wi-Fi or mobile data is enabled, and the device is connected to the expected network. If a sign-in page is required, disconnect the VPN, complete the network’s sign-in process in a browser, and then reconnect. Do not enter sensitive account details into a page unless you have verified that it belongs to the network provider.
If ordinary browsing works without the VPN but stops as soon as you connect, the underlying network is probably available and the next checks should focus on the VPN route, DNS, or client settings. If only one device is affected, compare it with another device on the same network. If every device has trouble, restart the router using its normal controls and check whether the network provider reports an outage. Avoid resetting a router to factory settings as an early troubleshooting step; that can erase its configuration without identifying the cause.
- ✅ Test one familiar website with the VPN disconnected, then reconnect and test again.
- ✅ Complete any public Wi-Fi sign-in before starting the VPN connection.
- ❌ Don’t change router DNS, firewall, or port settings until you know the local network is the problem.
2. Reconnect, then test another server or route
A route can become temporarily unavailable, congested, or unsuitable for a particular network. The client may still display a connection even when the selected route cannot deliver useful traffic. Disconnect fully, wait for the client to return to its idle state, and connect again. If the same result persists, select a different available server or route that fits the task you are trying to do.
Change only the route for this test. Keep the protocol, DNS options, system proxy mode, and other settings unchanged so the result is easier to interpret. After connecting, test a few ordinary websites in the same browser. If those load but one particular service does not, the issue may be specific to that service, its account requirements, or its own network checks rather than a total loss of internet access.
Route labels describe a location or route category; they do not guarantee that a specific website will work. Choose based on the access direction and the service’s requirements, not just on a familiar country or city name. For a broader overview of the service and its available routes, see VPNBig VPN for China. If a different route restores browsing, note which route worked and whether the first route fails consistently. That detail can help distinguish a temporary route issue from a device-wide configuration problem.
If changing routes makes no difference, reconnect to the original route before moving on, unless the client is still unable to establish a connection. Keeping track of the original selection makes it easier to undo a test and report the exact sequence of changes later.
3. Check DNS, proxy, and tunnel settings
DNS translates a website name into the address needed to reach it. If the VPN connects but name lookups fail, a browser may show an error such as “server IP address could not be found” even though the device has a route to the internet. Other symptoms include some apps working while others fail, or a website opening by address but not by its domain name. These clues are useful, but they do not prove that DNS is the only cause.
First, turn off any custom DNS setting you added for testing and return the client to its recommended or automatic configuration. If you use a separate DNS-filtering app, security suite, ad blocker, or local firewall, temporarily pause it only if you understand the effect and can turn it back on immediately. Do not disable protections permanently. Then disconnect and reconnect the VPN, close and reopen the affected app, and test again.
Also check how traffic is routed. Some clients use a system proxy, which covers apps that honor the operating system’s proxy settings. Other clients can use a tunnel mode, such as TUN, that routes a broader range of traffic but depends on client support, permissions, and system routing. A connected indicator does not necessarily mean every app is included. Check whether the affected app is excluded by a bypass rule, split-tunneling setting, or per-app routing option.
On Windows, review the client’s system-proxy or tunnel option and confirm that no old proxy address is left in the operating system after disconnecting. On macOS, check that the VPN client has the network permissions it requested and that another VPN or network extension is not active. On Android, inspect the VPN and per-app settings, and check whether an always-on VPN or “block connections without VPN” option is enabled. On iOS, reconnect through the VPN app and check for a second VPN or filtering profile that might be competing for network access. On Linux, review the client’s routing mode and system proxy environment, especially if the problem appears only in a terminal or only in graphical apps.
4. Run a short, controlled test
Use this sequence to narrow down the cause without making a collection of unrelated changes. Keep notes about what you observe. The goal is not to prove that one setting is always correct, but to find out whether the issue follows the network, the route, or the device.
- Test the network without the VPN. Disconnect the VPN and load a familiar website. If it fails, restore ordinary Wi-Fi or mobile data access first.
- Reconnect once. Wait for the client to report a completed connection, then test a website in a fresh browser tab. Avoid running several speed tests or downloads at the same time.
- Try one alternate route. Keep the other client settings the same. If browsing works on the alternate route, note the original and working selections.
- Check one routing or DNS setting. Restore custom settings to their recommended defaults, reconnect, and repeat the same browsing test. Do not change several options together.
- Test one other app or device. This helps establish whether the problem is limited to a browser, a particular device, or the whole network.
For a useful comparison, keep the test conditions as similar as possible: use the same network, browser, website, and approximate time, changing one factor at a time. A result from one website cannot establish that all internet traffic is working, and a speed-test result does not diagnose DNS, application routing, or access restrictions by itself. If you are new to subscription-based VPN clients, the quick-start guide can help you check that the client and imported configuration are set up as intended.
5. Try another supported protocol and review the kill switch
A protocol determines how the client establishes and carries a connection. Networks can treat different traffic types differently: a restrictive Wi-Fi network may interfere with a connection even when the same client works on mobile data. If your client offers more than one supported protocol, switch to one of its documented alternatives, reconnect, and repeat the same basic browsing test. Change only the protocol for this comparison, then return to the original choice if it does not help.
Available options depend on the VPN service and client. WireGuard is a VPN protocol; Shadowsocks, VMess, and Trojan are proxy protocols or solutions that compatible clients may support. Hysteria2 is based on QUIC and UDP, so its use depends on client support and whether the network permits the necessary traffic. These names do not guarantee that one option will be faster or more reliable in every location. Use only options provided by your service or documented by the client, and do not copy a protocol label from an unrelated guide as if it were a complete configuration.
Next, check the kill switch or network-lock setting. A kill switch is designed to block traffic when the VPN disconnects, to reduce the chance of traffic leaving outside the tunnel. If the VPN connection has failed or the client has not restored its routing rules properly, that protection can make the device appear offline. Use the client’s own controls to disconnect and reconnect, and check its documented recovery instructions. If you temporarily turn off a kill switch to diagnose the issue, do so only when you understand the privacy trade-off, avoid sensitive activity during the test, and turn the protection back on afterward.
Do not run two VPN clients at the same time. Their tunnel interfaces, system proxies, DNS settings, or kill switches can conflict. If you recently changed clients, disconnect the previous one fully and check that its system proxy or network extension is no longer active before testing the current client again.
When to contact support
Contact the VPN provider’s support team if ordinary internet works, you have tried a clean reconnect and at least one alternative route or supported protocol, and browsing still fails. Include practical information: your operating system and version, the client name and version, whether the issue affects all apps or only one, whether the connection works without the VPN, the route and protocol tested, and the exact error message. Mention when the problem began and whether it occurs on Wi-Fi, mobile data, or both.
Do not send a password, payment details, or a full subscription link in a public post or an unverified chat. If support requests diagnostic logs, use the client’s export feature and review the contents for personal information before sending them through the provider’s official support channel. A screenshot can help show the connection state, but hide account names, addresses, QR codes, subscription credentials, and unrelated notifications.
Keep a note of any setting you changed and whether restoring it altered the result. This lets support focus on the remaining possibilities instead of asking you to repeat the same checks. If the VPN disconnects unexpectedly, report that separately from a connected state with no browsing: those symptoms can point to different parts of the connection.