Wi-Fi Sign-In Page Won't Load? How to Force the Login Page on a Laptop (Hotel, Airport, Coffee Shop)

You're in a hotel room, an airport lounge, or a coffee shop, and you join the free Wi-Fi on your laptop. It connects — the icon says so — but every web page just spins and eventually times out, and Windows or your Mac quietly reports "connected, no internet." What's missing is the sign-in page: the screen where you accept the terms, enter a room number, or click "Connect" before the network lets any real traffic through. That page has a name — a captive portal — and when it refuses to appear, you're stuck on a network that looks connected but does nothing.

The good news: this is almost never a broken laptop or a broken network. It's a well-known snag with a short list of reliable fixes, and it's gotten more common lately for a specific modern reason we'll explain. You don't need to install anything or pay for a "Wi-Fi fixer" tool — the search results are full of those, and none of them fixes a captive portal. Work through the steps below in order and you'll usually be online in a couple of minutes.

First, make sure it really is a sign-in network

Most free public Wi-Fi is open — no password — and gates access behind that web page instead. So before troubleshooting, confirm that's the situation: you joined a network with no password (or a posted one), it connected, but nothing loads and no sign-in screen popped up. If instead you got a "wrong password" error, or it never connects at all, that's a different problem — see our guide on a laptop that won't connect to Wi-Fi when your phone can.

One quick check that saves time: does your phone get online on the same network? If your phone sailed through the sign-in page but your laptop didn't, the network is fine and the fix is on the laptop (keep reading). If neither device can get the sign-in page to appear, the portal itself may be having a bad day — try again in a few minutes, move closer to the access point, or ask the front desk, because sometimes their login system is simply down.

The one trick that works most often: open a plain, non-secure page

Here's the single most effective fix, and it's worth trying first. Open your web browser and, instead of letting it load your usual home page (which is almost certainly a secure "https" site), type a plain, non-secure address into the bar and go: neverssl.com is built exactly for this, and http://example.com works too. In most cases the captive portal will immediately hijack that request and throw up the sign-in page.

Why this works — and why your normal home page doesn't — is the key thing to understand. To show you its login page, the network has to intercept your browser and redirect it. But modern browsers refuse to be redirected away from a secure (https) site, on purpose, to stop anyone tampering with an encrypted connection. So when your browser tries to load a secure page and the network tries to bounce it to the portal, the browser blocks the redirect to protect you — and the portal never gets its chance. A plain http site has no such protection, so the redirect goes through and the sign-in screen appears. That's why "just open the browser" often fails while "open neverssl.com" works: it has to be a non-secure address. (This is also why neverssl.com exists at all — it promises never to upgrade itself to https, precisely so it can trigger these pages.)

The modern culprit almost nobody knows: secure DNS

If the neverssl trick doesn't work, this is very likely why — and it's a genuinely new problem, so most older advice online skips it. Over the last couple of years, Chrome, Edge, and Firefox have all switched on "Secure DNS" (technically DNS-over-HTTPS) by default. It's a privacy feature that encrypts the behind-the-scenes lookups your browser uses to find websites. The catch: a captive portal works by intercepting exactly those lookups to redirect you to its sign-in page — and when they're encrypted, it can't. The result is a network that stays "connected, no internet" with no login page in sight, no matter how many times you reload neverssl.

The fix is to turn secure DNS off temporarily so the portal can do its job. In Chrome or Edge, go to Settings > Privacy and security > Security, scroll to "Use secure DNS," and switch it off; reconnect to the Wi-Fi and the portal should appear. In Firefox it's Settings > Privacy & Security > DNS over HTTPS, set to Off. Sign in to the network, and you can switch secure DNS back on afterward if you like — many portals only need to see you once. If you use a third-party DNS or security app (some antivirus suites and ad-blockers reroute DNS), pause it for the same reason before connecting.

Turn off your VPN before you connect

A VPN and a captive portal fundamentally can't coexist at the moment you sign in. A VPN encrypts and tunnels all of your traffic to its own server — which means the local network can't intercept it to show the portal, and often the VPN can't even establish its tunnel until you've passed the portal and gotten real internet. So you get a standoff: the VPN is waiting for internet, and the portal is waiting for you.

Disconnect the VPN first, join the Wi-Fi, sign in through the portal, confirm you actually have internet, and only then turn the VPN back on. On public Wi-Fi a VPN is genuinely worth using once you're connected — just not during the sign-in step itself.

Check for a manual DNS setting left on your adapter

