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

A VPN app can show “Connected” while websites, apps, or even basic network checks fail. The status usually confirms that the client established a tunnel; it does not prove that your device has working DNS, that every app is routed through the tunnel, or that the VPN server can reach the destination you need. Work through the checks below in order, changing one thing at a time. That makes it easier to identify whether the cause is your local Wi-Fi or mobile connection, a server, a DNS setting, a conflicting proxy, or an app permission.

Identify where the connection fails

First establish whether the problem affects the whole device or only one destination. Try opening a familiar, ordinary website in a browser, then test a second site or app that does not depend on the same account or service. If only one app fails, its own sign-in state, network policy, or proxy configuration may be responsible. If nothing loads, investigate the device’s route and DNS before changing settings inside that app.

Next compare the connection with the VPN off and on. Disconnect using the client’s normal control, wait for the device to return to its regular network, and try the same test. If browsing fails both ways, the issue may be the Wi-Fi, mobile data, router, or an upstream outage rather than the VPN tunnel. If the internet works without the VPN but stops as soon as it connects, concentrate on server selection, DNS, proxy conflicts, and client permissions.

On public Wi-Fi, look for a captive portal: a sign-in or terms page that must be completed before ordinary internet access is available. Disconnect the VPN temporarily, open the network’s sign-in page, and complete the required steps according to the venue’s rules. Then reconnect and test again. A portal may not appear while a VPN is active, so a connected indicator can coexist with a network that has not yet granted internet access.

Also check whether the problem is limited to one network. If it is safe and available, compare Wi-Fi with mobile data, or compare the current Wi-Fi with another trusted network. Avoid testing sensitive work or personal accounts on a public connection just to diagnose the issue. The result helps separate a local router or provider problem from a setting that follows the device wherever it connects.

Seven checks to restore access

Use these checks in sequence rather than changing several options at once. After each change, reconnect and repeat the same simple browsing test. If access returns, note which change helped; that information is useful if the problem comes back or you need support.

1. Confirm the local network is online. Disconnect the VPN briefly and check whether other devices on the same Wi-Fi can load websites. If they cannot, restart the router only if you are authorized to manage it, or contact the network administrator or internet provider. On mobile data, confirm that data is enabled and that the carrier connection itself is available.
2. Reconnect the tunnel cleanly. Disconnect from the VPN in the client, wait until it reports that it is disconnected, then connect again. If the status is stuck or the client does not respond, fully quit and reopen it. On a phone, force-closing the app is different from removing its VPN permission or deleting its configuration; avoid resetting those items unless you understand the consequences.
3. Try another server or region. A particular server may be temporarily unreachable from your network, under maintenance, or unable to reach a destination. Select a different available server in the client, reconnect, and repeat the same test. Do not judge the result from the connection animation alone: check whether a browser and the affected app can actually load content.
4. Check DNS behavior. DNS translates a website name into an address. A tunnel can connect while name lookups fail because of stale DNS data, a custom resolver, or a mismatch between the client and device settings. Temporarily restore DNS to the operating system or client default if you previously entered custom DNS values, reconnect, and test a few unrelated domain names. Keep a record of existing settings before changing them.
5. Remove competing proxy settings. Quit other VPN or proxy clients before testing. Check whether a system proxy, browser proxy extension, local filtering application, or security tool is still routing traffic through a different endpoint. Two tools can compete over the system route or proxy configuration even when only one appears active. Change only settings you recognize, and restore managed settings rather than bypassing workplace or school controls.
6. Review permissions and network controls. Confirm that the VPN app is allowed to use the network and that its VPN profile or system extension remains enabled. A firewall, endpoint-security product, parental-control tool, or device-management policy may block the client or its traffic. Do not turn off security protection broadly to test a connection; instead, check the security tool’s logs or ask the administrator to review the relevant rule.
7. Update or switch the connection protocol. If the client offers more than one supported protocol, try another option using the client’s documented settings, then reconnect and test. Networks can treat protocols differently, and a protocol that works on one Wi-Fi may be blocked or disrupted on another. Update the client from its trusted source if an update is available, but do not paste an unfamiliar configuration or subscription into a third-party app to see whether it works.

These checks apply across the supported Windows, macOS, iOS, Android, and Linux platforms, but the control names differ by operating-system version and client. For example, a phone may label the VPN profile under network settings, while a desktop client may manage its own virtual adapter. If the device is managed by an employer, school, or family administrator, ask before changing a profile, firewall rule, DNS setting, or proxy configuration.

A safe reconnect and test routine

When a connection is stuck, use a small, repeatable procedure instead of deleting profiles or resetting the whole device. The same routine makes troubleshooting clearer whether you are on a phone, laptop, or desktop. If you are helping someone else, ask them to describe the exact client status and test results rather than sending account credentials or a full subscription URL.

