Try this first

Take the shortest safe route.

  1. Confirm that you joined the official hotel, airport or café Wi-Fi.
  2. If you typed only a name or used a search result, try the explicit address http://neverssl.com/ in a normal browser tab.
  3. You can also use Open Wi-Fi Login to request http://getmewifi.help/. Complete any sign-in only on the operator’s page.
  4. If neither request opens the login, use the result-specific checks below. Restore any personal setting you change after the test.

The page opens normally

NeverSSL loads, but the Wi-Fi login does not appear

A normal NeverSSL page means that request reached the site without the expected login being shown. It does not establish which connection was used or whether every website is reachable.

Try two unrelated secure websites. If a phone is involved, account for mobile data before judging the Wi-Fi. If secure sites fail over Wi-Fi while the plain page loads, ask staff for the current official login address and whether this device has an active guest session.

Nothing loads

NeverSSL times out or cannot be found

One unreachable site cannot distinguish a site problem from a blocked request or a network problem. Check the network connection and try the alternative rescue address once. If both fail, stop cycling through lists of test URLs.

Use the VPN and DNS guide only for settings you control. Restore the previous choice after each test, whether or not it helps. If other devices fail too, ask staff whether the portal or internet service is unavailable.

HTTPS or a warning

The browser switches to HTTPS or shows a warning

Check that you entered an explicit http:// address. Browsers and network policies can affect how an unencrypted request is handled. A failed HTTPS request is not evidence that NeverSSL or the venue is malicious.

Do not bypass certificate warnings, install a certificate from an unexpected page, or disable browser security globally to chase a login. Try the device’s own sign-in notice or ask the operator for help. On a managed device, ask IT to confirm the supported access method.

The login appears but fails

The portal opens, then loops or rejects my details

The plain request has already done its limited job if the operator’s portal appeared. Confirm the access code, terms step, session allowance or device limit with staff. Replacing NeverSSL with another trigger cannot authorize the session for you.

Neither tool can supply a hotel password, bypass a paid connection or repair the operator’s internet service. Use the repeated-sign-in guide for a loop, or the connected-without-internet guide after a completed login.

When the venue needs to act

Know when to stop troubleshooting.

Ask staff for the official network name and login address, and whether the portal, guest session and internet service are working. Contact IT when a managed device cannot follow the venue’s access method.

Say this to staffI joined the official Wi-Fi. A plain web request does not open a usable login. Could you confirm the sign-in address and check this device’s guest session?

Sources

First-party guidance.

  1. NeverSSL: plain-HTTP connection pageNeverSSL
  2. Captive portal detectionMozilla Support
  3. RFC 8952: Captive Portal ArchitectureInternet Engineering Task Force

Related help

Continue with the closest symptom.

Published Sep 5, 2026 · Updated Sep 5, 2026 · ONEKAPISCH Editorial