A VPN client can show “Connected” while a browser still fails to open websites. The status usually confirms that the tunnel was established; it does not guarantee that DNS requests, traffic rules, the browser, and the destination site are all working together. Start by checking whether the problem affects one website or many, then work through the fixes below in order. Change one thing at a time so you can tell which step made a difference.
Identify what is not loading
Before changing settings, note what the failure looks like. A blank page, a DNS error, a connection timeout, and a site that loads without images can have different causes. If the browser displays an error code, write it down. Also note whether the VPN client reports an active connection, which network you are using, and whether the issue began after changing a server, profile, browser setting, or network.
Test a few unrelated websites in the same browser. If only one site fails, its own availability, account checks, content restrictions, or browser data may be involved. If several sites fail in one browser but work in another, focus on that browser’s proxy, DNS, extensions, and cache. If websites fail across browsers and apps, investigate the device’s network and VPN routing instead.
Where possible, compare the same website with the VPN disconnected and reconnected. A successful direct connection followed by a failed VPN connection points toward the selected route, DNS handling, or a compatibility issue, but it does not by itself prove which one is responsible. Avoid repeatedly refreshing a site during the test; wait for each attempt to finish and record the result.
Check DNS and browser settings
DNS translates a website name into the address a device needs to connect. A VPN may establish its tunnel successfully while DNS queries still fail, use an unsuitable resolver, or take a path different from the website traffic. This can make a site appear unavailable even though the connection indicator remains on.
First, fully disconnect and reconnect the VPN, then restart the browser and try the site again. If the issue continues, check whether the browser has a custom DNS or “secure DNS” setting enabled. Depending on the browser and VPN client, encrypted DNS may use a resolver outside the system’s usual path. Temporarily return the browser to its default or system-managed DNS behavior and test again. If you use a custom setting for a specific reason, restore it after testing and consult the browser or VPN client documentation for compatible options.
You can also clear the device’s DNS cache. On Windows, open Command Prompt and run ipconfig /flushdns. On macOS, DNS cache commands and behavior can vary by system version; use the current Apple documentation or restart the Mac instead of copying a command intended for a different release. Linux distributions use different resolver services, so check which service is active before using a cache-flush command. On mobile, disconnecting the VPN and toggling the network connection, or restarting the device, is often a simpler first test.
Check the browser’s proxy settings as well. A manually configured proxy can conflict with a VPN client, leaving the browser pointed at a proxy that is unavailable or no longer needed. Review the operating system’s proxy settings and the browser’s own settings, and remove only configurations you recognize as unnecessary. In a managed work or school environment, do not remove an administrator-provided proxy without permission.
Review VPN routing and traffic rules
Many clients can send all traffic through the VPN or use rules to send some destinations directly. This behavior may be labelled global, rule-based, split tunneling, or something similar; names differ by client. If a rule sends the affected website through a route that is unavailable, or excludes traffic that you expected to protect, the browser’s behavior can be confusing even though the VPN tunnel is active.
For a controlled test, temporarily select the client’s mode that routes all traffic through the VPN, if that option is supported. Then retry the site. If it opens, inspect the rules for the website’s domain and any related domains used for sign-in, images, scripts, or content delivery. A single site can rely on several hostnames, so changing only one rule may not address every request. Return to your preferred routing mode after testing and adjust rules only when you understand their effect.
Also check for overlapping network tools. Running two VPN clients, a proxy application, a firewall with custom rules, or a security product that filters web traffic can create competing routes or DNS behavior. Disconnect other proxy or VPN tools before testing, but do not disable essential security protection as a routine fix. If you need to diagnose a firewall, use its documented allow-list or logging controls rather than turning it off indefinitely.
If you need a place to review the client and account options before continuing, the China VPN Download page is a useful starting point. Keep the troubleshooting itself focused on the failing site and the settings that affect its traffic.
- ✅ Confirm whether the client is in global or rule-based mode before changing routes.
- ✅ Test one routing mode at a time and restore your preferred settings afterward.
- ❌ Do not run multiple VPN or proxy clients simultaneously while diagnosing a route conflict.
Switch the server and check the network
A route can be connected but still fail to reach a particular destination reliably. The selected server may be temporarily congested, unavailable for that website, or affected by a network path between your device and the service. Reconnect to a different available server in the client, then test the same website in the same browser. Keep other settings unchanged so that the comparison is useful.
If the client offers several locations, choose a nearby option as a first comparison, or choose a different location when the website requires a particular region. Neither choice guarantees access: websites can apply their own location, account, or anti-abuse checks, and a location label alone does not establish how the site will respond. If one server fails and another works, the issue may be specific to the original route rather than your browser.
Check the underlying network too. If websites fail only on a particular Wi-Fi network, compare with mobile data or another trusted connection where available. A public or managed network may require you to accept a captive-portal page before normal internet access is allowed. Disconnect the VPN briefly, complete the network’s legitimate sign-in process if appropriate, and reconnect. Do not submit sensitive credentials to a portal unless you recognize and trust it.
On mobile, confirm which network is active and whether the device has moved between Wi-Fi and cellular data. A VPN may need to reconnect after that transition. On a computer, check that the operating system has not switched to a disconnected network adapter. If the VPN client shows repeated reconnects, resolve that underlying connection instability before treating a single website as the cause.
Check browser, device, and site compatibility
When only one browser is affected, open the website in a private window or a different browser. If it works there, temporarily disable extensions that filter traffic, change DNS, block scripts, or manage cookies. Then re-enable them one at a time to find a conflict. A privacy extension or content blocker can prevent a site’s sign-in page or essential scripts from loading, which may look like a network failure.
Clear data for the affected site rather than wiping every browser setting immediately. Old cookies, cached redirects, or stale service-worker data can keep sending the browser into a broken state. Be aware that clearing site data may sign you out or remove local preferences. If the site still fails in multiple browsers, the cause is less likely to be a single extension, though browser-level DNS or proxy settings can still matter.
On phones and tablets, force-close the affected app or browser, reopen it, and check whether its network permissions or data-saving settings have changed. Some apps use their own networking behavior or do not follow the same routing rules as the browser. If the website works in a browser but not in an app, focus on the app’s version, account state, network permissions, and any app-specific proxy or DNS configuration.
Finally, check whether the website itself is available. Try its official status page or another trusted way to confirm service health. A site may be undergoing maintenance, blocking a particular request, or rejecting a session for reasons unrelated to the VPN. If the site fails both with and without the VPN across browsers, changing VPN settings is unlikely to fix a site-side outage.
When to change the VPN protocol
If DNS, routing, browser settings, server selection, and the underlying network all check out, consider whether the current protocol is compatible with the network you are using. Some networks restrict or interfere with particular connection methods. A client may offer protocols such as Shadowsocks, VMess, Trojan, Hysteria2, or WireGuard, but support depends on the service, subscription, client, and configuration. The names are not interchangeable, and not every client can import or use every protocol.
Change protocols only through a supported option in your VPN client or service instructions. Select one alternative, reconnect, and repeat the same website test. If it makes no difference, restore the original setting before trying another supported option. Avoid manually editing subscription data or copying protocol settings from an unrelated guide; an incomplete or mismatched configuration can prevent connections or route traffic in an unexpected way.
If a site continues to fail, collect useful details before asking for help: the device and operating system, client name, whether the failure affects one site or many, the selected routing mode and server, the protocol shown by the client, and the exact browser error. Remove passwords, subscription links, account tokens, and other private information from screenshots or logs. This information helps distinguish a client configuration issue from a browser, network, or website problem without requiring risky trial-and-error changes.
In short, a “Connected” label is only one part of the diagnosis. Check scope first, then DNS and browser proxy behavior, traffic rules, server and network conditions, and finally compatibility. Keep each test reversible, use only options supported by your client, and stop changing VPN settings if evidence points to a browser extension, a managed network, or an outage at the website itself.