VPN, Private Relay, or DNS blocking Wi-Fi login

Try this first

Take the shortest safe route.

1. Try Open Wi-Fi Login before changing anything.
2. Pause one personal blocker, such as a VPN, then retry once.
3. If needed, restore the VPN and temporarily use automatic DNS before one more retry.
4. After the venue login, restore your previous DNS and turn your VPN back on.

VPN

The tunnel may start before the venue grants access.

Pause a personal VPN briefly, open the rescue page, and complete the venue login. Turn the VPN back on immediately afterward and confirm secure sites still load.

If the VPN is required by your employer, school, or device policy, do not disable it without permission.

DNS

The venue may expect its own name-resolution path.

Write down or capture your current DNS choice. Temporarily select automatic DNS, retry the rescue page once, then restore your previous DNS after login.

Android labels this feature Private DNS. Other systems and apps may use different names.

Private Relay and proxy

Treat network-specific privacy changes as temporary diagnostics.

Private Relay and proxy behavior varies by device, browser, network, and policy. Follow current platform instructions, change one setting at a time, and restore it after login.

A certificate warning is not a normal portal step. Stop and use venue or IT support instead of continuing through the warning.

When the venue needs to act

Know when to stop troubleshooting.

Stop and ask IT or venue staff when a setting is managed, when a certificate warning appears, or when the portal still fails after one reversible retry. Do not keep weakening protections to chase the login.

Sources

First-party guidance.

1. Captive portal detectionMozilla Support
2. Manage advanced network settings on AndroidGoogle Android Help
3. Use captive Wi-Fi networks on iPhone or iPadApple Support

Related help

Continue with the closest symptom.