If your VPN connects over mobile data but not Wi-Fi, the difference between the two networks is a useful clue. Your account and VPN settings may be fine; the Wi-Fi network could be blocking a connection method, waiting for a sign-in, applying a firewall rule, or using DNS settings that interfere with setup. Start with simple checks before changing advanced options. These steps cover iPhone, Android, Windows, and Mac, and help you narrow down whether the cause is the network, the device, or the VPN configuration.
First, note what “not connecting” means on your device. Does the app stay on “Connecting,” show an error immediately, or say “Connected” while websites still fail to load? Those symptoms point to different parts of the connection. If the VPN connects on mobile data, try not to change several settings at once: test Wi-Fi first, record the result, and then move through the fixes below in order.
7
checks to try
4
platforms covered
2
networks to compare
Identify where the connection fails
Before changing settings, establish a simple baseline. Join the Wi-Fi network, open an ordinary website without the VPN, and confirm that the connection is usable. If a browser displays a sign-in page, accept the network’s terms or complete its login first. Then open the VPN app and try to connect. If the app reports success, test more than one website or app; the VPN status alone does not prove that every request is using a working route.
Now compare the same device on mobile data, if available. If the VPN connects on mobile data but stalls on Wi-Fi, focus on the Wi-Fi network, its router, or a network-specific policy. If it fails on both, check the VPN app, subscription configuration, device settings, and service status. If another device can connect to the VPN on the same Wi-Fi, the router is less likely to be the only cause; compare the affected device’s app version, profile, and network permissions.
- ✅ Confirm ordinary browsing works on Wi-Fi before testing the VPN.
- ✅ Complete any hotel, campus, airport, or workplace Wi-Fi sign-in page.
- ✅ Compare Wi-Fi and mobile data on the same device when possible.
- ❌ Avoid changing the router, protocol, DNS, and firewall settings all at once.
For service-specific setup and supported clients, VPNRZ is the place to start. For this connection problem, however, first determine whether the failure follows one Wi-Fi network or follows the device wherever it connects. That distinction can save time and help you give support a useful description if the basic checks do not resolve it.
Fix 1: Check Wi-Fi access and sign-in
Public and managed Wi-Fi networks may require a browser sign-in, acceptance of terms, or confirmation of access before they allow general internet traffic. A VPN can start before that process is complete, but the network may block the tunnel or prevent the sign-in page from appearing. Disconnect the VPN, open a browser, and visit a familiar website. If a portal page appears, complete its steps, wait for ordinary browsing to work, and then reconnect the VPN.
If no portal appears, try opening a different ordinary website while the VPN is disconnected. Avoid entering sensitive information into a page unless you can verify that it belongs to the venue or network operator. Some managed networks also restrict VPN use by policy. On a workplace or school network, ask the network administrator whether VPN connections are permitted rather than attempting to bypass the restriction.
Fix 2: Restart the Wi-Fi connection and device
A temporary Wi-Fi association, address assignment, or app state can leave the device online for ordinary browsing while a new VPN session fails. Turn Wi-Fi off and on, wait for the device to reconnect, and make one fresh connection attempt. If that does not help, restart the device. A restart closes stale app sessions and reloads network components without deleting your saved VPN configuration.
If you manage the router, you can also restart it using its normal controls. Tell other household members first, because this briefly interrupts their connection. Do not reset the router to factory settings as an early troubleshooting step: that can erase the network name, password, and provider settings without addressing a VPN-specific block. If the Wi-Fi is provided by a hotel, campus, office, or landlord, do not restart or reconfigure equipment you do not administer.
On a phone, check that Airplane Mode is off and that Wi-Fi remains connected after the VPN attempt. On a laptop, confirm that the operating system has not switched to another saved network. If the Wi-Fi drops only when the VPN starts, note that behavior; it may indicate an app permission, network-extension, or router interaction rather than a simple weak signal.
Fix 3: Try another VPN protocol or route
VPN protocols do not all use the network in the same way. A Wi-Fi operator or router may allow one type of connection and interfere with another, especially where UDP traffic or unfamiliar ports are filtered. If your client supports more than one protocol, change only the protocol setting, reconnect, and record the result. Depending on the service and client, options may include WireGuard, OpenVPN, IKEv2, Shadowsocks, VMess, Trojan, or Hysteria2. Availability and names vary; do not assume that every app supports every protocol.
Some clients label a transport choice as TCP or UDP. These are transport settings, not interchangeable names for the VPN protocol itself. If the app provides a documented automatic option, try it before making manual changes. Otherwise, use only the protocol and transport combinations offered by your provider and client. Do not copy arbitrary port numbers or configuration values from unrelated guides, because an incorrect value can make a valid profile unusable.
Try a different route or server as a separate test. A single route might be temporarily unreachable from a particular network, while another route works. Choose a nearby or recommended option if the app provides one, but avoid cycling rapidly through many entries; a small, controlled comparison is more informative. If one route works consistently on Wi-Fi and another does not, report the route names and protocol to the provider.
Fix 4: Review firewall, router, and managed network rules
A firewall or router security feature can block traffic needed to establish a VPN session. On Windows or Mac, a third-party firewall, endpoint security app, or recently changed network profile may prevent the VPN client from communicating. Check the security app’s recent alerts and confirm that the installed VPN client is allowed to access the network. Use the operating system’s normal permission controls, and do not disable the firewall permanently just to test a connection.
On a home router, parental controls, access schedules, filtering features, or custom firewall rules may affect VPN traffic. If you administer the router, review recent changes and its documentation. Make one reversible change at a time, retest, and restore the original setting if it makes no difference. If you are unsure what a setting does, ask the internet provider or router manufacturer rather than opening broad access or disabling security protections.
On managed Wi-Fi, the network owner may deliberately limit tunnels for security, compliance, or bandwidth management. A VPN that works on home Wi-Fi but fails on a company or school network can be consistent with that policy. Ask the administrator whether the network supports the VPN connection. Do not try to evade a restriction or install an unapproved profile on a managed device.
Fix 5: Check app permissions and configuration
Confirm that you are using the intended VPN app and that it has permission to create a VPN connection. On iPhone and iPad, iOS may ask you to allow the VPN configuration when you first connect or after a profile change. Review the request and approve it only if you recognize the app and intended configuration. On Android, accept the system VPN connection prompt for the trusted app. If the prompt was dismissed, disconnect and try again so the system can ask anew.
On Windows, verify that the VPN app is permitted through the firewall on the network profile you are using. On Mac, check for an app permission or network extension request in System Settings and approve it only for software you trust. Menu names differ across operating system versions, so use the system search feature for “VPN,” “firewall,” or “network extensions” if the setting is not where expected.
If the client uses a subscription or imported profile, check that the profile is current and that the app reports a successful update. A stale or incomplete configuration can cause connection attempts to fail even though the app opens normally. Update the subscription from its official source, then retry with a supported route. Treat a subscription URL like a password: do not post it in a public forum or share it in an unredacted screenshot.
Fix 6: Review DNS, proxy, and security-app conflicts
DNS translates website names into addresses. A custom DNS setting, filtering app, private DNS feature, or security product can affect name resolution before or after the VPN connects. If the VPN says “Connected” but websites do not load, test whether the issue affects all browsing or only specific names. Disconnect the VPN and compare. If ordinary Wi-Fi browsing also fails, the problem is likely broader than the VPN tunnel.
On Android, review whether Private DNS is configured to use a custom provider. On iPhone, check for DNS or content-filtering profiles installed by an app or organization. On Windows and Mac, review any manually configured proxy or network filter, especially if the issue began after installing security software. Do not remove work or school profiles without permission. If you temporarily change a personal setting for diagnosis, write down its original value so you can restore it.
VPN apps may install network filters or create an operating-system VPN profile. Two VPN clients running at the same time can compete for the same system connection, and privacy, ad-blocking, or antivirus tools may also affect traffic. Disconnect other VPN apps and pause only trusted, optional filters for a brief test if their documentation allows it. Re-enable protections afterward. If the VPN starts working only when a specific app is disabled, update that app or ask its support team how to configure a compatible exception.
Fix 7: Update or reinstall only after basic tests
Check for updates to the VPN client and the device’s operating system. An older client may have compatibility issues with a recent system update, while an outdated profile may no longer match the provider’s current configuration. Use the official app source or the provider’s own download instructions. Before reinstalling, confirm that you can sign in again and obtain any subscription or configuration details you need.
Reinstalling can remove local profiles and permissions, so treat it as a later step rather than the first response. If you proceed, remove the client using its documented uninstall process, restart the device if instructed, and install a fresh copy from a trusted source. Add or update the configuration, approve the operating-system VPN prompt, and make a single connection test. Do not delete a managed configuration or security profile on a work or school device without authorization.
If the problem began immediately after a system, router, or security-app change, mention that in your notes. A clear timeline can be more useful than a general report that “the VPN stopped working,” and it helps support distinguish a client compatibility issue from a Wi-Fi restriction.
Platform-specific checks for iPhone, Android, Windows, and Mac
The checks below focus on settings that commonly differ by platform. Exact labels can vary with operating system versions and device manufacturers. Change only settings you understand, and follow your organization’s rules on managed devices.
| Platform | What to check | Practical next step |
|---|---|---|
| iPhone or iPad | Wi-Fi sign-in page, VPN configuration permission, DNS or content-filtering profiles | Complete the portal in a browser, then reconnect and approve a trusted VPN configuration prompt. |
| Android | VPN connection prompt, Private DNS, another active VPN, battery or background restrictions | Accept the system prompt for the trusted app, compare with Private DNS disabled only if appropriate, and test again. |
| Windows | Firewall permission, network profile, security software, proxy settings | Check recent firewall alerts and allow the correct client through the appropriate network profile. |
| Mac | VPN profile, network extension approval, firewall or security filters | Review System Settings for a pending permission request and approve only software you recognize. |
On mobile devices, also make sure the VPN app has not been put into a restricted background state. Battery optimization can affect reconnection or keep-alive behavior on some Android devices, although it is less likely to explain an immediate failure to start. On iPhone and iPad, check that a trusted VPN profile is still present after an app update. On desktop systems, distinguish a system VPN profile from an app’s own connection configuration: repairing one does not necessarily repair the other.
When to contact your network administrator or VPN support
Ask the Wi-Fi administrator for help if the connection fails only on a managed network, if the network blocks VPN use by policy, or if a captive portal never completes. Contact the VPN provider if the same configuration fails across unrelated Wi-Fi networks and mobile data, if subscription updates fail, or if only one particular route or protocol consistently errors. Your support request should describe the result of tests, not include secret credentials.
Include the device and operating system, VPN client name and version, Wi-Fi type (home, public, campus, or workplace), the exact error text, and whether ordinary browsing works without the VPN. State whether mobile data works and whether another route or protocol changes the result. If you share a log or screenshot, remove account identifiers, IP addresses if you do not want them disclosed, and any subscription URL or access token. Never send a password or full subscription link in a public support channel.
- ✅ Report whether the issue follows one Wi-Fi network or follows the device.
- ✅ Include the app’s exact error and the protocol or route tested.
- ✅ Tell support what changed shortly before the problem began.
- ❌ Do not post passwords, subscription URLs, or unredacted configuration files.
Frequently asked questions
Why does my VPN work on mobile data but not Wi-Fi?
Wi-Fi and mobile data use different network paths and policies. The Wi-Fi may require a sign-in, filter a protocol or transport, apply router rules, or be managed by an organization that restricts VPN connections. Compare ordinary browsing on Wi-Fi, complete any portal, and then test one protocol or route change at a time.
Should I change DNS to fix a VPN that will not connect?
Not as the first step. DNS is more likely to be relevant when the VPN reports that it is connected but names do not resolve, or when a custom DNS or filtering app is already in use. Record the existing setting before changing it, avoid removing managed profiles, and restore the original value if the test does not help.
Is it safe to turn off my firewall?
Do not leave a firewall disabled to make a VPN connect. Check its alerts and allow the trusted VPN client through the appropriate rules instead. If a short diagnostic test is necessary, follow the security product’s instructions, keep the test brief, and restore protection immediately afterward.
What should I send to VPN support?
Send the device and operating system, client version, network type, exact error, and the results of comparing Wi-Fi with mobile data. Mention the route or protocol tested and whether a sign-in page or security app was involved. Redact passwords, subscription URLs, tokens, and any other private configuration details.