1. Record the starting state. Note the operating system, client name and version, network type, selected server, and the exact message shown. Record whether the same device can browse when the VPN is disconnected. Do not include passwords, authentication tokens, or private subscription links in notes shared with others.
2. Close competing network tools. Quit any other VPN client, proxy application, or browser extension that you recognize as changing network traffic. If the device is managed or a tool’s purpose is unclear, pause and ask its administrator rather than removing it.
3. Reconnect once, then test consistently. Connect to the VPN, wait for the client to show an established connection, and open one ordinary website in a private or clean browser session. Then test the app that originally failed. Testing the same destinations before and after a change helps distinguish a genuine improvement from a temporary website or account issue.
4. Change one variable at a time. If the test fails, switch to one other available server and repeat. If that does not help, restore DNS to its default or change the client’s protocol according to its documentation, testing after each individual change. Keep a note of the original value so you can undo the change.
5. Restore anything that did not help. Return custom DNS, proxy, or routing settings to the values you recorded. Leave system security and device-management controls enabled. If a reset or reinstallation appears necessary, first check the client’s documentation and make sure you can retrieve the correct configuration again.

If you are comparing service options while troubleshooting, the VPNNQ VPN for China Travel overview can help you understand the available service context; it does not replace testing the current device and network. For the actual diagnosis, rely on what your client reports and on repeatable browser and app tests, not on a general claim that a particular server or protocol always works.

Some devices offer an “always-on” VPN or a setting that blocks traffic whenever the VPN is disconnected. Such a feature can be useful for privacy, but it may make a failed tunnel look like a complete internet outage. Check whether the option is enabled and understand its purpose before changing it. If it is controlled by an organization, do not disable it without approval.

Device-specific settings to review

Once the basic checks are complete, look at the settings most likely to differ by platform. The aim is to confirm that the client has permission to create and use its VPN connection, not to grant unrelated access or weaken the device’s protections.

• ✅ Windows: Check that the client is allowed through relevant firewall rules and that no second VPN or manually configured proxy is active. If a virtual network adapter reports an error, restart the client and review its documentation before removing or reinstalling the adapter.
• ✅ macOS: Confirm that any required network extension or VPN configuration is approved in system settings. A security prompt or organization policy can prevent a client component from operating even if the app itself opens normally.
• ✅ iOS: Verify that the VPN configuration remains installed and that the client is permitted to establish the connection. If the device uses a content filter or managed profile, check whether it affects the same traffic.
• ✅ Android: Review the VPN permission and any always-on or block-without-VPN option. Battery restrictions can affect background reconnection in some configurations, but changing battery settings will not fix a server or DNS failure.
• ✅ Linux: Check whether the desktop network manager, a separate VPN service, or a manually configured proxy is controlling the route. Network-management tools vary by distribution, so use the documentation for your own setup rather than applying commands from an unrelated guide.

Private DNS on Android, custom DNS on a computer, browser-level secure DNS, and DNS settings supplied by a VPN client are separate layers. Changing one does not necessarily change the others. If a browser fails while a different app works, inspect browser proxy and secure-DNS settings; if every app fails, focus on the system route, client, and network. Avoid disabling IPv6 or changing routing tables as a first response: those changes can create new problems and are not a universal fix.

When to contact support

If the connection still has no internet after testing the local network, reconnecting, trying another server, and reviewing DNS and proxy settings, contact support through the service’s official channel. A useful report describes the failure in a way that can be reproduced: the operating system and version, client name and version, approximate time and time zone, network type, selected server, protocol if visible, and whether browsing works with the VPN disconnected. Include the exact error text when there is one.

Explain what you already tested and the result of each test. For example, say whether another server changed anything, whether the same device works on a different network, and whether the issue affects all apps or only one. If you changed DNS or proxy settings, state the original and current values without exposing account secrets. A screenshot can help show a status message, but crop or cover usernames, subscription links, IP addresses, and any other information you do not want to share.

Do not send a password, one-time login code, or full subscription URL in a public forum or an ordinary screenshot. Support should not need you to publish those details to diagnose a route or client problem. If you suspect that a private link has been exposed, ask through the official support channel what account-side steps are available. Keep the client and device security protections enabled while waiting for a response.

Finally, distinguish a connection problem from a destination-specific restriction or outage. If other sites work through the VPN but one service does not, the tunnel may be functioning while that service, its account, or its own network policy is the limiting factor. Retest later, check the service’s official status information, and avoid repeatedly switching settings without a clear reason. A careful report with a reproducible test is more useful than simply saying “the VPN is connected but the internet is broken.”