iOS 15 can no longer connect locally to energy gateway

[morph3ous]

This is not a problem with the energy gateway or an issue on Tesla’s side. If others are seeing the following, then it may be an iOS 15 bug.

Prior to iOS 15, if I went to the ip of my energy gateway I would have to go through some hoops and click to ignore warnings to proceed to the site. This is because the gateway is using a self-signed certificate. On iOS 15 I am greeted with a gray page with no text. There is no warning or ability to proceed to the site.

Is anyone else seeing this?

 

[zanary]

Apple I think is enforcing ATS for all web site that Mobile Safari connects to. If you have an MacBook Pro with Big Sur, you can run a command to test out ATS compatibility on the self signed certificate in the Powerwall Gateway. I'm guessing it's failing on multiple ATS posture checks which might explain why Safari is failing to connect.

Alternatively, have you tried Chrome for iPhone to see if it has the same issue. I think Chrome is more forgiving when it comes to posture checks against SSL certificates...


/usr/bin/nscurl --ats-diagnostics --verbose <put_in_URL_of_your_Powerwall_gateway_here>

 

[morph3ous]

It must be the ATS checks Like you said. It works fine in mobile Chrome.

 

[zanary]

It must be the ATS checks Like you said. It works fine in mobile Chrome.

I guess Chrome is your browser of choice when connected to the Powerwall Gateway. I think with iOS 15, you are unable to disable any of the ATS posture checks... Apple is all about security and privacy now

 

[boaterva]

I was going to say the same, use another browser . I'll test this when I get my new phone tomorrow, but I'm assuming there are no options to disable any of the 'new security'. Thanks, Apple! At least we CAN load FF or Chrome....

I used to connect locally all the time when the updates blew up the wifi or other issues, but recently it seems they've made it pretty seamless.

 

[zƬesla]

/usr/bin/nscurl --ats-diagnostics --verbose <put_in_URL_of_your_Powerwall_gateway_here>

shows everything as PASS using local IP under Big Sur

 

[jhn_]

Do you have private relay turned on in iCloud settings of your iOS 15 device?

 

[morph3ous]

Do you have private relay turned on in iCloud settings of your iOS 15 device?

Private relay is turned off on my device.

I think maybe it will work if I can add a dns entry locally so I can match one of the SAN entries on the cert. Maybe it just will not work by IP.

That said, chrome works fine like @zanary suggested.

 

[morph3ous]

That is not the case. I can’t access my firewall by name that matches the name on its self-signed cert. I guess the cert just needs to be trusted on the device. I could go through the trouble of doing that, but I’m just going to use Chrome.

 

[BrettS]

For what it’s worth, I just tried and I had no problems connecting to my system using safari on my iPhone 12 with iOS 15. It came up with the normal warnings about the cert, but I was able to bypass them and connect.

 

[JGerardin]

Prior to iOS 15, if I went to the ip of my energy gateway I would have to go through some hoops and click to ignore warnings to proceed to the site. This is because the gateway is using a self-signed certificate. On iOS 15 I am greeted with a gray page with no text. There is no warning or ability to proceed to the site.

Is anyone else seeing this?

Just logged in to my Gateway2 with iPhone 12 & iOS15 and got the usual warning dialogs and was able to click on "See Details" and follow up with passwords to get in successfully.

 

[morph3ous]

Just logged in to my Gateway2 with iPhone 12 & iOS15 and got the usual warning dialogs and was able to click on "See Details" and follow up with passwords to get in successfully.

That’s so weird. When I first noticed the issue on both my iPhone and iPad, I asked a friend if he was having issues connecting to any of the devices on his network with self-signed certs using Safari on iOS 15. He told me it was working fine for him as well.

Maybe it is related to some way I have set something on both my devices. Is anyone else experiencing the problem? It may only be me.

 

[boaterva]

Tried this with my new iPhone 13 Pro Max, no issues at all. Using the usual 192 IP address as always, no special warnings. Maybe because I’d been there before. (I’d migrated all data from the old phone).

 

[morph3ous]

Tried this with my new iPhone 13 Pro Max, no issues at all. Using the usual 192 IP address as always, no special warnings. Maybe because I’d been there before. (I’d migrated all data from the old phone).

Seems like it is just me then. If I ever figure it out I’ll let you all know what it was…

 

[powerwall88]

Were you able to figure this out?

I cannot connect to the teg2 on my iPhone 13 pro on iOS 15.5 using safari, but I can on Firefox

I can also still connect to the teg2 on my iPhone X on iOS 15.2 on safari

As far as I can tell all my settings are the same on the X and 13 pro (other than the iOS version)

 

[morph3ous]

I never figured it out. It seems to work in Chrome on iOS. So I’ve just been doing that…