A VPN can show “Connected” while apps and websites still fail to load. The status usually confirms that a tunnel was created; it does not prove that DNS requests, traffic rules, the selected server, or the device’s internet connection are all working as intended. Start by checking whether the problem affects every app or just one, then work through the likely causes in a controlled order.

These five fixes cover common problems on desktop and mobile: a server that is not passing traffic, DNS resolution failures, conflicting proxy settings, restrictive app or device rules, and a problem with the underlying network. Change one thing at a time and retest. That makes it easier to identify the cause instead of losing track of several changes.

First, identify the scope of the problem

Before changing settings, determine what “no internet” means on this device. Try opening more than one website in a browser, then test an app that uses a different service, such as email or messaging. If only one app fails, the VPN may be working and the issue may be specific to that app, its account, or its own connection settings. If every app fails, investigate the tunnel, DNS, proxy, and network path.

Also compare access with the VPN on and off. Disconnect the VPN briefly and load a familiar website. If the device still cannot reach the internet, the VPN is unlikely to be the only cause. Check whether Wi-Fi or mobile data works on another device, and whether the current device can reach a local service such as the router’s settings page. If internet access returns as soon as the VPN disconnects, focus on the VPN client, selected route, DNS, or a conflict with another network tool.

Keep the test simple: use the same browser, website, and network while switching only the VPN state. Avoid judging the result from one website alone. A site can be temporarily unavailable, block a particular route, or fail because of a browser extension even when other traffic works. Note any exact error message, such as a name-resolution error, a timeout, or a message that the connection was refused; these clues point to different causes.

5

fixes to check

2

VPN states to compare

1

change at a time

Start here: If the device has no internet with the VPN disconnected, troubleshoot the underlying network before changing VPN settings.

Fix 1: reconnect and try another server

A client may establish a tunnel even when the selected server or route is temporarily unable to pass traffic for your device. First disconnect from the VPN inside the client, wait for the status to change, and connect again. If the problem remains, choose another available server or route and test the same websites and apps. A connection label by itself is not a guarantee that every destination is reachable through that route.

When switching routes, keep other settings unchanged. Do not simultaneously change the protocol, DNS option, and traffic mode: if the connection starts working, you would not know which change helped. If the client offers more than one protocol, use a protocol supported by both the client and the service configuration. A protocol name appearing in a generic troubleshooting guide does not mean it is enabled for every account, subscription, or client.

On a phone, make sure the old session has actually ended before starting another one. Some clients reconnect automatically, so tapping a second server may simply trigger a transition. On a computer, check the client’s connection log if available. Look for repeated reconnects, a route that cannot be established, or errors that appear at the same time as the failed browsing. Logs can help narrow the issue, but avoid sharing them publicly if they contain account details, subscription links, or other private information.

If every available route fails in the same way, continue with the next checks rather than repeatedly reconnecting. A local DNS setting, a system proxy, a firewall rule, or a restrictive network can affect multiple routes alike. If only one route fails while another works on the same device and network, the route itself or its compatibility with a particular destination is a more likely explanation.

  • ✅ Disconnect from the client, then reconnect once and retest.
  • ✅ Try a different available route while keeping other settings unchanged.
  • ❌ Do not run two VPN or proxy clients at the same time.

Fix 2: check DNS and proxy settings

DNS translates a website name into the address needed to reach it. If DNS is unavailable or a device keeps using an incompatible DNS setting, a VPN can appear connected while browsers report that a site cannot be found. A useful clue is that a service works by its app or an existing open session, while new website names fail to resolve. The pattern is not conclusive on its own, but it is a reason to inspect DNS-related settings.

Start with the VPN client’s DNS options. If you recently enabled a custom DNS server, encrypted DNS, or a DNS filter, temporarily return to the client’s default or recommended setting and reconnect. If the client has no such option, do not assume that changing DNS to an arbitrary public resolver is the right fix. DNS requests may be managed by the operating system, browser, security software, or VPN client, and changing one layer can conflict with another. Restore any custom setting you added only after confirming it is compatible with the current network and client.

Check system proxy settings as well. A manually configured HTTP or SOCKS proxy can direct browser traffic somewhere different from the VPN route. On Windows, review the proxy options in Network & Internet settings; on macOS, inspect the active network service’s proxy settings. On Android and iOS, check whether the connected Wi-Fi network has a manually configured proxy. If you use a browser proxy extension, disable it temporarily for a controlled test. Do not remove settings managed by an employer, school, or administrator without permission.

Some networks require a sign-in page before allowing internet access. This is common on public Wi-Fi, hotels, and guest networks. Disconnect the VPN, join the network, and complete its legitimate captive-portal sign-in in the browser. Then reconnect the VPN and test again. Do not enter credentials into a page that does not clearly belong to the network provider, and avoid using sensitive services on a network you do not trust.

If you need to verify the provider’s official client and setup information rather than relying on an unfamiliar download or configuration page, use Q9VPN China VPN Download as your starting point. Keep the troubleshooting process focused: verify the source of the client and configuration, then change only the DNS or proxy setting that is relevant to the observed symptom.

Useful clue: If websites fail by name but other network activity still works, inspect DNS and proxy settings before changing unrelated client options.

