A VPN status of “Connected” confirms that the client has established a tunnel; it does not prove that every request from your device can reach the internet. The underlying Wi-Fi or mobile connection may need attention, the selected server may not be responding properly, or a DNS, proxy, firewall, or routing setting may be blocking traffic. Work through the checks below in order. After each change, test a normal website and an app you use regularly, so you can identify which change helped.

5

practical checks

1

change at a time

2

connection layers to check

1. Check the connection underneath the VPN

A VPN uses your existing internet connection to reach its server. If your router has lost its upstream connection, a mobile signal is unstable, or a public network requires a sign-in, the VPN may appear to connect while ordinary browsing still fails. Start by disconnecting the VPN temporarily and opening a few familiar sites. This is a diagnostic step, not a recommendation to leave the device unprotected on an untrusted network.

If the internet also fails with the VPN disconnected, troubleshoot Wi-Fi or mobile data first. Check whether another device on the same network can browse. If no device can connect, restart the router using its normal controls, check its status indicators, and contact the network provider if the connection remains unavailable. On mobile data, confirm that cellular data is enabled and that the device has a usable signal. Moving to a location with better reception or reconnecting to the network can help distinguish a coverage problem from a VPN problem.

Public Wi-Fi at hotels, airports, cafés, or campuses may show a sign-in or terms-of-use page before allowing general access. Disconnect the VPN, open the network’s legitimate login page, complete the required sign-in, and then reconnect the VPN. Do not enter account details into a page that looks suspicious or was opened from an unexpected prompt. If the sign-in page does not appear, follow the venue’s own instructions rather than repeatedly changing VPN settings.

When ordinary browsing works without the VPN but fails immediately after connection, the problem is more likely to involve the VPN route, client settings, or how the device directs traffic. Note the network you are using and whether all apps fail or only one. That distinction will make the next checks more useful.

2. Reconnect and test another server

A connection can become stale after a Wi-Fi change, a device wakes from sleep, or the client has been running for a long time. Disconnect from the VPN using the client’s own control, wait briefly, and connect again. If you have switched between Wi-Fi and mobile data, choose the network you intend to use before reconnecting. Avoid rapidly tapping several server entries: give each connection attempt time to complete and check whether the client reports an error.

If reconnecting does not help, select a different available server or route in the client. A particular route may be temporarily unavailable, congested, or incompatible with the network you are using. A nearby option can be a useful first comparison, but physical distance alone does not guarantee that a route will work better. If the client offers different route types, test one at a time and keep a note of the selection that succeeds.

There is an important distinction between connecting to a VPN server and reaching a destination after the connection is established. A successful handshake confirms the tunnel setup; a browser still needs working name resolution and a route to the site. If every app fails on one server but works on another, the issue points toward the route or server rather than a general Wi-Fi failure. If only a particular website or app fails, check whether that service itself is available and whether it has a separate account or network restriction.

Use the official client or a compatible client you trust, and confirm that its subscription or configuration has not become outdated. If the client reports that its configuration cannot be updated, use the service’s official account or support process to retrieve or refresh it. Do not paste a private subscription URL into a public diagnostic website or an unfamiliar converter.

What this check tells you: If a fresh connection or another server restores access, the original session or route was the likely cause. If every server behaves the same way, continue with device and DNS settings.

3. Follow a controlled test on your device

Before changing system settings, run a small, repeatable test. Record whether the VPN is connected, which network the device uses, and whether the failure affects all apps or just one. Then change one item, reconnect, and repeat the same test. This approach avoids leaving behind several simultaneous changes that are difficult to reverse.

  1. Confirm that browsing works with the VPN disconnected. If it does not, return to the Wi-Fi, mobile data, or captive-portal checks.
  2. Reconnect using the client’s normal control and test a familiar website in a private or fresh browser tab. Also test an app that does not depend on the same browser session.
  3. Try one alternate server or route, then return to the original choice if there is no difference.
  4. Check whether the client, operating system, or security software shows a blocked connection, permission request, or error message. Write down the message without sharing passwords or subscription details.
  5. Undo any temporary setting you changed if it does not improve access, then proceed to the next check.

To keep troubleshooting focused, compare the result over the same network and with the same destination. Switching networks, servers, browser settings, and DNS all at once makes it hard to tell which factor matters. If you need to ask for help, a useful report includes the operating system, client name and version, connection type, approximate time of the issue, and whether the problem affects all apps. Redact account identifiers, IP addresses if you do not want to share them, subscription links, and authentication fields from screenshots or logs.

If you are comparing connection options or need to review the service’s available platforms and routes, VPN40 VPN for China provides the relevant starting point. Return to the controlled test afterward and make sure the same device and network are being compared.

  • ✅ Test one change at a time and record the result.
  • ✅ Compare more than one app when diagnosing a system-wide failure.
  • ❌ Do not disable firewall or security protections as a first-line fix.
  • ❌ Do not share a subscription link or unredacted configuration in a support request.

4. Check DNS, proxy, and client routing

