Wi-Fi Login Page Not Showing? Force the Captive Portal

Connected to the hotel or café Wi-Fi, but the login page never appears? Here is the twist that makes the fix make sense: the login page works by hijacking your web traffic — and your browser's security exists to prevent exactly that. Those portals wait for you to visit an unencrypted page so they can swap it for their login form; but in 2026 virtually every site is HTTPS, encrypted, un-hijackable — so the portal waits forever and you stare at "no internet." The fix is deliberately visiting an insecure page for it to grab: open a browser and go to neverssl.com — a site that exists purely for this — and the login page will pounce on it. When even that fails, the ladder below covers the six other blockers, from your VPN to a DNS setting you forgot you changed.

Jake owes this page to a repair-industry expo. Hotel Wi-Fi, three colleagues, three laptops "connected" with no login page in sight, and a lobby consensus forming that the hotel's internet was broken. Jake typed neverssl.com on the first laptop — portal appeared instantly. The second had a VPN auto-connecting at boot, strangling the portal's redirect in its crib; off it went, page appeared. The third was his own shop laptop, which he had once given Google's DNS "for speed" and forgotten — the portal's redirect depended on the hotel's DNS, which his laptop was politely ignoring. Three "identical" failures, three different locks, one lobby's faith in hotels restored.

Ethan: "The receptionist can only hand you the check-in form if you walk through the lobby — but you keep entering through the locked side doors, because every door you own is a locked side door now. Walking through the lobby on purpose, once, is not a security failure. It is how checking in works."

Why the page stopped appearing (a short history of your own security)

A captive portal is a bouncer that intercepts your first web request and answers with its own login page instead. That interception is a man-in-the-middle attack — a friendly, sanctioned one, but mechanically identical to the hostile kind — and the entire HTTPS project of the last decade was built to make such interception impossible. The 2016 version of this page could still say "just open any website"; today any website is encrypted, your browser refuses the swap, and the portal starves. Operating systems fight back with detection probes — Windows quietly checks a plain-HTTP Microsoft address on every new connection, and when the answer looks tampered-with it pops the "action needed" notification — but probes get delayed, cached, blocked by VPNs, or misrouted by custom DNS. When the automation fails, you do manually what it does automatically: offer the bouncer one hijackable page.

The fix ladder — stop at the first rung that works

1. Feed it a plain page: browse to neverssl.com or http://www.msftconnecttest.com/redirect — the second is the very address Windows' own detection uses, which makes it a beautifully appropriate crowbar.
2. Kill the VPN (and "secure DNS"/DoH features in some security apps) for one minute — a VPN encrypts the exact traffic the portal needs to grab. Reconnect the VPN after logging in.
3. Undo custom DNS: if this machine ever got 8.8.8.8 or 1.1.1.1 by hand, the portal's DNS tricks miss you entirely. Settings → Network & internet → Wi-Fi → your network → DNS server assignment → Automatic (DHCP). Change it back later if you must — but automatic-on-Wi-Fi is the traveler's setting.
4. Try a private/incognito window — sidesteps cached redirects and extensions that block the portal's scripts.
5. Flush the plumbing: terminal → ipconfig /flushdns, then toggle Wi-Fi off and on.
6. Forget and rejoin the network (Settings → Wi-Fi → Manage known networks → Forget) — a full reset of the connection state, portal detection included; the complete walkthrough is in our forget-network guide.
7. Knock on the router's door: terminal → ipconfig → note the Default Gateway address → type it into the browser. On many networks the portal lives there and answers directly.

The DNS gotcha, because it deserves its own headline

Half the chronic cases — the people for whom no hotel Wi-Fi ever works — are custom DNS. Portals commonly announce themselves through the network's own DNS server: ask it for any site, get pointed at the login page. A machine hard-wired to Google's or Cloudflare's DNS never asks the hotel's server anything, so it never hears about the portal — it just gets clean answers to questions the network then refuses to route. The symptom signature is distinctive: every public network fails the same way, while phones and other laptops sail through. If that is your life, rung 3 above is your whole cure — and the honest advice is to leave Wi-Fi DNS on automatic permanently; custom DNS belongs on your home network profile, not on a traveling laptop. (The same silent-setting principle came up with a different setting in our Wi-Fi guide — networks remember choices you forgot making.)

The VPN paradox: right tool, wrong moment

A VPN on public Wi-Fi is sensible — and a VPN that auto-connects the instant any network attaches will strangle every portal it meets, because it seals the traffic the portal must intercept before you have logged in. The sequence that keeps both worlds: connect to the Wi-Fi → VPN off → trigger and complete the portal login → VPN back on for the actual browsing session. Most VPN apps have a setting for exactly this dance ("pause on new networks," trusted-network rules, or a captive-portal grace period) — a two-minute settings visit that permanently ends the fight. The same logic applies to browser "secure DNS" (DoH) settings and antivirus web shields: security layers that encrypt or vet your lookups are, at the login moment, standing on the receptionist's foot.

One more modern wrinkle: random hardware addresses

