A VPN can show “Connected” while websites and apps still fail to load. That status usually means the client has established a tunnel; it does not guarantee that your device has working DNS, a usable route to the internet, or access through the selected server. The cause may be a temporary network change, a stale proxy setting, a DNS conflict, or an issue affecting one route rather than the whole connection.

Use the checks below in order. First determine whether the problem affects every app or only one, then test the underlying network and the VPN settings. These steps apply across Windows, macOS, Android, iOS, and Linux, though menu names differ between operating-system versions and clients.

Identify where the connection breaks

Before changing settings, note what you can and cannot reach. Try opening more than one website and one app. If only a single site or app fails, the VPN may be working and the problem could be that service, its account, or its own connection settings. If nothing loads, continue with the network and tunnel checks.

Next, disconnect the VPN briefly and try the same sites using your ordinary connection. If they also fail, troubleshoot the Wi-Fi, mobile data, router, or local network first. If they work without the VPN but fail as soon as you connect, focus on the VPN client, selected server, DNS, and proxy configuration. Reconnect after this comparison so you do not accidentally leave traffic on a connection you did not intend to use.

Check whether the device recently changed networks. Moving from Wi-Fi to mobile data, joining a workplace network, waking from sleep, or switching between access points can leave a client with outdated routes. A “connected” label may remain visible even when the underlying network has changed. Also look for a captive-portal sign-in page: hotels, airports, and public networks may require you to accept terms or sign in before they provide internet access.

  • ✅ Test multiple websites and apps to distinguish a single-service problem from a device-wide one.
  • ✅ Compare access with the VPN disconnected, then reconnect before continuing.
  • ✅ Check whether the Wi-Fi or mobile-data network recently changed or requires a sign-in page.
  • ❌ Do not assume that a connected indicator proves DNS and internet routing are both working.
Start here: If the internet also fails without the VPN, fix the underlying network first; if it works only when disconnected, investigate the tunnel and its settings.

Seven quick fixes to try in order

Make one change at a time and retest after each one. Changing several settings together can make it difficult to identify the cause, and it may introduce a second problem. If you use a managed work or school device, follow its administrator’s instructions before changing proxy, DNS, firewall, or profile settings.

  1. Refresh the connection. Disconnect from the VPN in its client, wait for the status to change, and reconnect. If that does not help, quit and reopen the client. On a phone, confirm the client is still allowed to run in the background. Avoid force-stopping system networking components or repeatedly toggling settings while the client is still applying a configuration.

  2. Confirm that the underlying network works. Disconnect the VPN temporarily and load a familiar site. If it fails there too, reconnect to Wi-Fi, check mobile data, or restart the router if you control it. On a public network, open a browser without the VPN and complete the captive-portal sign-in. Once the network itself is online, reconnect the VPN and test again.

  3. Switch to another available server or route. The selected server may be busy, temporarily unreachable, or unable to complete DNS requests from your current network. Disconnect before selecting a different route, then wait for the client to report a fresh connection. Do not judge a server from its name alone: test whether ordinary browsing and the specific apps you need work. A change of route can also affect the region shown to websites.

  4. Check DNS behavior. DNS translates a site name into an address. If names fail to resolve while some existing connections continue, DNS is a likely part of the problem. Restarting the VPN often reapplies the DNS settings supplied by the client. Check whether a custom DNS service, encrypted-DNS option, filtering app, or parental-control feature is active on the device or router. Temporarily disable only settings you control, make a note of their original values, and restore them if the test makes no difference. Do not enter an unfamiliar DNS address just because it appears in an online troubleshooting post.

  5. Look for a leftover proxy setting. VPN clients may use a system proxy, configure one for a particular app, or route traffic through a tunnel without changing the browser’s proxy settings. These approaches are not interchangeable. Check the operating system’s proxy panel and the affected app’s own network settings for a proxy that another tool may have left enabled. If your current VPN client manages the proxy, do not clear it blindly; use the client’s repair or reset option, or consult its setup instructions. A proxy mismatch can leave the browser unable to connect even though other apps still work.

  6. Review split tunneling and app exclusions. Split tunneling sends only selected apps or destinations through the VPN. If the failing app is excluded, it may use a different route from the rest of the device. If only one app fails, check whether it is included or excluded and whether its own proxy setting conflicts with the client. Temporarily use the client’s default routing mode as a comparison, if available, then restore your preferred rules. Do not change company-managed routing rules without permission.

  7. Change the protocol only if the earlier checks fail. The protocol is the method used to establish and carry the encrypted connection. Networks may treat protocols differently, and a client may offer more than one option. Disconnect first, choose another protocol supported by that client and service, reconnect, and repeat the same browsing test. A protocol change can help when a network blocks or disrupts one connection method, but it cannot fix a broken Wi-Fi connection or an account-level issue. Avoid assuming that every client supports every protocol.

When following a consistent setup matters, consult the provider’s official configuration instructions rather than mixing settings from unrelated apps. For example, VPN72 China VPN is the site’s home page; use the relevant client’s own instructions to confirm which connection options and routes are available for your account.

