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

A VPN client can report “connected” while websites, apps, or all internet traffic remain unavailable. The connection status usually confirms that a tunnel was established; it does not prove that your device has working internet access, that DNS can resolve website names, or that the app you are testing is using the tunnel correctly. Work through the checks below in order, changing one thing at a time so you can identify the cause rather than masking it.

Start with the basic connection and the VPN mode

Before changing routes or network settings, separate a local internet problem from a VPN problem. Disconnect the VPN temporarily and try to open a familiar website or app. If nothing works without the VPN either, the tunnel is unlikely to be the root cause. Check whether Wi-Fi or mobile data is actually connected, whether the router has internet access, and whether your device is in airplane mode. If you are on a hotel, airport, campus, or café network, you may also need to complete its sign-in page before other traffic can pass.

When a public Wi-Fi network uses a captive portal, connect to the network first, open a browser, and follow the network’s own access instructions. Some networks intercept the first web request and display a login page; a VPN tunnel can prevent that page from appearing. Disconnect the VPN only long enough to complete the authorized sign-in, then reconnect and test again. If the network asks you to accept terms or enter a room or access code, follow the venue’s instructions rather than trying to work around its access controls.

If internet access works while disconnected, reconnect the VPN and check the client’s selected mode. A rule-based mode may send some apps directly while routing others through the proxy; a global mode typically routes a wider range of traffic through it. Names and behavior vary by client, so read the mode description in the app instead of assuming that two clients use identical labels. Test with a browser or app that should follow the selected route. A “connected” indicator can coexist with a configuration that sends the app you are testing outside the tunnel.

✅ Confirm that the underlying Wi-Fi or mobile connection works before diagnosing the VPN.
✅ Complete any legitimate captive-portal sign-in before reconnecting.
✅ Check whether the selected proxy mode includes the app that cannot load.
❌ Don’t change several network settings at once; it becomes harder to tell which change helped.

Six practical fixes to try, one at a time

Once you have confirmed that ordinary internet access works without the VPN, use these fixes in sequence. After each one, reconnect if needed and test the same site or app. If the problem disappears, stop there and note what changed; there is no benefit in adjusting unrelated settings.

Reconnect cleanly. Disconnect from the current route inside the VPN client, wait for the client to show that it has disconnected, and connect again. If that does not help, close and reopen the client. On a phone or computer, check that the operating system still shows the VPN as active after reconnecting. A stale network session can leave the app displaying an old connection state even when traffic is no longer passing correctly.
Test the route with more than one destination. Try a simple webpage and a second familiar service. If one destination fails but others load, the issue may be specific to that site, app, account, or content delivery path rather than a complete loss of internet access. If nothing loads through the VPN, continue with the following checks. Avoid repeatedly refreshing a page while diagnosing; cached errors and automatic retries can make results confusing.
Check DNS behavior. DNS translates a name such as a website address into the network address a device needs to connect. If a page fails by its usual name but other connections appear to work, name resolution may be involved. First reconnect the VPN and retry the page. Then, if your client provides a documented DNS option, restore its default setting or choose another option the provider supports. Avoid copying DNS addresses from random posts or changing system DNS without understanding whether the setting applies to the VPN, the local network, or both.
Look for a conflicting proxy or VPN. Running two VPN clients, a separate proxy app, or a manually configured system proxy at the same time can create competing routes. Disconnect the other VPN or proxy, then check the operating system’s network settings for a proxy you intentionally configured in the past. Disable only settings you recognize and can restore. Some work or school devices require a managed proxy, so do not remove organization-controlled settings; ask the administrator if the device is managed.
Try a different server or route. Disconnect before switching, select another available route, and reconnect. A route can be temporarily unsuitable because of congestion, maintenance, or the way a particular local network reaches it. A different country or city is not automatically better: choose a route that fits the service you need and the locations available in your account. If the client provides route status or connection messages, record them rather than relying only on a color or latency indicator.
Change protocol only when the client offers a supported choice. If another route still fails, try an alternative protocol in the client’s own settings, then reconnect and test again. Protocols differ in how they establish and transport a connection, and a network may handle one differently from another. Don’t paste unfamiliar configuration text into the client or assume a protocol name guarantees compatibility. If the client does not expose a protocol choice, leave the setting alone and ask support which options apply to your subscription and device.

These checks help distinguish a basic connection failure from a DNS problem, a conflicting proxy, or a route-specific issue. They do not guarantee that every application will work: an app may use its own network rules, require a separate login, or block a connection for reasons unrelated to your VPN. For a broader overview of the service and supported access options, see VPNJoin VPN That Works in China.

In short: Verify the local connection first, then test the client mode, DNS, proxy conflicts, routes, and supported protocols in that order. Make one change at a time and retest the same destination.

Check device permissions, firewall rules, and network changes

