Why the login page is not appearing
A captive portal works by intercepting your first unencrypted web request and answering it with a redirect to the network's sign-in page instead of the site you asked for. macOS knows this and runs a connectivity check as soon as you join a Wi-Fi network. If that check gets a redirect instead of the expected answer, macOS opens a small sign-in window with the portal inside it.
So when the login page does not appear, it almost always means one of two things: the connectivity check never got a clean answer, or the redirect it should have received was blocked, encrypted or sent somewhere the portal could not reach. The Wi-Fi connection itself is usually fine. What broke is the step on top of it.
The usual causes, roughly in order of how often they turn out to be the problem:
- You opened an HTTPS page, which the portal cannot redirect, so the browser shows an error instead.
- A custom or encrypted DNS setting (DNS over HTTPS, a third-party resolver, a Pi-hole or NextDNS) keeps the redirect from reaching you.
- An active VPN wraps your traffic before the network can touch it.
- You closed the sign-in window too early, and it does not come back on its own.
- Cached DNS from a previous network sends your Mac to addresses that no longer apply.
- Your Mac's private Wi-Fi address changed, and the portal no longer recognises your session.
- A content filter or firewall quietly blocks the portal's request.
Notice that almost every item is a privacy or security feature doing its job. Captive portals rely on intercepting traffic, and modern macOS, browsers and security tools are built to prevent exactly that. The conflict is built in; neither side has a bug.
The fastest fixes, in order
Forget the network and join it again. This fix works most often and takes about fifteen seconds. Open System Settings > Wi-Fi, click Details next to the network, choose Forget This Network, then join it again. That makes macOS run its connectivity check from scratch, which usually brings the sign-in window back.
Open a plain http:// address in a browser. If the sign-in window does not appear, you can trigger the redirect by hand, but only with an unencrypted request. Typing a normal site name will not work: browsers use HTTPS by default, and the portal cannot redirect an HTTPS request, so you get an error or a certificate warning instead of a login page. Type the address with http:// in front, explicitly. Two addresses commonly used for this are http://captive.apple.com and http://neverssl.com. If the portal works at all, one of them should take you straight to the sign-in page.
Turn off your VPN. If a VPN is connected, or set to connect automatically, the portal cannot intercept anything, because your traffic is already encrypted and on its way elsewhere. Turn it off completely, not just the current session, sign in, then turn it back on. Many VPN apps have an auto-connect or always-on setting that reconnects within seconds and quietly undoes your progress.
Check the clock. It sounds unrelated but takes ten seconds. If your Mac's date and time are far off, certificate checks fail everywhere, and portal pages that use HTTPS for the actual login form will not load. Setting date and time back to automatic fixes it.
If all four fail, the cause is most likely DNS or a privacy setting. The next two sections cover those.
When DNS or a VPN is the culprit
Captive portals depend on DNS more than most people realise. When your Mac looks up an address, the network's own DNS server answers with the portal's address instead of the real one, and that starts the redirect. If your Mac is not asking the network's DNS server, that first step never happens.
That is why manually set DNS is such a frequent cause. If your Mac uses a third-party resolver, a Pi-hole at home, DNS over HTTPS or a service like NextDNS, your lookups go somewhere the hotel network cannot intercept. The fix is to set DNS back to automatic for a moment. In System Settings > Wi-Fi > Details > DNS, remove the manually entered servers; the Mac then uses whatever the network hands out. Sign in, then put your own settings back. Encrypted DNS installed through a configuration profile may need to be switched off rather than edited, but the principle is the same.
How do you tell that DNS is the problem? A good sign is a plain http:// address that fails to resolve at all instead of redirecting, or fails instantly instead of after a slow timeout. Another: the router loads when you type its bare IP address, but nothing typed as a name works. That points at name resolution, not the connection.
The VPN case has its own signature. With a VPN active, the connection often looks healthy and the VPN app may even report a working tunnel, yet no site loads and no portal appears. Some VPN apps have a mode for captive portals or hotspots that briefly allows unencrypted traffic so you can sign in. If yours has one, use it. If not, disconnect fully, sign in, reconnect.
Stale DNS from a previous network can also linger. If you have just moved between networks and the Mac seems to reach for addresses that make no sense where you are, flush the DNS cache. In Terminal, that is sudo dscacheutil -flushcache followed by sudo killall -HUP mDNSResponder. If you would rather not type commands, restarting the Mac does the same, and turning Wi-Fi off and on clears a surprising amount of it.
Privacy settings that break portals
Private Wi-Fi Address. macOS gives your Mac its own private hardware address for each Wi-Fi network, which makes it harder for operators and anyone nearby to track your device across places and over time. Since macOS Sequoia there are three settings per network: Off, Fixed and Rotating. Fixed keeps the same private address for that network; Rotating changes it about every two weeks, and macOS uses Rotating by default for open networks or networks with weak security, which is exactly what many hotels run. Some portals tie your paid or time-limited session to the hardware address. The symptom: you sign in successfully and land back on the login page later, or the session you paid for yesterday no longer recognises you.
The better fix is to set this network to Fixed, not Off. Open System Settings > Wi-Fi > Details next to the network and choose Fixed under Private Wi-Fi Address. The portal then sees the same address for your whole stay, and you still do not reveal your Mac's real hardware address. Turn it off completely only if a network refuses to work otherwise, and only for that one network.
Encrypted DNS and content filters. The same logic applies to DNS over HTTPS and DNS over TLS. They exist so the network cannot see or change your lookups, which is exactly what a portal needs to do. There is no clever way around that: for the sign-in itself, the network needs a window. The right approach is a narrow one, switching to automatic DNS just long enough to sign in.
Content filters and parental controls belong in the same category. Anything that inspects, rewrites or blocks DNS and HTTP requests can drop the portal's redirect without a word, and because such tools are built to fail quietly, you often see no error at all, just a page that never loads. If you use one, check it before you conclude the network is broken.
Browser behaviour. Browsers increasingly force HTTPS, block insecure redirects and cache aggressively. A different browser or a private window can be enough to get a portal to show up. Safari is often the most cooperative, because the macOS sign-in window uses the same engine.
Staying protected without breaking the portal
After a few hotels, a pattern is obvious: almost every fix in this guide means briefly lowering a defence. Turn off the VPN. Give up your custom DNS. Let an unencrypted request through. Then, signed in on an untrusted network, you are supposed to remember to switch everything back on. Many people forget, and the laptop sits on hotel Wi-Fi for three days with its protection still off since Tuesday.
That is the real cost, and it is worth naming. Public Wi-Fi is exactly where a Mac benefits from stricter rules than at home: fewer apps allowed online, background services held back and a clear view of what is talking on a network you do not control.
The way out is a tool that knows what a captive portal is, so you do not have to switch it off around one. NetMute shows for free which apps go online on the network you are on and takes any of them offline with one switch, so on hotel Wi-Fi only the browser and the VPN need to talk. With Pro, hotspot protection does this automatically: when your Mac joins an unknown or public network, a stricter profile applies, and the sign-in page is let through instead of being blocked with everything else. You sign in as usual, and the strict profile stays in force.
Network profiles in Pro belong to the network you are on, so your home rules and your airport rules can differ without you thinking about it. Temporary rules expire by themselves, which helps when you want to let one app through for a few minutes. The traffic monitor shows which apps are talking and where.
NetMute is free on the Mac App Store, and Pro is a one-time purchase rather than a subscription. If you spend time on hotel and airport Wi-Fi, a Mac that tightens up on its own and still gets you past the login page solves the part no checklist can: remembering to switch everything back on.

