VPN connection guide · sources checked 2026-11-03
Troubleshoot a VPN that will not connect on Wi-Fi
Use reversible checks for Wi-Fi connection failures and captive portal sign-in pages, with a stop point for managed devices and sensitive activity.
First: is Wi-Fi connected, or is internet access still waiting for sign-in?
A Wi-Fi icon does not necessarily mean the network has granted internet access. Hotels, airports, and cafes may require a captive-portal page where you sign in or accept terms. Complete only the expected venue sign-in; do not enter unrelated account credentials or payment information on an unexpected page. Google and Apple describe these login steps for their devices.
What should I check before changing VPN settings?
Confirm the network name and portal process with venue staff or an official notice. Check whether another device can use the same Wi-Fi and whether your device can reach a different trusted network; this helps distinguish a device issue from a network outage. Check the VPN app's status and any error message, then retry after the portal says access is granted. Menu labels and behavior vary by device, VPN app, and network.
The captive-portal page did not appear. What can I try?
Look for a system notification asking you to sign in. Open a new browser window and load a plain, non-sensitive page to trigger the network's sign-in flow; do not type credentials into a page unless its address and purpose match the venue's expected portal. If needed, disconnect and reconnect to the Wi-Fi once. Google documents these steps on Pixel/Android, and Apple documents its captive-network login screen on iPhone and iPad.
Could the VPN be preventing the Wi-Fi sign-in page from loading?
It is one possible cause: a captive network may require authorization before ordinary internet access is available, while a VPN needs network access to reach its server. This is a troubleshooting inference from how captive login and VPN connectivity work; the exact interaction depends on the network and app. First use the device's built-in portal prompt and the VPN provider's documented captive-portal instructions. If the instructions call for briefly pausing the VPN, do so only before sensitive activity, on a device you control, then complete the venue login, reconnect the VPN, and confirm its connected status before resuming. Prefer mobile data or wait for a trusted network if you cannot do this safely.
What are low-risk, reversible connection checks?
After confirming the portal is complete, check that Wi-Fi is on and airplane mode is off, then disconnect and reconnect to the network. Restart the VPN app's connection using its normal controls. On a network you own, restarting the router may help; on a public or managed network, do not change network equipment or administrator settings. Avoid forgetting a saved network unless you know its password and can complete any required sign-in again.
When should I stop and ask an administrator?
Stop before changing VPN, DNS, certificate, proxy, firewall, or device-management settings on a work-, school-, or otherwise managed device. Contact the device administrator or network owner if access policies, portal credentials, certificates, or repeated failures are involved. Do not disable a kill switch or other protection to make sensitive traffic work; use a trusted connection or pause the sensitive task instead.
How do I know the issue is resolved?
The venue portal reports access, the VPN app reports connected, and a fresh non-sensitive page loads. If you use a separate public-IP or DNS test, it only observes that browser at that moment; it does not prove all apps are covered or that the hotspot is trustworthy. See the IP/DNS and VPN visibility guides for those limits.
Does this guide guarantee that the Wi-Fi or VPN is secure?
No. A successful connection does not verify the hotspot, VPN provider, or every route taken by your apps. Use HTTPS and the expected site address, follow your organization's rules, and avoid sensitive activity when you cannot establish a connection you trust.