How to Fix Hotel Wi-Fi That Won’t Show the Login Page

You check into your hotel, connect to the Wi-Fi, and your phone happily says Connected. Then nothing loads. No web page, no video, and worst of all, no login screen where you are supposed to enter your room number or accept the terms. You are connected to a network that will not actually let you online, and there is no obvious way to summon the page that would fix it. It is one of the most common and maddening travel-tech snags, and in 2026 the usual reason is not the hotel at all. It is a privacy feature on your own phone quietly blocking the login page. Here is a step-by-step fix to get that page to appear and get you online.

That login screen is called a captive portal, and it only shows up when your device gets redirected to it. Anything that stops the redirect, and modern privacy features are very good at stopping it, leaves you connected but stuck. The good news is that the fixes are quick and you can run through them in a minute or two. Start at the top of the list and stop as soon as the portal appears.

The Short Version

If hotel Wi-Fi says connected but the login page never opens, the captive portal is being blocked from redirecting you. The fastest fix is to open a browser and visit a plain, non-secure address like http://neverssl.com, which usually forces the portal to appear. If that fails, turn off privacy features that break captive portals: Private DNS on Android, iCloud Private Relay on iPhone, and any VPN or secure DNS in your browser. Then forget the network and reconnect, try a private browser window, or type the router’s address directly. As a last resort, use another device or ask the front desk to help register yours.

Why the login page never appears

Hotel Wi-Fi uses a captive portal, the page that asks for your room number or a click to agree before it lets you online. Your device is supposed to detect that it is behind a portal and pop the page up automatically, which it does by quietly trying to reach a test address and noticing it gets redirected. The trouble in 2026 is that privacy features encrypt or reroute exactly the kind of request the portal relies on to catch you. Private DNS on Android, iCloud Private Relay on iPhone, secure DNS in your browser, and VPNs all can hide the redirect, so your phone connects but never sees the portal. That is why you end up connected with no way in, and why most fixes below are about temporarily switching those features off so the page can load.

This is general troubleshooting information, and exact menu names and steps vary by device, operating system version, and hotel network. Only turn privacy features back off temporarily to log in, then consider re-enabling them, and avoid entering sensitive information on a network you do not trust.

Step by step: get the login page to appear

1. Force the portal with a plain web address. Open your browser and type a simple, non-secure address such as http://neverssl.com or http://example.com, since a plain HTTP page cannot quietly upgrade to a secure one and usually triggers the redirect to the login screen. This single step solves a large share of cases, so try it first before changing any settings.
2. Turn off Private DNS on Android. A custom or automatic Private DNS setting encrypts your lookups and commonly blocks captive portals. Open your phone’s network settings and set Private DNS to off, following Google’s guide to advanced network settings on Android, then reconnect to the hotel network and try the plain address again.
3. Turn off iCloud Private Relay on iPhone. Private Relay reroutes your Safari traffic and can hide the portal. Turn it off in your Apple Account iCloud settings, or tap the hotel network in Wi-Fi settings and turn off Limit IP Address Tracking, as described in Apple’s overview of iCloud Private Relay. Then reconnect and reopen a plain web page.
4. Disconnect any VPN. A VPN sends your traffic through its own tunnel, which routes right around the hotel portal so it never appears. Turn the VPN off completely until after you have logged in, then reconnect it once you are online if you want its protection on the hotel network.
5. Turn off secure DNS in your browser. Browsers can use their own encrypted DNS that hides the portal, so open your browser settings, temporarily disable the secure DNS or DNS-over-HTTPS option, and try loading a plain HTTP page again to prompt the login screen.
6. Forget the network, then reconnect. A half-finished connection can leave you stuck without the portal ever firing. Tell your device to forget the hotel network, then reconnect from scratch, which often re-triggers the captive portal detection and brings the page up right away.
7. Turn off your private or random Wi-Fi address. Phones now use a randomized Wi-Fi address by default, which can confuse a portal, especially if you connected before. In the network’s settings, set the private or random address option to off for that network, reconnect, and the portal may finally load.
8. Try a private window or another browser. A cached redirect can stop the portal from showing, so open a private or incognito window, or a different browser entirely, and visit a plain HTTP address. The fresh session with no cached data frequently lets the login page through.
9. Open the gateway address directly. Find the router or gateway address in your Wi-Fi connection details, then type that number into your browser. This can load the portal directly when automatic detection fails, letting you reach the login screen by hand.
10. Reset the connection or switch devices. Toggle Airplane Mode on and off, or restart Wi-Fi, to restart the join. If the page still will not appear, try connecting a laptop instead, and if nothing works, ask the front desk for the portal link or to register your device, since they can often add it manually.