Fix 3: review device rules, firewalls, and split tunneling

Security software and traffic rules can block or redirect connections even when the VPN tunnel is active. A firewall may treat the VPN client as a new application after an update, or a device profile may restrict which apps can use the network. If the failure began after installing security software, changing a firewall rule, or updating the client, review that change first. Prefer allowing the legitimate VPN client through the relevant firewall rule over disabling the firewall entirely.

Look for split tunneling, per-app routing, or rules that decide which traffic uses the VPN. If a browser or app is excluded from the tunnel, it may take a different path from other apps. Conversely, a rule that sends all traffic through the tunnel may expose a route or DNS problem that is not visible in a more selective mode. Temporarily switch to the client’s basic or default routing mode, if available, and test again. Record the original mode so you can restore it if the test makes no difference.

On mobile devices, check for another profile or app that can control network routing. A work profile, parental-control tool, security filter, or another VPN client may compete for the system’s VPN slot or apply separate restrictions. On computers, inspect virtual network adapters and proxy tools only if you know what they are; removing an adapter at random can break other software. Disconnect unused VPN clients and restart the active one rather than trying to force two network tools to share control.

Also check whether the failure is limited to one application. Some apps use their own secure DNS, proxy, or connection method, while others follow the operating system’s routing rules. If only one app fails, update it from its official source, check its built-in network options, and test it without a browser extension or app-specific proxy. If the app still fails while other traffic works, report the app name and the exact error to its support team rather than changing system-wide settings unnecessarily.

  • ✅ Temporarily test the client’s default routing or split-tunnel mode.
  • ✅ Check for a firewall prompt or a recently changed network rule.
  • ❌ Do not disable all security protections as a permanent workaround.
  • ❌ Do not delete unfamiliar network profiles or adapters without identifying them.

Fix 4: test the network, then restart the device

A weak or restricted underlying connection can prevent a VPN from carrying useful traffic. Compare Wi-Fi with mobile data, or compare the current Wi-Fi with another network you are authorized to use. If the VPN works on one network but not another, the difference may be the router, local DNS, a sign-in requirement, or network filtering—not a setting that should be changed on every device. Public and managed networks may restrict VPN traffic, and only the network administrator can clarify its rules.

Restart the connection in a deliberate order. Disconnect the VPN, turn Wi-Fi or mobile data off and back on, then wait for the device to regain ordinary internet access before reconnecting. If the problem persists, restart the device and router when you have permission to do so. Restarting can clear a stuck network session, but it will not fix an incorrect proxy, an invalid rule, or a network that intentionally blocks the connection. Treat it as a diagnostic step, not proof that the underlying cause is resolved.

Check whether a captive portal, data-saving mode, low-data setting, or background restriction is affecting the client. On mobile, confirm that the VPN app is permitted to use the active network and has not been restricted by battery or data controls. On desktop, verify that the active connection is the one you intend to use, especially if Ethernet, Wi-Fi, a hotspot, and virtual adapters are all present. If you use a metered or managed connection, follow its provider’s instructions rather than bypassing its access controls.

After a network change, test both ordinary browsing and the app that originally failed. If the VPN connects but traffic stops only after the device sleeps or changes networks, note the timing and the client’s reconnect behavior. Updating the client from an official source may help if the issue is tied to a known compatibility problem, but do not import an old configuration from an unknown source just to test whether it connects.

Compare before you reset: A result that changes between Wi-Fi and mobile data points toward the network path; a result that follows the device across networks points toward its configuration or client.

Fix 5: update carefully and collect useful details

If the checks above do not restore access, update the VPN client and operating system using their official update channels, then restart the client and test again. Before updating, make sure you can retrieve the correct account or subscription configuration if the app asks you to import it again. Do not delete a working profile or clear all app data unless you understand what will be removed and can set the client up again.

Next, collect a short, reproducible description of the failure. Record the device and operating system, client name and version, whether the issue affects every app or only one, whether it occurs on Wi-Fi and mobile data, and the exact error text. Note which basic checks you tried: reconnecting, changing routes, reviewing DNS or proxy settings, and testing the network with the VPN disconnected. This gives support teams enough context to distinguish a route problem from a device or network configuration problem.

Protect your account while seeking help. Do not post a subscription URL, password, authentication token, or full diagnostic log in a public forum. If a support team requests logs, use its official private channel and review the file for personal or account information first. A screenshot can be useful, but crop out notifications, email addresses, device identifiers, and unrelated private content.

Avoid drastic fixes as a first response. Factory-resetting a phone, deleting every network profile, installing an unofficial client build, or turning off security protections can create new problems and may not address the cause. If the device is managed by an organization, ask its administrator before changing profiles or firewall settings. If the VPN works on one network but not another, ask the network provider whether its connection requires a portal or restricts VPN traffic.

Once service is restored, undo temporary tests that did not help. Re-enable any firewall protections you paused, return proxy and DNS settings to the intended configuration, and restore the routing mode you actually need. Retest the apps that matter to you. A good fix is not simply a momentary connection; it is a clear, repeatable configuration that does not leave unnecessary security settings disabled.