After each change, test a normal website and the app that originally failed. If the browser works but one app does not, the issue is more likely to involve that app’s proxy, DNS, permissions, or split-tunnel rule than a complete loss of internet access.

Platform-specific checks for Windows, macOS, phones, and Linux

The same network fault can appear differently on each platform. Start with the client’s connection state, then check operating-system settings that can override or restrict its traffic. Menu labels vary across versions, so use Settings search when a named control is not where you expect it.

Windows

Open Windows network settings and review the proxy section. If a proxy was configured by another application, confirm that it is still required; if your VPN client manages it, use the client’s documented controls instead of deleting values at random. Also check whether the VPN client is allowed through the firewall and whether a security product recently changed its network rules. If only a browser fails, inspect that browser’s proxy or secure-DNS settings as well. Restart the VPN client after correcting a setting so it can rebuild its routes.

macOS

In System Settings, inspect the active network service’s proxy and DNS settings. A custom entry may be intentional, particularly on a managed network, so note its current state before making a temporary comparison. Check whether a content filter, security app, or another VPN client is also running. Two tools attempting to control network routing at the same time can produce confusing results. Quit unused proxy or VPN apps, reconnect the intended client, and test the affected app again.

Android-and-ios

On Android, check the current Wi-Fi network for a manually configured proxy and review Private DNS if you have set a custom provider. Private DNS availability and behavior depend on the Android version and network. Also check battery or background restrictions if the VPN disconnects after the screen locks. On iOS, review the VPN profile and any DNS or content-filter configuration installed by another app or organization. If a profile is managed, do not remove it without authorization. On either platform, switching between Wi-Fi and mobile data is a useful comparison, but remember that a mobile-data restriction or carrier setting can affect the result.

Linux

On Linux, check the desktop network settings, the VPN client’s status, and whether another network manager or proxy tool is active. Some distributions use NetworkManager, while DNS handling may involve systemd-resolved or another resolver; the exact arrangement depends on the distribution and configuration. Prefer the controls provided by your desktop environment or VPN client. If you inspect resolver or route information in a terminal, use read-only checks first and avoid copying commands that overwrite resolver files or flush networking rules unless you understand the effect and have a recovery path.

For any platform, a full device restart is a reasonable later test if the client cannot restore routes after a network change. Save work first, restart once, connect to the underlying network, and then launch the VPN client. Reinstalling the client should not be the first response: it may remove profiles or settings without addressing a router, DNS, or network-policy problem.

When changing servers or protocols is not enough

If a different server and a different supported protocol produce the same result, look beyond the tunnel choice. A router may have lost internet access, a local firewall may block the client, or a workplace network may restrict VPN traffic. Try another trusted network, such as your own mobile connection, only if doing so is appropriate for your data plan and the device’s policies. If browsing works on one network but not another, that comparison points toward a network-specific restriction or configuration rather than a general device failure.

Check the client for a clear error message, a failed DNS indicator, or a status that changes immediately after connection. Record what happened, including the platform, network type, selected route, protocol option, and which tests succeeded. Do not include passwords, subscription URLs, private keys, or account tokens in screenshots or support requests. A subscription link can grant access to your configuration, so treat it as private account information.

Some apps use their own DNS, proxy, or certificate settings. If ordinary browsing works but a work app, game, calling app, or streaming service does not, check that app’s support guidance and network requirements. A VPN connection cannot guarantee that a third-party service will accept a route, account region, or connection method. Where an app is business-managed, ask its administrator before changing security or routing controls.

Useful comparison: If the same device works on another network, investigate the original network; if every network fails only while the VPN is active, focus on client settings, DNS, and the selected route.

Prevent the same problem from returning

Once browsing works, restore any temporary DNS, proxy, or split-tunneling settings that you changed and test again. Keeping a short note of the original values makes it easier to reverse a troubleshooting step. If you disabled a security feature for comparison, turn it back on unless its administrator or official documentation tells you otherwise. Leave only one VPN or proxy tool in control of the system route unless the tools are specifically designed to work together.

After a network change, allow the client to reconnect before testing several apps at once. If you routinely move between home Wi-Fi, public Wi-Fi, and mobile data, learn where your client reports route and DNS status, and make sure its background permissions are appropriate for your device. Keep the client and operating system updated through their trusted distribution channels, but avoid installing multiple clients simply to test a connection; they can leave competing profiles or proxy settings behind.

A practical troubleshooting record can be brief: whether the internet worked without the VPN, which network was in use, whether another server helped, and whether a browser and the affected app behaved differently. That is enough to identify patterns without exposing private configuration details. If the problem continues, provide those observations to the network administrator or service support team and ask which logs are safe to share.

  • ✅ Retest after restoring temporary settings so you know which change actually helped.
  • ✅ Keep one VPN client in control of routing during diagnosis.
  • ✅ Protect subscription links, credentials, and private configuration details.
  • ❌ Do not delete managed profiles, disable security protections permanently, or apply unknown network commands as a shortcut.

In most cases, a connected-but-offline symptom can be narrowed down by separating the underlying network from the VPN, then checking DNS, proxy settings, routing rules, and the selected server in that order. Make one change at a time, keep a way to restore the original configuration, and escalate with specific observations if the fault persists.