Portals remember who has paid or logged in by the device's hardware (MAC) address — and modern Windows can randomize that address per network for privacy. Useful feature, occasional troublemaker: if the address changes between sessions, the portal forgets you and demands the ritual again, or half-remembers you into limbo. If one particular network keeps "unremembering" you — hotel Wi-Fi mid-stay, a plan you paid for — open that network's properties in Settings and set Random hardware addresses to Off for that network, then forget-and-rejoin once. Privacy on strange networks is worth keeping the feature on generally; consistency on a paid network you'll use all week is the honest exception.

Symptom → likely lock → key

The traveler's two-line insurance policy

1. Bookmark neverssl.com on every device you travel with — one bookmark converts this entire page into a two-second reflex, and it works on phones and tablets exactly as on Windows.
2. Know your phone-hotspot fallback cold — when a venue's network is genuinely broken (it happens), five minutes of tethering beats thirty of portal archaeology. Set the laptop's hotspot connection to metered so updates don't eat the data plan.

And the standing hygiene for any network that greets you with a login page: it is a shared, untrusted network by definition — tell Windows it is Public when asked, keep your browsing to HTTPS (which, pleasingly, is everything the portal was fighting with), and save the sensitive logins for home or the hotspot. What these networks can and cannot actually see is its own story.

Portal-trigger addresses, for the bookmark bar

Different networks respond to different knocks, so seasoned travelers keep more than one. All four below do the same job — hand the portal something it can intercept — and if the first is somehow blocked or cached, the second usually lands. They are safe to visit anywhere, carry nothing, and cost nothing to keep bookmarked forever:

FAQ — captive portals and login pages

Why doesn't the Wi-Fi login page appear?

The portal needs to hijack an unencrypted page, and modern browsing is almost entirely encrypted — so it has nothing to grab. Visit neverssl.com to hand it one on purpose.

What is a captive portal?

The login/terms page public networks put between you and the internet — technically a sanctioned man-in-the-middle that intercepts your first web request and answers with its own form.

What is neverssl.com and is it safe?

A deliberately unencrypted, content-free page that exists specifically so captive portals can hijack it. Safe in the way a doorbell is safe — it carries nothing and asks for nothing.

Why does my VPN break hotel Wi-Fi?

It encrypts the traffic the portal must intercept before you have logged in. Sequence matters: Wi-Fi on, VPN off, portal login, VPN on. Most VPN apps have a captive-portal or trusted-network setting for exactly this.

Why does public Wi-Fi fail only on my laptop?

The classic signature of custom DNS — a hand-set 8.8.8.8 or 1.1.1.1 makes your machine ignore the network's DNS, which is where the portal announces itself. Set Wi-Fi DNS back to Automatic.

What is the msftconnecttest address?

The plain-HTTP page Windows itself probes on every new connection to detect portals. Visiting http://www.msftconnecttest.com/redirect manually re-triggers the check the automation fumbled.

The portal page loads but it's blank or broken. Now what?

Try a private/incognito window (kills cache and extensions), then a different browser entirely. Portal pages are often fragile old web code that ad blockers cheerfully break.

I logged in but still have no internet. Why?

The portal's session tracking hiccupped. Forget the network, rejoin, redo the login — a full state reset on both sides, and the reliable cure for portal limbo.

Why does the hotel Wi-Fi forget me every day?

Session expiry is policy on many networks — but if it forgets you between every connection, Windows' random hardware addresses may be presenting a new identity each time. Turn the setting off for that one network.

How do I find the router's address to visit directly?

Terminal → ipconfig → read Default Gateway → type that number into the browser. On many networks the portal answers there directly.

Does this happen on phones too?

Yes, same mechanics — phones just hide it better with aggressive auto-detection. The neverssl bookmark works identically on Android and iPhone when the automation fails.

Is it safe to type passwords into a captive portal?

Give it the minimum it demands — room number, voucher code — and never reuse a real password there. A portal asking for your email password or card details for "free Wi-Fi" is a scam wearing a lobby's clothes.

Should I use a VPN on public Wi-Fi at all?

After the portal login, it is a reasonable layer — though HTTPS already does the heavy lifting for ordinary browsing. The order is the whole trick: portal first, VPN second.

Why does Windows sometimes open the portal by itself?

That is the connectivity probe working as designed — the "Action needed" notification and auto-opened browser are the success case. This page exists for the days the automation loses the race.

Can I skip the portal entirely?

No — it gates the network's internet access at the router, not on your machine. The fastest path through is triggering it cleanly, which is precisely what the ladder optimizes.

Everyone's devices are failing, not just mine. What then?

Then it was never your laptop — the venue's portal or uplink is down. Phone hotspot, metered connection on, and mention it to staff on your way past; you will not be the first.

Where to go next

Revision note. Originally published November 2016, when "open any website" was still enough to summon a login page. Rewritten August 18, 2026 for the encrypted web that broke that advice: why portals starve now, the neverssl reflex, and the VPN, DNS, and hardware-address locks that keep frequent travelers locked out of lobby after lobby. If hotel Wi-Fi has ever made you feel uniquely cursed, you weren't — you were just carrying better security than the lobby could handle. Spotted something wrong or something missing? Tell me through the contact page and I will fix it. Safe travels.