 So Larry said, I went out of town this past weekend and stayed at a hotel that I had stayed at many times over the years. This time I took my 14 inch MacBook Pro M3 and instead of my 10.9 inch iPad Pro, I also took two iPhones. The first thing I do when I get to the room is to connect my iPhones and iPad to the hotel Wi-Fi, usually with no problems. This time I had no problems with the iPhones, but lots of problems with the MacBook Pro. The procedure is to connect the phone or the MacBook Pro to the Wi-Fi and the webpage opens in the browser for me to accept the service. Everything went well with the iPhones, but not on the laptop. When I enabled the Wi-Fi, I did not get a browser page asking for me to accept the service. Instead I got nothing but a note on the Wi-Fi page saying the Wi-Fi was unsecured and the MacBook Pro did indicate that the computer was connected to Wi-Fi, but when I tried to access the webpage, I got a notice that I was not connected to the internet. I tried everything I could think of to no avail. I rebooted a couple of times into safe mode, no change, I removed all the extensions from my browser, Firefox with no change, changed browsers to Safari and Chrome, still no internet. I'm at a loss as to what I need to change. I'm running macOS 14.4.1 with 16GB of memory, 512GB SSD, and I have connected to a local community Wi-Fi with no password with no problems. This is the first time I've taken this MacBook Pro on a trip and tried to use it in place of my iPad. Any suggestions to help would be very much appreciated. I have not contacted Apple Support yet in the hopes that one of you fine podcasters will have the answer. Dave, I think you have the answer. I could be wrong. Well, I don't know if I have the specific answer for Larry, but I know what I would do if I were in Larry's shoes, which is sort of my default. It's our default way of approaching your questions when they come in. If we know the specific answer, we'll answer it, but otherwise it's, here's what I would do next if I were there. So oftentimes this happens because as soon as your computer starts to connect to the internet, as soon as it realizes it has an IP address, it starts trying to load all of the things that it needs on the internet, and that includes your mail, whatever, apps are open, whatever things are running in the background, includes your browser too. Every web page these days is secured. We see HTTPS, we see the little lock in the URL bar, and when you visit one of these captive portal pages for the hotel, the way the hotel delivers that to you is it sees that you're trying to load another web page, and then it redirects that page. It says, no, I'm going to hijack this lookup for this page and show you my captive portal page instead. In a sense, that's what we want to have happen. We normally, we don't like it when our browser stuff is hijacked, but in these scenarios, that's what needs to happen. And the nice part about this is this way you don't need to know what the magic URL is to load the hotel's captive portal page because it's going to be, you know, it might even just be at an IP address slash, you know, whatever. Like you don't know. So this hijacking auto redirects you to the hotel's page and you don't need to know it just says, oh, I'm going to take you there. Great. The problem is your browser, it doesn't like it when a secure page is hijacked because it sees the security certificate doesn't match with where you have been brought and it stops. And that's the end of that. You get a nice blank page. You sometimes, or you get the, or no page, or you get the warning that, you know, the, it's unsecure or whatever, right. And so the way to get around this is to ensure that you load a non-secure page. If in fact, that's the problem. And this might not have been Larry's problem. We'll talk about other reasons that this might happen too. But if in fact, this was Larry's problem, the way you get around it is you load a page that's not HTTPS. Of course, none of the places that we visit are HTTP anymore. Everybody's using HTTPS and that's a good thing. So I always type never SSL.com into my browser toolbar. And as you might guess by the name of the website, it is never SSL. That means it's never HTTPS. It's never secure. It's always sent in the clear. And therefore your browser is okay redirecting to whatever the captive portal on the hotel on the plane, all of those things. So that, that would be step one for me is to visit never SSL.com. And it is always going to be HTTP colon slash slash never SSL.com. It's, it's never HTTPS and, and Apple tries to do this in the background too, right? They have, is it captive.apple.com to either of you know what the, okay. I remember that. Yes. Yeah. PJ put it in the discord. Ah, there it is. Yep. Yeah. So if you remember captive.apple.com that also would work. Yeah, exactly. I, I think never SSL predates it or at least in my memory, it was the first thing baked in there. So that's, that's what I type and it's easy to remember because it's never SSL. So that's one way.