Your device joins the hotel’s Wi-Fi, but the browser still cannot reach the page you wanted. Many guest networks require a separate sign-in step, often called a captive portal. Completing that step should not require ignoring a warning that a secure website’s identity cannot be verified.
The FTC’s public Wi-Fi guidance explains that widespread HTTPS encryption has made ordinary browsing safer. It also notes that an encrypted connection does not prove a website itself is trustworthy. Network identity, connection security, and the honesty of a page are different questions.
Confirm the route into the network
Ask reception for the exact network name and the expected sign-in method. Select the device’s own “sign in to network” prompt when available. If nothing appears, ask staff for their documented connection instructions rather than guessing a web address from a message sent by an unknown account.
A room-number request can be part of a hotel’s access process, but confirm unexpected payment or identity requests with staff through a known channel. Do not install an unfamiliar certificate, management profile, or app simply because a pop-up says it is required.
For a practical troubleshooting note, record the device, network name, and wording of the problem without including passwords. “Connected to the confirmed guest network; sign-in screen never opens” gives support a different starting point from “browser reports a certificate error on my bank.”
If the process remains unclear, use a trusted alternative connection or wait for assistance. Once connected, keep your device updated and check the address before entering sensitive information. The goal is to finish the hotel’s legitimate access process, not to make warnings disappear until a page happens to load.