A VPN can show “Connected” while websites and apps still fail to load. That status usually confirms that the client has established a tunnel; it does not prove that your device has working internet access, that DNS is resolving correctly, or that traffic is taking the route you expect. Start with the checks that are easiest to reverse, and change one thing at a time so you can identify what helped.
Before troubleshooting, note whether the problem affects every app or only one, whether it began after changing networks or settings, and whether the same device works when the VPN is disconnected. Avoid resetting network settings or deleting a profile as your first move: those steps can erase useful configuration without addressing the cause.
Start with the scope of the problem
First determine whether the internet connection works independently of the VPN. Disconnect in the VPN app, then open a familiar website or use an app that does not depend on the affected service. If the device still cannot get online, the VPN tunnel is unlikely to be the first problem to fix. Check Wi-Fi or mobile data, the router, and any captive portal that requires you to sign in.
If the internet works with the VPN off but fails as soon as you connect, concentrate on the VPN client, selected server, DNS, or routing settings. If only one browser or app is affected, check its own proxy, privacy, or network settings before changing the whole device. When possible, compare the result on another device using the same network. This helps separate a device-specific issue from a network or service issue.
- ✅ Confirm that Wi-Fi or mobile data works with the VPN disconnected.
- ✅ Test more than one website or app to rule out a single service outage.
- ✅ Note whether the problem follows the device, the network, or one particular app.
- ❌ Do not change several network settings at once; you may lose track of the cause.
Check whether the device is waiting for a network sign-in page. Hotels, schools, airports, and some public Wi-Fi networks may require you to accept terms or enter a code before internet access is available. Disconnect the VPN temporarily, complete the network’s sign-in process using its normal instructions, and then reconnect. If the sign-in page does not appear, open the network’s official sign-in prompt or ask its operator for help rather than entering account details into an unfamiliar page.
Seven fixes to try, from simple to specific
Fix 1: Recheck the connection and restart the client
Turn the VPN off, wait briefly, and connect again. If that does not help, fully quit and reopen the VPN app; merely closing its window may leave the background service running. On a phone, toggle Wi-Fi off and back on, or switch between Wi-Fi and mobile data to see whether the issue is limited to one access network. On a computer, reconnect to the current network before opening the VPN again. A device restart is a reasonable next step if the client remains stuck, but save your work first.
Make sure you are using the intended VPN profile and that the app has not been paused. If your client displays connection details, check whether it reports an established tunnel rather than only a selected server. Do not share passwords, private keys, or full configuration files when asking for help.
Fix 2: Choose another server or location
A particular server can be temporarily busy, under maintenance, or unsuitable for the network you are currently using. Disconnect, choose a different available server, and test the same website again. If the app offers several routes in the same location, compare them one at a time. A server that connects successfully is not automatically the best route for every site, so judge it by whether the services you need actually load.
Keep the comparison controlled: use the same device, network, and test site, and change only the server. If one route works while another does not, record the affected location and the time of the test for support. Do not assume that a website’s failure means the entire VPN is offline; the website may have its own availability or access restrictions.
Fix 3: Check for a second proxy or VPN
Two tools trying to direct traffic at the same time can create conflicting routes. Check whether another VPN app, system proxy, browser proxy extension, security product, or local traffic-filtering tool is active. Turn off only the extra proxy or VPN temporarily, then test again. If that restores access, re-enable tools one at a time to find the overlap and decide which one should manage the connection.
On Windows and macOS, review the operating system’s proxy settings as well as any proxy configured inside the browser. On Android and iOS, check whether another VPN profile or filtering app is active; many mobile systems allow only one VPN connection at a time. In compatible clients such as Clash Verge or sing-box, confirm that the expected profile and routing mode are active. A client importing a subscription may update server configuration, but its routing rules and system proxy settings can still determine which apps use the route.
If the VPN app offers split tunneling or per-app routing, check whether the affected browser or app is excluded. Temporarily return to the standard routing mode if you can do so safely, then test again. Restore any custom settings that did not affect the problem. For a managed work or school device, do not remove an organization’s proxy or security profile without permission.
Fix 4: Review DNS and the kill switch
DNS translates a website name into the address needed to reach it. If the tunnel connects but name lookup fails, a browser may report that it cannot find a site even though the VPN appears active. If your VPN client provides a DNS option, return it to the default or provider-recommended setting for a test. Avoid copying DNS addresses from random posts: a setting that works on one network may not suit yours, and changing DNS alone does not repair every connection problem.
A kill switch is designed to block traffic if the VPN drops, helping prevent unprotected traffic from leaving the device. Depending on the app and operating system, it may continue blocking internet access after a disconnect or when a connection attempt fails. Check the VPN app’s kill-switch status and description. If you turn it off briefly to diagnose the problem, do so only if you understand that traffic may no longer be routed through the VPN; turn it back on after testing if you need that protection.
On a phone, also check whether a system-level “always-on” VPN or “block connections without VPN” option is enabled. These options can be useful when intended, but they may prevent all internet access if the selected VPN profile is unavailable. Change one option at a time and restore the original protection settings when the test is complete.
Fix 5: Try a supported protocol
Networks sometimes handle VPN protocols differently. If the client provides a protocol selector, try another option that the service and client both support, reconnect, and test the same destination. This is a diagnostic comparison, not a reason to download an unknown configuration or install an unverified protocol add-on.
Protocol names are not interchangeable: Shadowsocks, VMess, Trojan, Hysteria2, and WireGuard use different configuration formats and connection behavior. A profile for one cannot be converted into another by renaming a file. When using a third-party client, confirm that it supports the protocol and subscription format supplied by your VPN provider, and use the provider’s import instructions. If the app does not expose protocol settings, do not edit configuration fields you cannot verify; ask support which options are appropriate for that client.
Fix 6: Update the client or reimport its profile
An outdated app, an incomplete profile, or a failed subscription update can leave the client with settings that no longer match the service. Check for an update using the app’s official distribution channel, then reopen the client and reconnect. If the provider supplies a subscription link, refresh or reimport it using the client’s documented procedure. Keep a copy of any custom routing rules you created before replacing a profile, and do not post a private subscription link publicly.
If the problem began immediately after an update, note the app version and the change in behavior. Do not install a modified build from an unknown source as a workaround. If an official update is unavailable or reimporting would remove settings you rely on, gather the error details and ask the provider before deleting the configuration.
Fix 7: Check the current network and its restrictions
Some networks limit particular connection types, require a browser sign-in, or block unknown traffic. Test on another trusted connection if available, such as your own mobile data, without changing multiple VPN settings at the same time. If the VPN works there but not on the original network, the difference points toward that network’s rules, router, or access procedure. Follow the network operator’s policies; do not try to bypass restrictions on a network you are not authorized to use.
On a home network, a router restart may help if other devices are also having trouble, but check whether anyone else is relying on the connection first. If only the VPN device is affected, focus on its client and configuration rather than resetting the router. If this began after a router setting changed, restore that setting only when you know what it does.
Apply changes safely and keep a useful record
For a clean test, disconnect the VPN, note the current settings, and make one reversible change. Reconnect and check the same destination. If there is no improvement, undo that change before moving to the next one. This avoids ending up with several simultaneous changes that are hard to explain or reverse.
For example, if you switch protocols and access returns, repeat the test after reconnecting once more. If the problem returns only on one network, record that distinction. If changing a proxy setting fixes one app but disrupts another, restore the previous setting and investigate the app-specific configuration instead. Do not clear all app data, remove every network profile, or reset all network settings unless the provider or device documentation recommends it and you understand what will be erased.
When a supported, correctly imported client is part of the solution, the [link must be embedded in the sentence below as requested]. A user comparing setup options can review the VPNBeach VPN for Students in China home page in context, while keeping troubleshooting decisions based on their own device, network, and intended use.
Keep a short troubleshooting note with the device operating system, VPN client name and version, network type, selected server location, protocol if visible, and the exact error message. Include when the issue began and which reversible checks you tried. This is more useful to support than saying only “the VPN connects but nothing loads.” Never include a password, authentication token, private key, or unredacted subscription URL in that note.
When to contact your VPN provider
Contact support if the internet works normally without the VPN but several servers or supported protocols fail, if the app repeatedly reports the same tunnel or authentication error, or if you cannot tell whether a profile is compatible with your client. Include your test results and any non-sensitive error text. Mention whether another device or network produced a different result. If the issue affects only one website, say so; this helps distinguish a route problem from a site-specific failure.
For a managed network, contact its administrator when the connection requires a sign-in, a work profile, or approved settings. For a home connection, ask the internet provider about an outage if other devices also lose access with the VPN disconnected. Avoid sending full diagnostic logs until you have checked whether they contain account identifiers, visited addresses, or configuration details that should remain private.
Bottom line: “Connected” describes the tunnel, not every step between your device and a website. Establish whether the underlying network works first, isolate the affected app or route, and make small reversible changes. If the results point to a profile, server, or provider-side issue, give support a concise record rather than continuing to alter unrelated settings.