VPN Connected but No Internet? 5 Fixes to Get Back Online

VPN Connected but No Internet: What “Connected” Really Means

A VPN client can report “Connected” even when websites and apps cannot reach the internet. The status usually confirms that the client established a tunnel or control connection; it does not prove that every part of the traffic path is working. The selected server may be reachable while DNS requests fail, the operating system may still be using an old proxy, or a firewall may block traffic after the tunnel comes up.

Start by separating a VPN problem from an ordinary network outage. Disconnect the VPN and open a familiar website. If it still does not load, the issue is probably with the Wi-Fi, mobile data, router, or internet provider rather than the VPN tunnel. If the internet works without the VPN but stops as soon as you connect, focus on the VPN app, its selected route, DNS, proxy settings, and device permissions.

Also compare more than one app. If a browser fails but another app works, the browser may have its own proxy, secure DNS, or network restrictions. If nothing can connect, a system-wide setting or route is more likely. A page that stays open from an earlier session is not a reliable test; close it or open a fresh page so the device has to create a new connection.

Use the checks below in order, changing one setting at a time. That makes it easier to identify the cause and undo a setting if it makes the connection worse. Avoid repeatedly toggling several VPN modes, DNS options, and firewall controls together: if access returns, you will not know which change fixed it.

Fix 1: Check the Network, Then Try Another Server

First reconnect the device to a known working network. On Wi-Fi, confirm that other devices can browse and that a sign-in page is not waiting in the background. On mobile data, check that data is enabled and that the phone has a usable signal. Public Wi-Fi networks sometimes require an acceptance page before they allow general internet access. Disconnect the VPN, complete any required network sign-in, and then connect again.

Next, change only the VPN server or route. A particular server can be temporarily busy, unavailable from your current network, or incompatible with the service you are trying to reach. Choose another available location that fits the task, wait for the client to show a completed connection, and test a new webpage. If the client offers more than one supported protocol, a different protocol can also help when a network interferes with the current one. Make one change, reconnect, and test before moving on.

Restarting the VPN connection is often more useful than repeatedly refreshing a browser. Disconnect within the client, wait for the status to change, and connect again. If that does not help, fully quit and reopen the client. A device restart may clear a stuck network interface, but try it after the simpler checks so that the restart does not obscure the original cause.

• ✅ Confirm that the internet works while the VPN is disconnected.
• ✅ Complete any Wi-Fi sign-in page before reconnecting.
• ✅ Test another available server or route, changing one option at a time.
• ❌ Do not assume that the server shown as connected is automatically suitable for every app or network.

If one route works and another does not on the same network, the difference points toward route availability or compatibility. If every route fails but the internet works normally without the VPN, continue with the device-level checks instead of cycling through servers indefinitely.

Fix 2: Check DNS and Proxy Settings

DNS translates a site name into an address that devices can connect to. A tunnel may be active while DNS requests are sent to an unreachable resolver, blocked by another app, or handled by settings that conflict with the VPN. The result can look like a complete internet outage even if some connections still work. If a site opens by a saved session but fresh sites do not, or if apps behave differently from one another, DNS is worth checking.

Begin with settings that are easy to reverse. Disconnect and reconnect the VPN so it can apply its DNS configuration again. If the client has a DNS option, return it to the provider’s recommended or automatic setting while troubleshooting. Do not enter a random resolver address simply because it appears in an online guide; resolver behavior depends on the network and the VPN configuration, and an unrelated setting can cause leaks or make access less reliable.

On Windows, open the VPN client’s settings and look for DNS, network protection, or leak-protection options. If the client provides a documented repair or reset for its network adapter, use that rather than manually removing system routes. On Android, review the system’s Private DNS setting. A custom hostname can prevent name lookups from working with some VPN configurations; temporarily set it to Automatic for a test, then restore your preferred setting if it was not the cause. On iPhone, check whether a separate DNS, filtering, or security app is active. Such apps can install network profiles that continue to affect traffic while the VPN is connected.

Then check for a proxy configured outside the VPN app. On Windows, go to the system proxy settings and turn off a manually configured proxy if you do not intentionally use one. Some browsers also have their own proxy or secure DNS settings, so compare with another browser before changing system-wide settings. On Android and iPhone, inspect the current Wi-Fi network’s proxy configuration; it should normally be off unless your network administrator has provided specific proxy details. A proxy left over from a workplace, school, testing tool, or previous setup can send requests to an unreachable address.

When the connection is restored, keep only the DNS and proxy settings you actually need. If changing a setting does not help, put it back before trying the next one. This preserves a clear record of what you tested and avoids leaving the device in a less secure or less predictable configuration.

Fix 3: Run a Short Platform-Specific Test

Use this sequence as a practical test rather than changing several platform settings at once. First disconnect the VPN and confirm that the device has internet access. Next reconnect and test a newly opened page in a second app. If it still fails, follow the steps for your platform below, then reconnect and test again. A device can display an active VPN indicator while a different setting prevents apps from using the tunnel.

Windows

Open the VPN client and check that it has not paused traffic or selected a mode that excludes the app you are testing. If the client supports rule-based routing, the browser or other app may be assigned to a direct connection instead of the VPN. For diagnosis, temporarily use the client’s broadest supported routing mode, if available, and test a browser. If that works, review the routing rules rather than treating the result as a server failure.