If the checks above do not restore access, consider whether anything changed shortly before the problem started. Operating-system updates, client updates, a new security app, a switch from Wi-Fi to mobile data, or a change to a router can affect how traffic is routed. Note what changed and when. If the issue began immediately after installing another network tool, test with that tool disconnected rather than removing it outright.

VPN clients may need permission to add or manage a VPN connection, create a virtual network interface, or apply routing and DNS settings. If the operating system displayed a permission prompt, confirm that you approved the legitimate request from the client you installed. On mobile devices, check the system’s VPN settings to see whether the expected profile is enabled and whether another profile is active. On desktop systems, look for the VPN’s own connection status and any operating-system notification that says the network configuration needs attention.

A firewall or endpoint security product can also block the client’s connection or its traffic after the tunnel is established. Do not turn off your firewall or antivirus as a general troubleshooting step. Instead, review its recent alerts and use the product’s documented process to verify whether the VPN client was blocked. On a managed work or school device, contact the administrator before changing policy. Security tools can be enforcing rules that are required by the organization, and bypassing them may expose the device or violate its use policy.

Check for device-specific conditions as well. A phone may switch between Wi-Fi and mobile data while the client is reconnecting; a laptop may wake from sleep with an old connection state. Try toggling the affected network connection off and back on, then reconnect through the client. If another device on the same Wi-Fi can reach the internet but this device cannot, focus on its client, permissions, local proxy, and security settings. If several devices lose access at the same time, investigate the router or upstream network before changing each device separately.

Keep a note of the exact test you performed. “The internet is broken” is difficult to diagnose, while “Wi-Fi works without the VPN; after connecting, two unrelated websites fail; switching routes changes nothing” narrows the possibilities. Use plain descriptions and avoid sharing passwords, full subscription links, authentication tokens, or private configuration files when asking for help.

Identify where the failure occurs

Compare behavior in a small, repeatable set of conditions. First test the device on its current network with the VPN disconnected. Then connect the VPN and test the same destination in the same app. If practical, try another app and another network you are authorized to use, such as your own mobile connection instead of the current Wi-Fi. You are looking for a pattern, not a speed score: does the failure affect one app, one route, one network, or every connection through the VPN?

If internet access fails both with and without the VPN, check the local network, router, mobile connection, or captive portal first.
If internet access works without the VPN but fails on every VPN route, record the client status and move on to device settings or support.
If another route works, the original route may be unsuitable at that time; note which route failed and which one connected successfully.
If only one website or app fails, check that service’s own status, sign-in state, and app-specific network settings before changing system-wide configuration.
If the issue appears only on one device, compare its VPN permissions and proxy settings with a device that works, without copying private credentials.

For a controlled test, avoid changing the browser, route, protocol, and Wi-Fi network simultaneously. Keep the same destination and app while testing one variable. If you need to switch networks, record that change and repeat the same test after the VPN reconnects. A connection indicator, a route label, or a single successful page load is useful evidence, but none alone proves that all applications are using the VPN as intended.

Some networks restrict VPN traffic or interfere with particular connection methods. If the VPN works on one network but not another, that difference is useful information; it does not by itself show that the client is misconfigured. Use only networks and services you are authorized to access, and do not attempt to bypass an organization’s network controls. On a company or campus connection, ask its administrator whether VPN use is allowed and whether a required proxy or device profile must remain enabled.

What to send support if the problem continues

If you have tried the safe checks and still cannot get online through the VPN, send support a concise description that makes the problem reproducible. Include your device platform and operating-system version, the client name and version if visible, the route or server label you selected, the connection mode, and the time the issue occurred with your time zone. State whether ordinary internet access works with the VPN disconnected, whether the problem affects all apps or only some, and what happened after trying another route or supported protocol.

Include the exact wording of any client or operating-system error. If you can provide a screenshot, inspect it first and conceal account details, email or username information, authentication tokens, QR codes, and the full subscription URL. A subscription link can grant access to your configuration, so treat it as a secret. Do not post it in a public forum or send it to an unverified account. If support requests diagnostic logs, use the client’s official export function where available and review the contents for personal information before sharing.

A useful report separates what you observed from what you suspect. For example: “Wi-Fi works when the VPN is disconnected. With the VPN connected, the browser and another app cannot load pages. Reconnecting did not help; a different route has the same result. The client displays this message: …” This gives support a clear starting point without claiming that the cause is DNS or the server before it has been checked.

Do not uninstall security software, reset every network setting, or install unofficial client builds just to produce more troubleshooting data. Such changes can remove useful evidence or create new problems. If the device is managed, ask its administrator before altering network profiles. If support confirms a specific setting should be changed, follow the instructions for your operating system and make a note of the original value so you can restore it if needed.

Bottom line: A successful VPN handshake and working internet are separate checks. Establish that the local network works, test one change at a time, and give support the device, route, mode, error message, and exact results—never your password or full subscription link.