Hotel WiFi can show as connected while the sign-in page stays hidden. The network is often waiting for a room number, access code, or terms-of-use approval. Before changing DNS or resetting your phone, reconnect to the guest network, open a plain browser page, and pause tools that reroute traffic.
If the same device also fails on your home network, use our WiFi connected but no internet checklist to separate a hotel portal issue from a general connection problem.
First, identify what is actually failing
| What you see | First test | Most likely area |
|---|---|---|
| WiFi is connected, but every site waits | Open a new browser tab and visit a plain HTTP page | Captive portal has not completed |
| One device shows the login page | Compare its VPN, DNS, and private address settings | Device setting or saved network profile |
| Several guests cannot sign in | Ask the front desk whether the portal is working | Hotel gateway or account system |
| Login succeeds, then stops after moving rooms | Forget the old guest network and join the correct one | Access point or session change |
1. Rejoin the exact guest network
Check the hotel card, TV instructions, or front-desk message for the exact network name. Some properties have separate networks for guests, meeting rooms, and staff. On your phone or laptop, forget the guest network, select it again, and enter the password if one is required. Stay near the room access point for the first login.
Do not join a similarly named network just because it has a stronger signal. If the name or password is unclear, ask the hotel to confirm it. A device can show a WiFi connection without having reached the hotel internet service.
2. Trigger the sign-in page with a fresh browser request
After joining, open Safari, Chrome, or Edge in a new tab. Type a simple address yourself instead of opening a saved bookmark. A captive portal needs an ordinary web request so the hotel gateway can redirect you to its sign-in page. If a secure site stays on a loading screen, try a plain HTTP address such as http://example.com, then close the tab and try again.
On iPhone or iPad, Apple describes these networks as captive WiFi networks. The WiFi settings screen may show a sign-in option, and the device can display a notice that the network is not connected to the internet until the login is complete. See Apple’s guide to captive WiFi networks for the current iPhone and iPad flow.
3. Pause VPNs, filtering apps, and custom DNS for one test
A VPN can send the first browser request through a tunnel before the hotel can show its portal. Pause the VPN from its own app and try the fresh browser request again. Also pause browser content blockers or security filters for that test. If the login page appears, turn the protection back on after you finish and use the hotel network only as needed.
Custom DNS can also complicate a guest network that expects its own DNS response. Return the device to automatic DNS temporarily. Do not leave security software disabled on an untrusted public network, and do not remove a work or school profile without following its administrator’s instructions.
4. Use the device’s WiFi details to check the session
Open the network details and check that the device received an IP address, router, and DNS entries. A blank router field or an address beginning with 169.254 means the device did not receive a normal local address. Forget the network, rejoin it, and test near the access point before entering manual IP values.
If the phone and laptop receive addresses but only one browser fails, try a private window or a second browser. This comparison can separate a stale browser session from a hotel gateway problem.
5. Check the hotel instructions before guessing the portal address
Some hotels print a portal address on the welcome card or display it on the room TV. Use that address exactly, including the correct spelling. Do not type a random router address from a forum. A hotel may use a room-specific session, a last-name and room-number form, or a button on its own guest page.
If the page asks for payment details or personal information, confirm the address with the front desk before entering anything. A WiFi name alone does not prove that a login page is genuine.
6. Compare another device and another room location
Try a second device on the same guest network. If it opens the portal, copy the visible hotel instructions but do not share a personal login unless the hotel permits multiple devices. If both devices fail, ask whether the hotel requires a device registration step or has reached its guest-network limit.
If the connection works in the lobby but not in your room, the issue may be the local access point or signal path. Report the room and time to the hotel instead of repeatedly resetting your devices.
7. When to contact the front desk
Contact staff when the network name is missing, the portal returns an error, the account code is rejected, or several devices cannot complete the same step. Tell them the network name, room area, device type, and the last screen you saw. That information helps them distinguish a hotel account problem from a device setting.
After you finish: protect the connection
Forget the guest network when you leave if you do not expect to return. Public WiFi is not the place to leave automatic joining enabled. Use HTTPS sites, keep your device updated, and reconnect your VPN after the portal has finished. If you need a private connection for work, a phone hotspot may be a better choice than sending sensitive traffic through an unknown guest network.
Quick checklist
- Confirm the exact hotel network name.
- Forget and rejoin the network.
- Open a fresh tab and try a plain HTTP request.
- Pause VPN, filtering, and custom DNS for one test.
- Check the IP, router, and DNS fields.
- Compare another device or location.
- Ask the front desk before entering payment or personal details.