DNS translates a site name into the address a device needs to contact. If DNS requests are blocked, sent to an unreachable resolver, or handled differently by the VPN client, a site may fail to load even though the tunnel is connected. If the client has a DNS setting, note its current value before changing it. Prefer the client’s supported default or a resolver recommended by the service. Avoid copying an address from an unverified post: a resolver is part of your connection path and can affect privacy as well as availability.

Some clients let users choose between routing all traffic through the VPN and using rules that send only selected destinations through it. A rule may send a browser or app to a route that is unavailable, or leave a system service using a path that does not work on the current network. If you use rule-based routing, temporarily switch to the client’s documented global or full-tunnel mode as a test, if that mode is available. Record the previous mode and restore it if the test does not help. The setting names and behavior vary by client, so do not assume that two applications use identical rules.

Also look for a system proxy configured separately from the VPN. A proxy left over from a work network, local development tool, or another client can direct browser traffic to a service that is no longer running. On Windows, review the proxy controls in Settings under Network & internet. On macOS, inspect the active network service’s proxy settings in System Settings. On Android and iOS, check whether a proxy was configured for the connected Wi-Fi network. Only remove a proxy if you know it is not required for your organization or network.

Third-party VPNs, proxy apps, DNS filters, ad blockers, firewall tools, and endpoint security software may compete for the same network settings. Close or disconnect one competing tool at a time, then retest. Do not run two VPN clients simultaneously unless their documentation explicitly supports that arrangement. If a security product blocks the VPN, review its notification or allow-list guidance rather than turning off protection wholesale. On managed work or school devices, ask the administrator before changing proxy, firewall, or routing policies.

If changing DNS or a proxy setting does not help, restore the previous value before trying a different setting. This makes the test reversible and prevents a temporary experiment from becoming a lasting source of connection problems.

5. Review platform-specific network settings

On Windows, disconnect the VPN before reviewing whether Windows reports that the Wi-Fi or Ethernet connection has internet access. If the VPN client has an option such as a kill switch or “block connections without VPN,” understand its purpose before changing it. Such a control may intentionally stop traffic whenever the tunnel is disconnected or unavailable. If you use it, reconnect through the client and check its status rather than assuming that all traffic should be permitted. Avoid random network resets or command-line repairs from an unknown source; they can remove working network configuration without fixing the actual cause.

On macOS, confirm that the client has permission to add or manage its VPN configuration and that the active network service is the one you are using. If the system asks to approve a VPN configuration, follow the client’s official setup instructions. When testing a proxy, inspect only the active service, since settings for an unused connection may not explain the current failure. If the connection breaks after waking from sleep, disconnect and reconnect through the client before changing broader network preferences.

On Android, check that the VPN app is allowed to establish a connection and review Android’s VPN settings for an always-on VPN or a setting that blocks connections without a VPN. These options can be useful security controls, but an outdated or disconnected VPN may leave the device with no permitted route. If the problem began after switching Wi-Fi networks, reconnect to the new network and start the VPN again. Battery-management restrictions can also interrupt background activity on some devices; check the device maker’s guidance and adjust only the setting that applies to the VPN app.

On iOS, confirm the VPN profile is present and that the client is allowed to connect. If iOS displays an approval prompt for adding a VPN configuration, follow the official client instructions. A managed device may receive VPN, DNS, or network rules from an organization; do not remove a profile you do not recognize without asking its administrator. For a Wi-Fi-only failure, compare the same device on another trusted network if available. This helps separate a Wi-Fi configuration problem from an app or VPN issue.

On Linux, identify which network manager and VPN client control the connection before editing DNS or routes. Desktop distributions can manage DNS through NetworkManager, systemd-resolved, or another local service, and manually overwriting one configuration may conflict with the rest. Review the client’s logs for a clear connection or name-resolution error, but redact credentials and subscription data before sharing excerpts. If you use a command-line client, verify that the expected interface and routes are present using the documentation for that client; do not copy commands that flush all routes or firewall rules without understanding their effect.

Restore changes and escalate with useful details

After testing, restore any proxy, DNS, routing, or security setting that did not solve the problem. Disconnect and reconnect once using your normal configuration, then check whether ordinary browsing and the affected app work. If the device has internet without the VPN but consistently loses it with multiple servers, the client’s diagnostic log or a support request may reveal a route, authentication, or policy error. If neither the device nor other devices can browse without the VPN, focus on the local network or contact its administrator or provider.

When contacting support, describe the sequence of events rather than sending a vague “VPN is broken” message. Include the operating system, VPN client, whether the issue occurs on Wi-Fi, mobile data, or both, whether all apps are affected, and which checks you tried. Add the exact error text if one appears. Share logs only through an official support channel, and remove subscription URLs, passwords, tokens, and unrelated personal information first. Do not include full configuration files unless support specifically requests them through a secure process.

Some networks restrict VPN connections, and organization-managed devices may enforce policies that prevent a particular route or DNS setting. A connection problem in those circumstances may require the network administrator, not repeated changes to the device. Keep security controls enabled unless the responsible administrator or official client documentation provides a specific, safe troubleshooting step.

Bottom line: First verify the underlying internet connection, then reconnect and compare routes, then inspect DNS, proxies, and platform settings. Make each change reversible, and use the error details to decide whether the next step belongs to your device, network, client, or service support.