If your VPN connects over mobile data but not Wi-Fi, the VPN account and profile may be working while something about the Wi-Fi path is getting in the way. The difference could be the router, DNS resolution, a captive portal, a network handoff, or a permission or firewall setting on the device. Start by confirming that ordinary internet access works on Wi-Fi, then change one thing at a time. This makes it easier to identify the cause without deleting a working profile or changing several settings at once.

Identify where the connection fails

First, turn off the VPN and open a few familiar websites while connected to the Wi-Fi network. If they do not load, troubleshoot the Wi-Fi connection itself before changing VPN settings. If they load normally, reconnect the VPN and note what happens: does the client stay on “Connecting,” show an error, report “Connected” while apps cannot load, or connect but fail only for certain destinations? Those differences point to different parts of the connection.

Next, test the same device on mobile data, then return to Wi-Fi and retry without changing the VPN profile. If the VPN works on mobile data but consistently fails on one Wi-Fi network, the contrast is useful evidence, not proof of a single cause. The Wi-Fi router or network may treat VPN traffic differently, but the device may also switch DNS servers, apply different firewall rules, or retain a stale network route when changing connections.

  • ✅ Confirm that ordinary browsing works on Wi-Fi with the VPN disconnected.
  • ✅ Record the exact client error or connection state before changing settings.
  • ✅ Compare Wi-Fi and mobile data using the same device and VPN profile.
  • ❌ Avoid deleting the profile or resetting all network settings as a first step.

If the Wi-Fi network has a sign-in page, such as a hotel, campus, or public hotspot, disconnect the VPN and complete that page first. A captive portal can block access until you accept its terms or sign in. Once regular browsing works, reconnect the VPN. If the sign-in page does not appear, open a plain, non-sensitive website or use the network’s official instructions to trigger it; do not enter account details into a page you cannot verify.

Check the router and Wi-Fi network

On a home network, restart the router using its normal controls, then reconnect the device and test again. A restart can clear a temporary router state, but it will not correct a persistent policy or configuration issue. If several devices fail to connect their VPNs on the same Wi-Fi, while ordinary browsing still works, focus on the router or network administrator rather than reinstalling every client.

Check whether the router has parental controls, security filters, guest-network restrictions, or settings that limit unfamiliar encrypted connections. These features vary by manufacturer, so look for the actual rule or event in the router’s management interface instead of disabling security protections broadly. If you are on a managed workplace, school, or public network, ask its administrator whether VPN connections are permitted. Do not try to bypass an organization’s access policy.

Some routers expose separate options for IPv6, DNS, firewall behavior, or traffic inspection. If you suspect one of these, change only a setting you understand and make a note of its original value so you can restore it. Avoid forwarding ports or placing a device in a router’s DMZ merely to make a client connect: those changes can expose services and are not a general VPN fix. If a router setting appears to be involved, its documentation or administrator is a safer source than guessing at values.

For a useful comparison, try another trusted Wi-Fi network if one is available. A VPN that works on a second Wi-Fi network but not the first suggests that the issue may be specific to the original router or its provider. If the same device fails on multiple Wi-Fi networks but succeeds on mobile data, continue with device settings and the client. In either case, a China VPN Download page can help you find the service’s official client or setup guidance rather than relying on an unrelated app or configuration file.

Check DNS and network handoffs

DNS translates a domain name into an address. A DNS problem can prevent a client from finding a VPN server before a tunnel is established, or it can make websites appear unavailable after connection. DNS is only one possibility: if the VPN client cannot reach its server at all, changing a browser’s DNS setting may have no effect. First compare the client’s status and try more than one ordinary destination after connecting.

Look for custom DNS, encrypted DNS, filtering, or security apps that apply only on Wi-Fi. Depending on the operating system and client, DNS may be controlled by the VPN, the device, the router, or a separate filtering application. Temporarily pause a personal filtering feature only if you understand what it does and can safely restore it. Do not install an unknown DNS profile or enter an address from an untrusted troubleshooting post.

Network handoffs can also leave a client using a route or DNS state from the previous connection. Fully disconnect the VPN, switch Wi-Fi off and back on, wait until the device has internet access, and then reconnect. If you moved between mobile data and Wi-Fi while the tunnel was active, quit and reopen the client before testing again. A device reboot can be a later diagnostic step if a clean reconnect does not help, but it should not replace checking the actual error message.

Key takeaway: If the tunnel says “Connected” but browsing fails, investigate DNS, traffic rules, and stale network state; if it never reaches the connected state, focus first on server reachability, router restrictions, and client permissions.

Use the checks that match your device

iPhone and iPad

Open the VPN client and disconnect it before changing networks. Check that iOS has granted the VPN configuration requested by the client; if the system prompts you to add or approve a VPN configuration, make sure the request comes from the app you intended to use. Then reconnect from the client and inspect its status. Deleting a VPN configuration from Settings without first understanding which client created it can remove a working setup, so prefer the app’s own disconnect and repair steps.

If the issue began after switching between Wi-Fi and mobile data, close and reopen the client, reconnect to Wi-Fi, and try again. Check whether an iOS content filter, DNS profile, or another network utility is active, since it may affect Wi-Fi traffic differently. If you use a managed device, a configuration profile may be controlled by an organization; contact its administrator rather than removing it. When the VPN connects but only one app fails, check that app’s own network or proxy settings before resetting the phone’s network configuration.

Android devices