What to do if the page still will not load

If you have worked through the list and the portal still refuses to appear, a few fallback moves usually break the logjam. Try a completely different device, since a laptop often triggers the portal when a phone will not, and a second phone can confirm whether the problem is your settings or the network itself. Reboot your device fully, which clears any stuck network state. If you connected to this hotel before, the network may be trying to remember an old session, so forgetting it and rebooting together is more effective than either alone. And do not overlook the simplest fix: call or visit the front desk, tell them your device connects but the login page will not load, and they can frequently send you the direct portal link or register your device on their system. Once you are finally online, you can turn your privacy features back on if you want them, though on an untrusted hotel network it is wise to avoid sensitive logins regardless.

Main Takeaways

• Connected with no login page means the captive portal is being blocked from redirecting your device.
• The quickest fix is opening a plain HTTP address like http://neverssl.com to force the portal to appear.
• Turn off the 2026 privacy features that break portals: Private DNS on Android, iCloud Private Relay on iPhone, VPNs, and secure DNS.
• Forget and reconnect to the network, turn off your random Wi-Fi address, or try a private browser window.
• As a last resort, open the gateway address directly, switch to a laptop, or ask the front desk to register your device.

For more travel-connectivity guides, browse the DelightfulBlogs Travel section, or see our guide to common hotel Wi-Fi captive portal mistakes.

Frequently Asked Questions

Why does my phone say connected but the hotel login page will not open?

Because the captive portal, the login page, only appears when your device is redirected to it, and something is blocking that redirect. In 2026 the usual culprits are privacy features like Private DNS, iCloud Private Relay, secure browser DNS, or a VPN, which reroute or encrypt the request the portal relies on. Turn those off temporarily and open a plain HTTP page to force the login screen to load.

What is the fastest way to make the login page appear?

Open your browser and go to a plain, non-secure address such as http://neverssl.com or http://example.com. Because these are ordinary HTTP pages that cannot silently upgrade to a secure connection, your device is redirected to the captive portal and the login screen pops up. It is the single most effective first step and often works before you need to change any settings.

Does Private DNS or iCloud Private Relay block hotel Wi-Fi?

They can. Private DNS on Android and iCloud Private Relay on iPhone both reroute or encrypt the lookups a captive portal uses to catch your device, which can stop the login page from appearing. Turning them off just until you have logged in usually lets the portal load. You can switch them back on afterward, though avoid sensitive activity on an untrusted hotel network.

Should I turn off my VPN to connect to hotel Wi-Fi?

Yes, at least until you are logged in. A VPN tunnels your traffic past the hotel portal, so the login page never appears. Disconnect the VPN, complete the captive portal login, and then reconnect the VPN if you want its protection on the network. Trying to reach the portal with a VPN still running is a common reason the page refuses to show.

What if none of the fixes work?

Try a different device, since a laptop often triggers the portal when a phone will not, and reboot your device to clear any stuck network state. If you have used the hotel Wi-Fi before, forget the network and restart, so it is not clinging to an old session. If it still fails, contact the front desk, who can usually send you the direct portal link or register your device manually on their system.

The Bottom Line

Hotel Wi-Fi that connects but never shows the login page feels broken, but it is almost always a fixable redirect problem rather than a dead network. Start by forcing the captive portal with a plain HTTP address, and if that fails, temporarily switch off the modern privacy features, Private DNS, iCloud Private Relay, secure DNS, and any VPN, that quietly block it. Forget and rejoin the network, try a private browser window, or reach the gateway directly, and you will get that login screen to appear. Keep this short sequence in mind, and the next time you check in, you will be online in a minute instead of fighting a network that says connected but goes nowhere.