WiFi Login Page Not Showing Up? Captive Portal Fixes for Android, iPhone, Windows and Mac
You joined the WiFi, the phone says connected, and the login page never appears. Here is why that happens, how a guest gets past it in under a minute, and what a venue should fix so it stops happening.
Every hotel, cafe, airport and co-working WiFi in India that asks you to sign in uses a captive portal: a login page the network shows before it lets your device onto the internet. Usually it opens by itself a second after you join. When it does not, the phone says “Connected, no internet” and nothing happens. This guide covers why, how to open it on each kind of device, and, for the people running the network, what to fix so guests stop hitting it.
The short answer: if the WiFi login page does not open, open a browser and type a plain http:// address such as http://neverssl.com. The network intercepts that request and shows its login page. If that does not work, turn off any VPN, Private DNS or ad blocker, forget the network and rejoin. On iPhone, also turn off Private Wi-Fi Address for that network. If none of this helps, the fault is on the network side.
Why the login page normally opens by itself
The moment a phone or laptop joins a new WiFi network, it quietly loads a known test address in the background and checks the reply. If the reply is exactly what it expects, the network has internet. If the reply is a different page, the device concludes it is behind a captive portal and opens a small sign-in window with that page in it.
Each operating system uses its own test address:
| Device | Background check (plain HTTP) | What you see when it detects a portal |
|---|---|---|
| Android | connectivitycheck.gstatic.com/generate_204 |
A “Sign in to Wi-Fi network” notification |
| iPhone, iPad, Mac | captive.apple.com/hotspot-detect.html |
A sign-in sheet that slides up |
| Windows 10 and 11 | www.msftconnecttest.com/connecttest.txt |
The browser opens, or “Open browser and connect” under the network |
| Firefox (any OS) | detectportal.firefox.com/canonical.html |
A bar at the top: “You must log in to this network” |
These checks are plain HTTP, not HTTPS, on purpose. A network can redirect an unencrypted request to its login page. It cannot redirect an encrypted (HTTPS) one without the browser showing a security warning. That one detail explains most “login page not showing up” cases: if something on the device stops that plain HTTP check, or the network blocks it, the device never learns there is a portal to show.
Newer phones can also be told the portal’s address directly by the network when they join (a standard called RFC 8910), so they do not have to rely on the test alone. Not every network or device uses it yet.
How to open the WiFi login page: the 30-second fix
Try these in order. Most people are online by step 2.
- Wait five seconds, then tap the notification. On Android it says “Sign in to Wi-Fi network” or “Sign in to network”. On iPhone, go to Settings, Wi-Fi and tap the network name again.
- Open a browser and go to
http://neverssl.com. Type thehttp://part. This site exists for exactly this purpose: it never uses HTTPS, so the network can redirect it. Typinggoogle.comusually fails, because Google is HTTPS-only and your browser refuses the redirect. - Turn off your VPN, ad blocker or DNS app (such as a 1.1.1.1 or ad-blocking DNS app) until you have signed in. These carry your traffic past the network’s redirect, so the portal never gets a chance to appear.
- Forget the network and join again. This clears a half-finished session.
- Try a different browser, or a private/incognito window. A cached page or an extension can get in the way.
On Android
- Pull down the notification shade and tap Sign in to Wi-Fi network. It opens the login page in Android’s built-in “Captive Portal Login” screen.
- If the network details say “Private DNS server cannot be accessed”, go to Settings, Network and internet, Private DNS, and set it to Automatic (or Off) while you sign in. A fixed Private DNS provider bypasses the venue’s DNS, which is what the portal relies on.
- If you already logged in on this network before and it asks again, check the network’s Privacy setting. “Use randomised MAC” gives the network a different device address, so it may not recognise you as the same device.
On iPhone and iPad
- Settings, Wi-Fi, tap the ⓘ next to the network. Set Private Wi-Fi Address to Off (on iOS 18 the options are Off, Fixed and Rotating; Fixed or Off both work), then rejoin.
- On the same screen, turn off Limit IP Address Tracking if you see a message that the network is not compatible with iCloud Private Relay.
- Open Safari and go to
http://captive.apple.com. If the portal is there, it will replace that page.
On Windows
- Click the WiFi icon in the taskbar. Under the network, look for Open browser and connect.
- If nothing appears, open Edge or Chrome and go to
http://neverssl.comorhttp://www.msftconnecttest.com/redirect. - Disconnect any corporate VPN. Work laptops often force all traffic through the office, which hides the portal entirely.
On Mac
- A small sign-in window (Captive Network Assistant) should open by itself. If it does not, turn WiFi off and on again from the menu bar.
- Open Safari and go to
http://captive.apple.comorhttp://neverssl.com. - On macOS Sequoia and later, check System Settings, Wi-Fi, Details for Private Wi-Fi address, and set it to Fixed or Off for this network.
Is the “Captive Portal Login” app on my Android safe?
Yes, if it came with your phone. “Captive Portal Login” (com.google.android.captiveportallogin on most phones) is a system component of Android itself, not a third-party app. It is the window Android uses to show a WiFi network’s sign-in page, and it only opens when a network asks you to sign in. You do not need to download a separate “captive portal login” app from a store, and you should be cautious of one that asks for permissions unrelated to WiFi.
If the page still does not appear, it is the network
When a guest has tried all of the above and still sees nothing, the problem is almost never their phone. Hand it to whoever runs the WiFi. If that is you, these are the five causes worth checking, in the order they usually turn up.
1. The operating system’s check is being blocked before login
Before a guest signs in, the network lets almost nothing through. If the rule is so strict that it also blocks the background checks in the table above, or answers them with an error instead of a redirect, the phone decides “no internet” rather than “portal” and never opens the sign-in window. The fix is to make sure those plain HTTP checks are redirected to the portal, not dropped. A correctly set-up portal does this; a firewall or ad-blocking DNS added later in front of the router is a common way to break it.
2. DNS does not work before login
The phone has to look up the address of the test site before it can load it. If DNS (the internet’s address book) is not answering for devices that have not logged in yet, nothing else can happen. Guest devices need a working DNS server from the moment they join, not only after sign-in.
3. The network has run out of addresses
Every device that joins needs an IP address from the router (handed out by DHCP). In a busy venue with a small address pool and long lease times, the pool fills up with phones that left hours ago. New guests then sit on “Obtaining IP address” or connect with no internet, and no portal appears because they never really got on the network. This tends to show up only at peak hours, which is why it is easy to miss when testing in the morning.
4. The portal page itself is slow or broken
If the login page loads heavy images, a font or a script from a site the network does not allow before login, it can hang on a blank screen. Anything the portal needs before sign-in, such as a logo or a payment page, has to be on the allowed list (often called the walled garden).
5. The phone changed its device address
Modern phones use a private, randomised hardware (MAC) address per network, and some rotate it. Many networks recognise a returning device by that address. When it changes, a guest who signed in yesterday looks like a new device today and is asked again. That is not a fault, but it explains “it keeps asking me to log in”. A clear, quick login screen matters more than trying to stop it.
What guests can do vs what the venue has to fix
| Symptom | Likely cause | Who fixes it |
|---|---|---|
| Connected, no internet, no notification | VPN, Private DNS or ad blocker on the device | Guest: turn it off until signed in |
Works in a browser at http://neverssl.com only |
Device skipped the automatic check | Guest: use that address; nothing to fix |
| Works on iPhone but not Android (or the reverse) | One OS’s check is blocked before login | Venue: allow and redirect that check |
| Fails only at busy times | Address pool (DHCP) exhausted | Venue: larger pool, shorter lease |
| Page opens but stays blank | Portal content blocked before login | Venue: add it to the walled garden |
| Asked to log in again every visit | Randomised device address | Neither: expected behaviour |
| Login page opens, OTP never arrives | SMS delivery, not the portal | Venue: offer a second OTP channel |
Where Wyfy Guest fits
Wyfy Guest runs the captive portal for venues in India: a branded login page with mobile, WhatsApp or email OTP, or a voucher code, chosen per location. A venue’s Access Rules let it allow specific websites before login, so a payment page or the venue’s own booking site can open without signing in. The dashboard shows who is connected right now and keeps a record of each login, so “the WiFi isn’t working” can be checked against what the network actually saw, rather than guessed at.
We don’t claim a portal can make every device behave the same way. Phones change how they detect networks with almost every major release, and a VPN on a guest’s phone will hide any portal. What a well-run network can do is make sure nothing on its side stops the phone from seeing the login page. For the wider list of guest WiFi login problems from the venue side, see Common guest WiFi login problems, explained. For what a captive portal is, see What is a captive portal.
Common questions
Why is my WiFi login page not showing up?
Usually because something stopped your device’s automatic check: a VPN, a Private DNS setting, an ad-blocking app, or the network blocking that check before login. Open a browser and go to http://neverssl.com. If the login page still does not appear, the network itself needs fixing.
How do I open the captive portal login page manually?
Open any browser and type a plain HTTP address, such as http://neverssl.com, or http://captive.apple.com on Apple devices. The network redirects that request to its login page. Do not use google.com: HTTPS sites cannot be redirected, so you get an error instead.
What does “Sign in to Wi-Fi network” mean on Android?
It means the network you joined wants you to log in on a web page before it allows internet access. Tap the notification and Android opens that sign-in page. It is normal on hotel, cafe, airport and office guest WiFi.
Why does it say “Connected, no internet” on guest WiFi?
Before you sign in, that is expected: you are on the network, but the network is holding back internet access until you log in. If it still says so after you have signed in, the venue’s internet line may be down or your session may have ended.
Why does the WiFi keep asking me to log in again?
Most phones now use a private, randomised device address for each network, and some change it over time. The network recognises returning devices by that address, so a changed address looks like a new device. Sessions also end after the time limit the venue sets.
Does a VPN stop the captive portal from opening?
Yes. A VPN sends all your traffic through an encrypted tunnel, so the network’s redirect to its login page never reaches you. Pause the VPN, sign in, then turn it back on.
