Captive portal and VPN on public Wi-Fi
Hotels, airports, cafes, and campuses often require a web login before normal internet works. If the VPN starts before that login, it can look like the VPN broke the connection.
Quick answer
Disconnect VPN, open a plain HTTP site or the network login page, complete the captive portal, confirm direct browsing works, then reconnect GhostMesh and test DNS and IP again.
Recognize the portal
A captive portal intercepts traffic until you accept terms, enter a room code, or complete payment.
DNS and HTTPS can behave strangely before login, so diagnose the portal first.
| Symptom | Likely cause | How to check | How to fix |
|---|---|---|---|
| Wi-Fi connected, no sites load | Portal not completed | Open the network login page | Sign in before starting VPN |
| Only HTTPS errors | Portal intercepting traffic | Try a plain HTTP test page | Complete portal and reconnect |
| Internet blocked after disconnect | Kill switch still protecting traffic | Check VPN state | Reconnect or disable kill switch intentionally |
After login
Reconnect the VPN and repeat IP and DNS tests. Public Wi-Fi networks can also have weak signal, client isolation, or time limits.
If the portal expires, the same symptoms can return later even though the VPN settings did not change.
Checklist
- ✓Complete portal before VPN
- ✓Verify direct browsing
- ✓Reconnect GhostMesh
- ✓Run IP and DNS checks