Separate from the browser's secure DNS above, some laptops have a DNS server typed directly into the network adapter — often a leftover from a VPN, a security tool, or a "make my internet faster" tip that had you set 8.8.8.8 or 1.1.1.1 by hand. On a public network that can quietly block the portal for the same reason: the sign-in system expects to answer your DNS lookups itself, and it can't if you've hard-coded someone else's server.

Set DNS back to automatic so the network can hand you its own. On Windows: Settings > Network & internet > Wi-Fi > Hardware properties > DNS server assignment > Edit > Automatic (DHCP). On a Mac: System Settings > Network > Wi-Fi > Details > DNS, and remove any addresses listed there. Reconnect and try the neverssl trick again.

Use a private window, a different browser, or clear the cache

Captive portals get tripped up by anything your browser remembers. A cached copy of an old page, a stale cookie from the last time you used this network, or a browser extension that blocks scripts or redirects can all stop the sign-in screen from rendering. The quickest way around all of that at once is a private/incognito window (Ctrl+Shift+N in Chrome or Edge, Cmd+Shift+N in Safari), which starts with no cookies, no cache, and extensions usually disabled — then load neverssl.com in it.

If that still doesn't do it, try a different browser. On Windows, Edge tends to cooperate with sign-in pages because it's tied into the operating system's own portal detection; on a Mac, Safari is the one that most reliably pops the portal for the same reason. And if you suspect a stubborn cached page, clearing your browser's cached files (or just cookies for the site) and reconnecting is worth a shot.

Make the network re-offer the sign-in page

Windows and macOS both probe every new network the moment you join — Windows quietly requests a Microsoft test page, a Mac requests an Apple one — and if the reply gets redirected, they know it's a sign-in network and normally pop the portal for you (on Windows, a "Sign in" prompt on the network; on a Mac, a small login window opens on its own). If that automatic prompt didn't fire or you dismissed it, you can force a fresh probe by disconnecting and reconnecting.

The cleanest way is to forget the network and rejoin it, which triggers the whole detect-and-redirect sequence from scratch. On Windows: click the Wi-Fi icon, right-click the network, choose "Forget," then reconnect — and watch for the "Sign in" notification, which opens the portal when you click it. On a Mac: System Settings > Network > Wi-Fi > Details for the network > Forget This Network, then rejoin. Simply toggling Wi-Fi (or Airplane Mode) off and back on is a faster, lighter version of the same idea and sometimes enough on its own.

The small stuff that quietly breaks it

A wrong clock. If your laptop's date and time are off by more than a little — common on a machine that's been off for a while or had its clock reset — secure pages and many sign-in portals fail to load, because the security certificates they rely on are checked against the current time. Set the clock back to automatic (on Windows, Settings > Time & language > Date & time > "Set time automatically"), reconnect, and try again. If your clock keeps drifting or resetting on its own, that's worth fixing at the root — we have a separate guide on a PC clock that won't stay correct.

A per-room or per-account device limit. Lots of hotels cap how many devices one room or guest login can put on the Wi-Fi — often just one or two. If your phone and tablet are already on and the portal now refuses your laptop (or logs one device off when another joins), you've likely hit the cap. The fix is usually to remove a device you don't need online, or call the front desk and ask them to raise your limit or clear old devices; many hotel systems let staff do it in seconds.

A portal that wants information you don't have yet. Some sign-in pages ask for a room number and last name, a code printed on a receipt, or a voucher from the counter. If the page did load but won't accept you, you may simply be missing that detail — grab it from the front desk, your receipt, or the posted sign, rather than assuming the network is broken.

On your phone instead of a laptop?

The same captive-portal logic applies to phones, but the menus and a couple of the causes are different — most notably the private/randomized Wi-Fi address that iPhones and Androids use by default, which can block a portal specifically on a hotel or airport network. If it's your phone that won't get past the sign-in page, our guide to a phone that won't connect to Wi-Fi walks through the phone-specific version of all of this, including the private-address toggle.

How we can help

A captive portal that won't load is almost always one of the things on this page — a secure page it can't redirect, secure DNS or a VPN in the way, a wrong clock, or a device limit — and none of them is a fault with your laptop. There is no legitimate "Wi-Fi login repair" download; ignore the tools promising one. If you've worked through these steps and public sign-in pages still never appear for you — or your laptop drops secure DNS and other networks but not this one — that can point to a deeper network or profile issue on the machine, and that's the kind of thing we're glad to sort out. We help people across Southern California and the Coachella Valley get laptops, phones, and tablets reliably online, at home and on the road.