Force the login page to load

Captive portals intercept unencrypted HTTP traffic. Join the Wi-Fi network and open http://nossl.sh so the gateway can redirect you.

If the portal does not appear, pause VPNs or private relay features that hide the first request.

• Join the network and accept any device prompts.
• Open http://nossl.sh in a browser tab.
• Complete the portal login and wait for a success message.

Confirm you are online

Reload this page after you sign in. If you see your IP and headers without a redirect, the portal released you.

Share the request snapshot with support if browsing still fails.

• Check that the URL stays on http://nossl.sh.
• Look for a 200 response instead of a redirect.
• Use the share link to show timing and headers.

If the login page never appears

Forget the Wi-Fi network and reconnect, or try the device captive portal checks for Apple and Android.

• Toggle Wi-Fi off and back on.
• Disable VPNs, private relay, or custom DNS apps temporarily.
• Try another browser or a private window.

Why does the captive portal login page keep looping?

The gateway might not like HTTPS-first traffic or cached cookies. Reload the HTTP page, clear the browser cache, or reconnect to force a fresh redirect.

Is it safe to log in over HTTP?

Captive portals are commonly delivered over HTTP. Avoid entering sensitive data beyond the login itself and switch to HTTPS sites after you are online.

How can I tell the portal released me?

Reload http://nossl.sh and confirm you see the diagnostics page without being redirected to the portal.