In the VPN client, confirm the selected profile and route, then reconnect after Wi-Fi is fully online. Android’s system VPN settings may show whether an app is connected and may offer “Always-on VPN” or “Block connections without VPN” controls. These options can change what happens when the tunnel drops or the network changes. If you use them, understand their effect before toggling them; a blocked connection can look like Wi-Fi itself has stopped working.

Check whether Android Private DNS, a security app, or a battery-management setting is interfering with the client. Private DNS may affect name resolution, while aggressive background restrictions can interrupt a client during a network transition. Prefer the client’s recommended battery or background setting, if needed, and avoid granting unrelated permissions. If the client reports that its VPN permission is missing, reconnect through the app and approve the system request rather than creating a different VPN entry by hand.

Windows

On Windows, check whether another VPN, proxy, firewall, or endpoint-security application is active. Two programs trying to control routing at once can cause connection failures or leave traffic on an unexpected path. Disconnect other VPN clients, but do not disable workplace security software without authorization. If the client displays a permission or adapter error, close and reopen it with the normal privileges recommended by its documentation; avoid running unfamiliar programs as administrator.

Verify that Windows has internet access over Wi-Fi with the VPN disconnected, and check the system proxy settings if you previously configured one. A stale adapter or route can sometimes persist after switching networks; disconnecting the VPN, reconnecting Wi-Fi, and reopening the client is a sensible first test. If the failure began after a firewall or antivirus change, review that product’s log or allow-list instructions instead of turning off the firewall entirely.

Try a different server or protocol carefully

If Wi-Fi works normally and the device permissions look correct, select another available server in the client and test again. A single server or route may be temporarily unreachable from a particular network. Keep the test controlled: change the server first, note the result, and only then consider another protocol. If the client offers automatic selection, compare its result with a manually selected alternative rather than repeatedly switching without recording what changed.

Protocols are not interchangeable labels. Shadowsocks, VMess, Trojan, Hysteria2, and WireGuard are examples of different protocols or protocol implementations; the client and service must support the chosen one, and the configuration must match. A protocol that works on mobile data may still be blocked or disrupted on a particular Wi-Fi network. Where the client offers supported alternatives, follow the provider’s instructions and test one option at a time. Do not edit subscription data or copy protocol parameters from an unrelated source.

Use the pattern of the failure to choose the next check; these clues are not a diagnosis by themselves.
What you observe Likely area to inspect Next useful test
Wi-Fi has no internet even without the VPN Router, access point, captive portal, or internet service Restore ordinary Wi-Fi access before testing the tunnel
VPN fails only on one Wi-Fi network Router policy, filtering, DNS, or network restrictions Compare with another permitted Wi-Fi network
VPN says connected but websites do not load DNS, routing rules, network handoff, or another filter Reconnect cleanly and test more than one destination
Only one app fails after connection App-specific proxy settings, traffic rules, or app connectivity Compare that app with a browser and review its settings
Several devices fail on the same Wi-Fi Router configuration or network administrator policy Review router controls or ask the network administrator

Some clients expose advanced connection options such as MTU or IPv6 handling. These can matter on particular networks, but changing them without a client-specific reason can introduce new problems. Use an option only when the client’s documentation or support guidance identifies it as relevant. Save the original setting, test one change, and restore it if there is no clear improvement.

Know when to contact support

If the VPN still fails, gather information before contacting the provider or network administrator. Include the device and operating system, client name and version, whether ordinary Wi-Fi browsing works, whether mobile data still works, the exact client error, and whether the issue occurs on one or multiple Wi-Fi networks. Mention any recent change to the router, DNS, firewall, client, or operating system. This gives support a reproducible comparison rather than a vague report that the VPN is broken.

Do not send your password, complete subscription link, private keys, or other account credentials in a public forum. If support requests diagnostic logs, use its official channel and check whether the logs contain identifiers or configuration details. Avoid posting screenshots that reveal account information. If the problem is limited to a managed Wi-Fi network, its administrator may be the only person able to confirm its restrictions.

As a final clean test, update the client through its official source, refresh the configuration only through the provider’s official process, and reconnect after Wi-Fi is stable. Reinstalling may help if the client installation is damaged, but it can also remove local settings; make sure you know how to restore the supported configuration first. A device-wide network reset should be a last resort because it may remove saved Wi-Fi networks and other network settings.

Frequently asked questions

Why does the VPN work on mobile data but not Wi-Fi?

The two connections can use different routers, DNS resolvers, firewall rules, and routes to the VPN server. The Wi-Fi network may also require a captive-portal sign-in or restrict VPN traffic. The contrast narrows the investigation, but it does not by itself identify the exact cause.

Why does Wi-Fi work while the VPN stays on “Connecting”?

Ordinary browsing and a VPN tunnel use different connection paths. Check for a captive portal, router restrictions, a client permission error, or a server route that cannot be reached from that network. Try another permitted Wi-Fi network and, if supported, another server before changing advanced settings.

What if the VPN says “Connected” but there is no internet?

Disconnect and reconnect after Wi-Fi is fully online. Then check DNS or filtering settings, traffic rules, and whether another VPN or proxy is active. Compare more than one app or destination: if only one app is affected, its settings may be the issue rather than the tunnel itself.

Should I disable my router firewall to test the VPN?

No. Disabling the firewall broadly can reduce network security and is not a safe general troubleshooting step. Review specific router logs or documented controls, ask the network administrator, or compare with another trusted network. Restore any temporary diagnostic change when testing is complete.