We’ve all been there, you are on some hotel guest Wi-Fi and you see the Wi-Fi connect, but then you can’t get an IP address, and the Captive Portal just isn’t getting triggered.
Here are a couple of solutions that might help trigger the HTTP the Captive Portal is looking for, instead of the HTTPS your client is probably defaulting to.
http://captive.apple.com
Apple’s Default
http://neverssl.com
From François Vergès
http://nossl.sh
From Scott McDermott
https://lnkd.in/gyT5tQR
From Eddie Forero
http://httpforever.com
From Scott Helme
http://check.gstatic.com
Android Default
http://msftconnecttest.com
Windows Default
https://lnkd.in/gHCs7iKn
Ubuntu Default
The above three from Simon Mesnage
You can also trigger the captive portal by grabbing the IP address of the router from your wifi connection info and putting that in a browser.
Sam Crockett
https://www.rfc-editor.org/rfc/rfc8910.html
RFC 8910 – Captive-Portal Identification (DHCP Option 114)
One Response
It is infuriating when this happens, the problem is 99% of people have no idea how to trigger the login page when this happens. The future of public wifi surely has to be secure and seamless. At Purple we serve 100s of millions of these captive portals every year but would like to see the back of them and have released an app, Purple ConneX to deal with that problem.