If your VPN connects over mobile data but fails on Wi-Fi, the difference between the two networks is a useful clue. It points toward something in the Wi-Fi path—such as a router setting, DNS response, captive portal, or network policy—but it does not prove that the router is the cause. The VPN app may also be using different settings, servers, or connection protocols on each network.
Start by narrowing down the failure before changing settings. Check whether Wi-Fi works normally with the VPN disconnected, whether the VPN can connect but apps cannot load, and whether the problem happens on one Wi-Fi network or several. These distinctions help you choose a targeted test instead of changing multiple settings at once and losing track of what helped.
Identify where the connection fails
With the VPN disconnected, open a few ordinary websites or apps over Wi-Fi. If they do not load, troubleshoot the Wi-Fi connection first: reconnect to the network, check whether other devices have internet access, and complete any sign-in page that appears. A VPN cannot repair a Wi-Fi network that has no usable internet connection.
If ordinary browsing works, connect the VPN and observe exactly what happens. “Not working” can describe several different problems: the client never completes its connection, the client says connected but websites do not open, only some apps fail, or the connection drops after working briefly. Record the error message and whether the issue begins immediately or after a period of use. Those details can distinguish a blocked connection attempt from a DNS or traffic-routing problem.
| What you observe | Check first | A low-risk test |
|---|---|---|
| Wi-Fi has no internet even without the VPN | Router connection, sign-in page, or internet service | Reconnect to Wi-Fi and test another device |
| VPN stays on Connecting | Network restrictions, server reachability, and protocol settings | Try another available server or protocol setting |
| VPN says Connected, but most sites fail | DNS, routing, or conflicting proxy settings | Disconnect and reconnect, then test a different app or site |
| Some apps work while others do not | Per-app routing, split tunneling, and app-specific DNS | Check whether the affected app is excluded from the VPN |
| It works briefly, then disconnects | Wi-Fi roaming, sleep settings, and router stability | Keep the device near the router and test without moving |
Compare the same device on mobile data and Wi-Fi, then compare another device on the same Wi-Fi if possible. If every device has the same VPN issue on that network, the router or network policy becomes more likely. If just one device is affected, focus on its VPN client, operating-system settings, or other network software. When deciding which service and setup to use, VPN for China is one place to review the available service information; whichever option you use, first confirm that its client and connection settings match your device.
Check router and network restrictions
Routers and managed Wi-Fi networks can treat VPN traffic differently from ordinary web browsing. A router may have firewall rules, parental controls, access-control settings, or security features that interfere with a particular connection method. Public, workplace, school, hotel, and apartment Wi-Fi may also restrict some traffic. The fact that a VPN works on mobile data but not on one Wi-Fi network is consistent with these restrictions, though it is not proof of them.
First, rule out a captive portal. Disconnect the VPN, open a browser, and check whether the Wi-Fi requires you to accept terms or sign in. Complete that step before connecting the VPN. Some sign-in pages do not appear while a VPN is trying to route traffic, so repeatedly reconnecting the VPN can leave the device stuck without making the required network authorization.
Next, restart the device’s Wi-Fi connection and, if you manage the router, restart the router using its normal controls. Do not reset the router to factory settings as an early troubleshooting step: that can erase the network name, password, and provider configuration. If you do not manage the network, avoid trying to bypass its administrator’s policies. Ask the network owner whether VPN connections are permitted and whether a supported alternative network is available.
- ✅ Confirm ordinary internet access with the VPN disconnected
- ✅ Complete a Wi-Fi sign-in or captive-portal step before reconnecting
- ✅ Test another Wi-Fi network to see whether the issue follows the router
- ❌ Do not disable the router firewall or security features without understanding the consequences
- ❌ Do not change several router settings at once; make one reversible change and test it
If you administer the router, review whether it has an explicit VPN, firewall, or traffic-filtering option that was recently changed. Names and behavior vary by manufacturer, so consult the router’s own documentation rather than assuming a particular menu label has the same meaning everywhere. If changing a setting is necessary, note its original value first and restore it if the test does not help. On a managed network, report the symptom and the client’s error message to the administrator instead of modifying network equipment yourself.
Rule out DNS and device settings
DNS translates a domain name into the network address an app needs. If the VPN establishes a tunnel but the device cannot resolve names correctly, the client may show “Connected” while websites and apps appear offline. DNS behavior can differ between Wi-Fi and mobile data because the networks may supply different DNS settings, and a device-level private DNS or custom resolver can add another layer.
Begin with simple, reversible checks. Disconnect and reconnect to Wi-Fi, then reconnect the VPN. If the client offers a setting to use its own DNS or restore automatic DNS, use the documented option rather than entering an unfamiliar server address. On Android, review whether Private DNS has been set to a custom provider; on computers, check whether DNS was manually configured for the Wi-Fi adapter. On Apple devices, review any installed VPN, DNS, filtering, or configuration profile that could be affecting the connection.
Also check for overlapping network tools. A second VPN, proxy app, ad blocker, firewall, endpoint-security product, or custom DNS utility may compete with the VPN client for traffic routing. Disconnect or pause one tool at a time using its normal controls, then test again. Do not remove a work or school management profile without permission, and do not leave security software disabled after a brief diagnostic test.
On desktop systems, check the operating system’s proxy settings as well as the VPN app. A proxy configured for a browser or system can cause traffic to take a different path from the one you expect. In a VPN client that supports split tunneling, verify whether the affected apps are included in the tunnel; an app excluded from it may continue using the Wi-Fi connection directly. Keep a note of any original setting so you can restore it after testing.
Try another server or protocol
A particular server may be temporarily unreachable from one network, or a network may handle one connection method more reliably than another. If the client offers multiple servers, choose another suitable option and test again. Change one variable at a time: first try a different server while keeping the protocol the same, then compare a different protocol if the client provides that choice. This makes the result easier to interpret.
Protocols and transport options do not behave identically. Depending on the service and client, options may include WireGuard, OpenVPN, IKEv2, Shadowsocks, VMess, Trojan, or Hysteria2. Availability, names, and configuration depend on the provider; do not assume every client supports every option or that a protocol name alone guarantees a successful connection. Some networks filter certain traffic patterns, while others have trouble with a specific transport or connection mode. Follow the provider’s client instructions and use only options actually offered for your account.
If a protocol setting includes automatic selection, that can be a useful baseline. If the automatic option fails on one Wi-Fi network, compare a supported alternative, reconnect, and test a small set of ordinary sites or apps. If you use a third-party client such as Clash Verge, sing-box, or Shadowrocket, verify that the subscription or profile was imported correctly and that the active configuration uses the intended outbound route. Do not edit unfamiliar configuration values simply because they look network-related.
Keep the operating system and VPN client reasonably up to date, and use the provider’s current setup guide when importing a subscription. A stale profile, expired configuration, or outdated app can cause connection failures that look like a router problem. If the service offers an official client for your platform, testing that client can help determine whether the issue is specific to a third-party configuration.
Consider IPv6, MTU, and Wi-Fi stability
When basic checks do not resolve the problem, less visible network details may be involved. IPv6 is one example: a device, router, or VPN client may handle IPv4 and IPv6 traffic differently. Symptoms can include certain sites failing while others work, or traffic taking a path that does not match the client’s expected routing. Do not disable IPv6 system-wide as a guess. First look for a documented IPv6 setting in the VPN client or ask the provider whether the current configuration supports it.
MTU, the maximum size of a network packet, can also affect a tunnel. If packets are too large for a path and fragmentation or path discovery does not work as expected, some connections may stall or load incompletely. This is not the first thing to change: an incorrect MTU can make performance worse. Only adjust it if the VPN client or provider documents a specific test for your platform, record the original value, and revert the change if it does not improve the symptom.
Wi-Fi quality matters even when ordinary browsing seems acceptable. A weak signal, interference, or roaming between access points can interrupt a long-lived VPN connection before a short web request visibly fails. Test near the router, keep the device stationary for the comparison, and see whether the problem appears on another Wi-Fi band or access point if your network provides one. A VPN cannot make an unstable local wireless link stable, so resolve repeated Wi-Fi drops before drawing conclusions about server performance.
If the VPN works on one Wi-Fi network but not another, record the network type, device, client version, selected server, selected protocol, and exact error. This information is more useful to support staff than saying only that the VPN is broken. Avoid sharing passwords or a complete subscription link in a public forum: subscription links can provide access to account configuration and should be treated as private credentials.
Bottom line: If the VPN works on mobile data, compare networks before reinstalling apps or changing router security settings. Confirm Wi-Fi internet access, clear any captive-portal step, test for DNS or proxy conflicts, and then compare a different server or supported protocol one at a time.
Frequently asked questions
Why does my VPN work on mobile data but not Wi-Fi?
Mobile data and Wi-Fi use different network paths and may apply different DNS, firewall, or traffic-filtering rules. A captive portal or router setting can also affect the Wi-Fi connection. Compare the same device on another Wi-Fi network: if the problem occurs only on one network, investigate that network before changing the VPN account or reinstalling the client.
The VPN says connected, but nothing loads. What should I do?
Disconnect and reconnect to Wi-Fi and the VPN, then test more than one app. Check DNS or Private DNS settings, system proxy settings, split-tunneling rules, and other VPN or filtering apps. If only particular apps fail, check whether those apps are excluded from the VPN or use their own network settings.
Should I turn off my router firewall?
Not as a general troubleshooting step. Disabling a firewall can expose devices on the network and may not address the cause. If you manage the router, review its documentation and make only a specific, reversible change that you understand. On a public or managed network, ask its administrator whether VPN use is supported.
When should I contact VPN support?
Contact support after confirming that Wi-Fi works without the VPN and testing whether the failure is limited to one network, server, or protocol. Include the device and operating system, VPN client and version, connection method, error text, and the tests you tried. Never send your password or post a private subscription link as part of a troubleshooting report.