Check Windows proxy settings for an unexpected manual server, and close other proxy or VPN clients that might compete for the same network settings. If the client offers a network repair function, follow its instructions and grant the requested administrator permission only when you trust the application. Do not disable the Windows firewall as a first step. If a managed work or school device is involved, its administrator may control firewall rules or network adapters, so consult the applicable support team before changing them.

Android

Open the system VPN settings and confirm which VPN app is active. Android generally allows one active VPN connection at a time, so another privacy, filtering, or work-profile app may interrupt the connection. Check whether Always-on VPN or “block connections without VPN” is enabled. Those controls can intentionally block traffic when the VPN is unavailable; during diagnosis, change them only if you understand the security effect and can restore the original setting.

Review Private DNS and the Wi-Fi network’s proxy setting as described above. Also check whether the VPN app is restricted by battery optimization or background-data controls. On some devices, aggressive power management can suspend an app or its network activity after the screen turns off. Temporarily allow the VPN app to run in the background, reconnect, and test while the app is open. If that resolves the issue, adjust only the restriction that caused the interruption.

iPhone and iPad

Open the VPN app and confirm its connection status, then check the device’s VPN configuration in Settings. If a device-management profile, content filter, or another security app is installed, it may control network traffic alongside the VPN. Avoid deleting profiles you do not recognize, especially on a managed device. Ask the organization that supplied the device or profile to confirm whether it is expected.

Test once on Wi-Fi and once on mobile data, where available. If the VPN works on one network but not the other, the difference helps narrow the cause to that network’s filtering, proxy, or access requirements. If the problem began immediately after an iOS update or a change in another network app, disconnect and reconnect the VPN, then restart the device before removing or reinstalling profiles.

For a structured comparison of supported platforms, setup options, and service details, see VPNXW Best VPN for China. Regardless of platform, make sure you are testing the app that actually fails: a browser test cannot confirm that every game, meeting app, or background service follows the same route.

Fix 4: Review App Permissions and Conflicting Tools

A VPN depends on operating-system permission to create or manage a network connection. If permission was denied, revoked, or interrupted during setup, the client may appear open without successfully routing app traffic. Open the VPN app’s connection settings and follow its prompts to grant the required system permission. On mobile devices, approving the system VPN request is different from merely allowing notifications; notifications are not what carries your internet traffic.

Look for other software that can change network behavior: another VPN, a proxy utility, a firewall, an antivirus web shield, parental controls, DNS filtering, or a corporate security agent. These tools can be legitimate and useful, but two products trying to intercept traffic at once can produce a connection that looks active while requests fail. Close or pause only the tool you recognize and can safely control, then test again. Do not remove an employer’s security software or bypass organization policy.

On Windows, check that the VPN client is not blocked by a firewall rule and that it has permission to run its network component. If a firewall prompt appears, verify the publisher and application before allowing access. On Android and iPhone, confirm that the VPN profile belongs to the client you installed and that the app has not been restricted by background-data or device-management controls. Reinstalling should be a later step, not the first one, because it may remove configuration that would help diagnose the problem.

If the problem began after an update, record which app or operating-system change happened immediately beforehand. Update the VPN client through its normal distribution channel, restart the device, and test with the default client settings. Avoid installing multiple clients at once as a comparison method; each may add its own profile, routes, or DNS behavior and make the original issue harder to isolate.

Fix 5: Respond to Network Changes and Escalate Carefully

Connections can fail after moving between Wi-Fi and mobile data, waking a device from sleep, changing routers, or joining a network with a sign-in portal. The old tunnel may not recover cleanly after the underlying network changes. Disconnect the VPN, confirm that the new network can reach the internet, and reconnect. If the client has an automatic reconnect option, use its documented setting; do not assume that leaving a stale connection active will make it recover by itself.

When a VPN works on one network but not another, note the difference before changing more settings. A hotel or workplace network may restrict certain connection methods, while a home router may have its own DNS or parental-control configuration. If permitted, compare with another trusted network. If the same server works there, the evidence points toward the original network rather than a general device failure. On managed networks, ask the administrator whether VPN traffic is permitted instead of trying to circumvent their controls.

If nothing has worked, collect useful details before contacting support: the device and operating-system version, VPN client version, whether the internet works when disconnected, which networks you tested, whether every app fails, and which route or protocol changes you tried. Include the approximate time the issue began and any recent system or security-app changes. Do not send passwords, authentication codes, or private browsing contents. A connection log can help, but review it for personal details before sharing it.

• ✅ Restore any temporary DNS, proxy, or security setting that did not help.
• ✅ Keep notes on the network, app, and route used for each test.
• ✅ Use the VPN client’s documented repair steps before manually changing system routes.
• ❌ Do not leave the firewall disabled or remove an unknown device-management profile to force a connection.

Once access returns, repeat the same test that failed before and confirm that the result is consistent. Then re-enable any security control you temporarily changed and verify that the VPN still works. A single successful page load is useful evidence, but it is better to confirm the affected app and the network conditions that matter to your normal use.