Why will the hotel or cafe wifi login page not appear?
Connected, no internet, and the sign-in page never opens. Why it happens — encrypted DNS, a cached page, an old connection remembered — and the four things that reliably force it to appear.
- Difficulty
- beginner
- Time
- 15 min
- Read
- 5 min
- Safety
- caution
Short answer
The login page appears because the network intercepts an unencrypted web request and redirects it. Modern phones and browsers make almost no unencrypted requests, so there is nothing to intercept. Force one: open a browser and go to a plain address such as neverssl.com or captive.apple.com, typed in full, or turn wifi off and on to trigger the phone's own captive-portal check.
A captive portal is a deliberate man-in-the-middle. The network lets you connect, gives you an address, and then intercepts your first web request and answers with its own sign-in page instead. That trick depended on your device making a plain unencrypted request that could be intercepted and rewritten — and almost nothing does that any more. Browsers force encrypted connections, phones use encrypted DNS, and an encrypted request cannot be redirected, it can only fail. So the portal never gets its chance, and you get a network that says it is connected while nothing works. Every fix below is a way of manufacturing the plain request the portal is waiting for.
Safety
Step by step
- Turn wifi off and on again first.Both iOS and Android make a specific unencrypted check when joining a network, precisely to detect captive portals, and reconnecting triggers it again. It is the fastest fix and works surprisingly often, particularly when the phone joined the network automatically in the background.
- Type a plain unencrypted address into a browser.Type it in full, including http:// so the browser does not upgrade it. Addresses that exist for exactly this purpose include neverssl.com and captive.apple.com. Do not use a search — the search itself is encrypted and will simply fail.
- Turn off private or randomised wifi address for that network.Both platforms use a randomised hardware address per network by default. Some venue systems track your session by that address and get confused when it changes, or when the address does not match an earlier registration. Turning it off for that one network is often the fix for "I registered but it keeps asking".
- Turn off encrypted DNS temporarily.If your phone or browser is set to a private DNS or secure DNS service, the portal cannot redirect the lookup and cannot appear. Turn it off, connect and sign in, then turn it back on. On Android this is Private DNS in network settings; in browsers it is the secure DNS setting.
- Forget the network and rejoin.A remembered network carries a stale session that the phone believes is still valid. Forgetting it removes that and makes the join look new to both sides, which restarts the portal process.
- Try a different device, and prefer the simplest one.An older laptop or a device with fewer privacy protections often gets the portal immediately. Some venues also let you register a device on the portal from another device already signed in, which is the standard way to get a television or a games console online.
- Read the actual instructions rather than guessing.Hotels increasingly use a room number and surname, a code on a card, or a code sent by email. Guessing at the fields on the page is a slower route than reading what reception gave you, and it is where people end up on the wrong network entirely.
- Use your own connection instead where it makes sense.Your phone's hotspot is faster to set up, faster in use, and considerably safer than a shared venue network. If the data is available and roaming allows it, this is often the better answer rather than the fallback.
Common mistakes
- Typing a search into the address bar to trigger the portal — The search is encrypted and cannot be redirected, so it simply fails and tells you nothing. A plain http address typed in full is the thing that works.
- Joining a network because its name sounds official — Fake hotspots named after the venue are a real and easy attack in exactly this environment, where everyone expects a login page. Check the name against what the venue published before entering anything.
- Entering a password you use elsewhere — Some portals ask for an email address and a password, and create an account. Anything typed into a captive portal should be treated as visible to the venue, so it should never be a reused password.
If it doesn't work
Connected with a warning that there is no internet
Cause: The device detected a captive portal and could not open it — Fix: That warning is the device telling you the portal check failed. Turn wifi off and on, then force a plain address.
Page opens and then immediately closes
Cause: The mini-browser some devices use for portals closed on redirect — Fix: Use a full browser instead. On iPhone, closing the portal sheet and opening Safari to a plain address usually completes the sign-in.
Signs in, works for a while, then asks again
Cause: A session timeout, or a randomised address changing — Fix: Turn off the private wifi address for that network. Many venue systems also have a fixed session length and re-authentication is expected.
Portal appears but the submit button does nothing
Cause: The page depends on something being blocked — Fix: Turn off content blockers and any VPN, and try a different browser. Portal pages are often badly built and break on anything unusual.
One device works, another never does
Cause: Different privacy defaults — Fix: Compare the private address and secure DNS settings between the two. The device that works is usually the one with fewer protections turned on.
A VPN is connected
Cause: The VPN prevents the redirect entirely — Fix: Disconnect the VPN, sign in to the portal, then reconnect it. On a public network, reconnecting the VPN afterwards is worth doing — the catalogue's guide on public wifi covers why.
Questions people ask
Why does this happen more than it used to?
Because devices and browsers have become much better at refusing unencrypted connections, and captive portals depend on one. Encrypted DNS, HTTPS-only browsing and randomised addresses are all improvements that happen to break the portal mechanism. The technique is genuinely on its way out and nothing has replaced it.
Is hotel wifi safe to use?
Modern encrypted web traffic means the venue cannot read most of what you do, which is a big improvement on a decade ago. The remaining risks are fake hotspots impersonating the venue and the portal itself asking for information it has no business having. The catalogue's guide on using public wifi safely covers the sensible precautions.
Can I get a smart TV or a console onto hotel wifi?
Sometimes. Many venues have a device registration page you reach from a phone already signed in, using the device's hardware address. A travel router is the other answer — it joins the venue network once and presents your own private network to your devices.
Why does it work at the airport and not at the hotel?
Portal systems vary enormously in quality and in how they cope with modern devices. There is nothing you are doing differently — some systems are simply better built than others.