A VPN can show “Connected” while your browser still cannot open a page. The status usually means the client has established a tunnel, not that every part of your internet connection is working. Your device still needs a usable local network, a route through the tunnel, a working DNS resolver, and permission to send traffic through the VPN. A browser proxy or another security app can interfere as well.
Work through the checks below in order. After each change, test the same website or app again; changing several settings at once makes it harder to identify the cause. Menu names vary between operating-system versions and VPN clients, so look for the equivalent setting if your screen uses different wording.
- ✅ Check whether the internet works without the VPN before changing advanced settings.
- ✅ Change one setting at a time, then reconnect and test again.
- ✅ Restore any temporary change that does not help.
- ❌ Do not share your subscription link, configuration file, or account password while troubleshooting.
1. Check your Wi-Fi or mobile data first
A VPN cannot provide internet access if the connection beneath it is unavailable or repeatedly dropping. Before changing DNS or protocols, check whether the same device can load a familiar website with the VPN disconnected. If it cannot, the immediate problem is likely with Wi-Fi, mobile data, a captive sign-in page, or the local network rather than the VPN tunnel.
Test the connection without the tunnel
Disconnect the VPN briefly and open a site you normally use. On public Wi-Fi, a hotel, airport, school, or workplace network may require you to accept terms or sign in through a browser page. Complete that step on the local connection before reconnecting. If the sign-in page does not appear, open a regular website address rather than relying on an app that may keep retrying its previous connection.
On a home network, check that other devices can reach the internet. If none can, restart the router using its normal controls and verify that the internet service itself is available. If only one device is affected, toggle Wi-Fi off and on, forget and rejoin the network only if you know its password, or switch to mobile data as a comparison. On a phone, confirm that Airplane Mode is off and that mobile data is enabled when you are not using Wi-Fi.
Some networks restrict VPN traffic or require a browser-based sign-in before allowing general access. If the VPN works on mobile data but not on a particular Wi-Fi network, that contrast is useful evidence: it points toward a network-specific restriction or configuration. Do not try to bypass workplace or school network rules; ask the network administrator whether VPN use is allowed.
Restart the client cleanly
If the local connection works, disconnect from the VPN inside its client, wait until the status changes, and reconnect. If that does not help, fully quit and reopen the app. A device that has just resumed from sleep or switched between Wi-Fi and cellular service may retain a stale route for a short time. A normal restart can refresh the network state, but first save work that could be interrupted.
2. Refresh the route and check DNS settings
DNS translates a site name into the address a device uses to reach it. A tunnel can be active while name lookups fail, making a browser appear offline even when some network traffic is passing. A stale route can produce a similar symptom after a network change. Start with simple refreshes before editing system-level network settings.
Disconnect and reconnect once, then test both a website you know by name and an app that uses an existing connection. If apps that were already open behave differently from newly opened sites, close and reopen them. You can also try another browser or a different familiar website. One failed site may be an issue with that site, its content delivery network, or the browser rather than a general loss of internet access.
Next, inspect the VPN client’s DNS or network options. If you previously enabled a custom DNS server, private DNS, a content filter, or a DNS-over-HTTPS setting, temporarily return to the client’s default or automatic option and reconnect. Record the original value before changing it. On Android, Private DNS is a system setting that can affect name resolution; temporarily switching it to Automatic can help determine whether a manually specified hostname is involved. Restore your preferred setting if it is not the cause.
Windows and macOS also maintain DNS and network state outside the VPN app. Restarting the device is a reasonable first refresh. If you are comfortable using built-in network tools, follow the operating system’s official guidance for clearing its DNS cache rather than pasting unfamiliar commands from a forum. Do not enter arbitrary DNS server addresses just because they appear in a troubleshooting post: a resolver should be chosen deliberately, and changing it can affect privacy, filtering, or access to local services.
If only domain names fail while a specific app or an already-open connection still works, DNS is a stronger possibility. If absolutely nothing can connect, continue checking the route, client, and network permissions instead of repeatedly changing DNS values. A VPN client may also offer a setting to use the system DNS or its own resolver; test one mode at a time and note whether the result changes.
For people comparing VPN options for everyday browsing, the LeleVPN VPN for China homepage describes the service and its supported platforms. Regardless of provider, DNS behavior still depends on the device, client configuration, and network you are using.
3. Check for proxy settings and competing network apps
A system proxy and a VPN tunnel are different mechanisms. A proxy setting can direct browser traffic to a separate server, while the VPN client changes how device traffic is routed. If an old proxy remains enabled after you stop using it, a browser may keep sending requests to an endpoint that is unavailable. A second VPN, firewall, ad blocker, DNS filter, or traffic-monitoring app can also install network rules that conflict with the active client.
Check the operating system’s proxy settings and the settings inside your browser. If you intentionally use a proxy, note its current configuration before changing anything. Otherwise, turn off an unexpected manual proxy and test again. On Windows, review the system proxy controls; on macOS, review the active network service’s proxy options. Browser-specific proxy extensions may need to be disabled separately. Do not remove a proxy required by your organization or a managed device without asking its administrator.
Look for another VPN or network-filtering app that may still be running in the background. Disconnect it cleanly rather than force-stopping multiple services at once. On Android, a device generally uses one active VPN connection at a time, and an always-on VPN or “block connections without VPN” option can prevent traffic when the selected VPN is unavailable. Check which app owns the active VPN connection and review those settings before switching clients.
On iPhone and iPad, a VPN configuration, filtering profile, or managed configuration may be installed separately from the app you are currently opening. If the device is managed by an employer or school, do not delete profiles or certificates; contact the administrator. On desktop systems, security software can also filter traffic. If you suspect a conflict, use the software’s documented controls for a brief test instead of uninstalling it or leaving protection disabled.
| Possible conflict | Typical clue | Safe first check |
|---|---|---|
| Manual system or browser proxy | One browser fails while other apps behave differently | Review proxy settings and disable only an unexpected, unused entry |
| Another VPN client | The active VPN status changes unexpectedly or traffic stops after switching apps | Disconnect the other client and confirm which VPN is active |
| DNS or content filter | Some domains fail while other network activity continues | Temporarily test the filter’s documented default setting |
| Managed profile or firewall | Settings are locked or the device belongs to an organization | Ask the administrator before removing profiles or changing policy |
4. Try another server or a compatible protocol
A particular server route may be unavailable from your current network, temporarily congested, or incompatible with a network’s filtering rules. Disconnect and select a different available server location, then reconnect. If the client offers multiple entries for the same location, compare them one at a time. A change that works on one network but not another can indicate a route-specific issue; it does not by itself prove that your device is damaged.
If changing servers does not help, check the client’s protocol setting. Protocols such as WireGuard, OpenVPN, Shadowsocks, VMess, Trojan, and Hysteria2 are not interchangeable labels for the same connection method. Support depends on the service, operating system, and client. Use only a protocol that your provider and client explicitly support, and avoid importing configuration intended for a different app.
When a client offers an automatic protocol option, try it before manually changing advanced transport parameters. If automatic mode is unavailable, choose a documented alternative and record the original selection. Reconnect after each change. Do not combine a protocol change with a DNS change and a proxy change in the same test, because you will not know which adjustment mattered.
A subscription-based client may need to refresh its server list or subscription configuration before a newly added route appears. Use the client’s own update control and check that the subscription is still present. Do not post the subscription URL in a public support forum or send it to an unknown person: it may provide access to your account’s service configuration. If the list is empty, outdated, or reports an import error, check the provider’s official setup instructions for that specific client and platform.
Server availability and streaming access can vary by route, app, and network. A server that works for one task is not guaranteed to work for every website or service. For a fair test, use the same device, network, and destination while changing only the selected server or protocol. If none of the documented options connect, collect the client’s error message and proceed to the permission checks rather than repeatedly importing random configuration files.
5. Review app permissions, updates, and useful support details
VPN clients need the operating system’s permission to create or maintain a VPN connection. On Windows and macOS, check whether the app is blocked by a firewall prompt, security approval, or pending system permission. On Android and iOS, accept the operating system’s VPN configuration prompt for the app you intend to use. If you previously denied the request, open the system settings for VPN or network access and review the permission there. Exact menu names differ by OS version.
Check that the app is up to date through its official distribution channel and that the operating system has not paused or restricted it. On Android, battery optimization or background restrictions may interrupt a VPN after the screen turns off; review the app’s battery settings if the connection drops only in the background. On iPhone, check whether a profile or on-demand connection rule is repeatedly reconnecting. On desktop, confirm that the client is not being launched with an outdated configuration from an old installation.
If you use a third-party compatible client such as Clash Verge, sing-box, or Shadowrocket, verify that the imported subscription format and selected mode are supported by that client. A successful import does not necessarily mean the correct profile is active, and a connected indicator may refer to the local proxy listener rather than a successfully reachable remote route. Check the client’s own connection log for a specific error and compare its documentation with the configuration format you imported. Avoid editing low-level fields unless you understand what they control.
As a diagnostic only, you can disconnect the VPN and test an ordinary trusted connection to see whether the device has internet access. Do not leave a security feature disabled as a workaround, and avoid sensitive transactions on an untrusted network during the test. If the VPN connection itself is essential for your environment, skip this test and use a permitted alternate network or contact the administrator instead.
If the problem remains, gather information before contacting support: the operating system and version, VPN client name and version, whether Wi-Fi and mobile data behave differently, the selected server and protocol, the exact error text, and the changes you already tested. Include the time the issue began and whether other devices on the same network are affected. Do not include passwords, one-time codes, private keys, or a complete subscription URL. A short, ordered account of the tests is more useful than a screenshot of a “Connected” label alone.
- ✅ Confirm the app has permission to create a VPN connection.
- ✅ Update the client using its official source and check the client’s own error log.
- ✅ Note the operating system, network type, server, protocol, and exact error message.
- ❌ Do not send account credentials, private keys, or subscription links in a public post.
In most cases, the order of checks matters: establish that the local network works, refresh the connection, investigate DNS and proxy conflicts, then compare a supported server or protocol and verify permissions. If the issue follows one Wi-Fi network, focus on that network’s sign-in or restrictions. If it follows one device across different networks, focus on its VPN client, profiles, and system settings. This separation helps narrow the cause without making unnecessary changes to unrelated security or network configuration.