In recent years it’s become increasingly difficult to log in to public Wifi networks at airports, coffeehouses, etc. (At least, it has for me.) My understanding is the reason is that most browsers are using https by default, causing them to reject connection to the login page for the public Wifi network. While this may be a good thing for security, it can be frustrating.
I’ve Googled to find a workaround for this problem, and for a while I was able to use neverssl to access the login page. It usually worked well, but recently even this hasn’t succeeded for some networks.
One thing I don’t understand is why it seems easier to call up the login page on some devices than others. My usual browser is Chrome. Recently I’ve had no problem getting the login page using my laptop (HP Envy) or tablet (Samsung Galaxy), while I can’t connect using my phone (also a Samsung Galaxy).
So my questions (Note that my technical understanding or these issues is basic, so please reply with that in mind):
Is there a better workaround to access the login page when the connection is refused?
Is there a better browser to use for this than Chrome?
Why, if I’m using the same browser, should it be easier to get to the login page on my Samsung tablet than my Samsung phone?
I’ve noticed this too. My older phone recognizes WiFi networks and brings up their login screens immediately. Whereas my newer and “better” devices take upwards of a minute or more to perform the same action. Frustrating. And it must be confusing to new users who think the device isn’t doing anything at all.
It’s the opposite for me, since my phone is the oldest of my devices, purchased about four years ago. I got the laptop in 2018, and the tablet this year. The phone is the worst, the tablet the best.
I often have problems getting onto public WiFi, the login page never comes up. Knowing a little about networking, I can usually get to a login/user agreement page by going to one of these IPs, just type them in the address bar:
The problem Colibri is describing can’t be solved by figuring out the IP of the login page. The issue is that browsers are increasingly refusing to connect to login pages that don’t have a valid and current certificate. While that’s reasonable and prudent for, say, your bank’s website, it’s unnecessary hassle and expense (SSL certs can cost anywhere from $150 to over $1000 a year) for a “login” page that really isn’t a login at all, just an acknowledgement that you understand you’re joining a public network. They used to give you a notice that the site may not really be secure with an option to continue at your own risk. Now they frequently just refuse to connect at all, and don’t give you the “I understand the risk” link anymore.