2026.3.0 and Safari

[jchh ((not John))]

With 2026.3.0 I now need to load HA twice in fairly rapid succession in order for it not to hang in Safari.

It loads fast enough on the 2nd attempt but hangs forever on the 1st attempt.

This is not a problem with the mobile apps or Firefox. It’s also not a problem for another machine running Safari on the same OS (Tahoe 26.3.1) and a different instance of HA 2026.3.0 (this machine is in different location).

This is a screenshot of the web inspector timeline when it hangs but I’m not sure how to analyse it (this was taken after maybe 60s of hanging:

This is after I call the website twice within ~1sec (it loads instantly on the send attempt):

This is the 'OK" Safari instantly loading a different instance of HA (but still 2026.3.0)

Any ideas?

[PeteRage]

Delete the browser cache

[paulbates]

Same problem on Safari / IPad OS, and as suggested, clearing browser cache immediately restored connectivity to HA

[mennzo]

Same issue on Chrome on iPad OS, and it was happening before 2026.3.0.

[jchh ((not John))]

Hi,

Thanks. I’ve done it but it only worked the first time after clearing.

If I then close the browser, restart it and go back to HA, I have the same loading hang as I had before.

[paulbates]

Can confirm same for me. It works on my PC with edge. Also, I have a home view that is HTML only, and it is served and works as expected on Safari, IPad OS

[sidjohn1]

use the host name (ie: homeassistant.local) instead of the IP, issue cleared for me when i did.

[paulbates]

For me the issue is local when i use IP address.

• To your point if I use nabu casa it works
• In either case, I get the login screen challenge, and when I’m local I then get the spinny arrow and that’s it

[jchh ((not John))]

@paulbates

For me the issue is local when i use IP address.

Same. Works perfectly with the Nabu Casa address.

…also works locally with Firefox (which is very fast).

edit: I’m running HA Core in Docker so no local host name.

[paulbates]

Yep and continues working my W11 / edge. I’m using a green but haven’t been able to get local name resolution (mdns?) working, but I am not going down that rabbit hole, it’s not material to my HA setup.

[jchh ((not John))]

@paulbates

haven’t been able to get local name resolution (mdns?) working

same again.

[ReneNulschDE (Rene Nulsch)]

This is IMHO not a HA problem and more a Safari MacOS/IOS issue. We discussed this already here some months ago. We see this issue with other software solutions too…

Current Solution/workaround: access your HA environment with a name (hostname or set up a name via DNS)

edit: or see here for a more detailed analysis…

[jchh ((not John))]

@ReneNulschDE

This is IMHO not a HA problem and more a Safari MacOS/IOS issue.

I think you’re probably right, but I am still seeking help from others that may know how to address it (if it can be addressed).

The odd thing is I have 2 machines on different sites (both with Tahoe 26.3.1), both accessing (different) HA instances (both 2026.3.0 running on Pi-5’s with the same version of Debian etc etc) via Safari with one displaying the issue and the other not.

[ReneNulschDE (Rene Nulsch)]

Please explain the differences of these environments? Could it be that the working environment is accessible with http/1.1 only? (looks like that forcing http/1.1 over 2 is a solution right now) - Is there a vpn provider in the middle of the client and the working environment?

[jchh ((not John))]

@ReneNulschDE

Could it be that the working environment is accessible with http/1.1 only?

I’m sorry but I do not know what that means.

@ReneNulschDE

Please explain the differences of these environments?

item	Mac 1	Mac 2	notes
MacOS	Tahoe 26.3.1	Tahoe 26.3.1
HA h/ware	PI-5 4GB	PI-5 4GB
HA OS	Dietpi 10.1.2	Dietpi 10.1.2	(Debian varient)
HA install	Core 26.3.0	Core 26.3.0	(docker)
using Safari	NOK	OK	NOK mean hangs on 1st call, works perfectly 2nd time if done quickly
using Firefox	OK	OK

@ReneNulschDE

Is there a vpn provider in the middle of the client and the working environment?

not sure exactly what ‘in the middle’ means but both machines use iCloud private relay. Switching it off seems to make no difference.

---

Edit: Calling HA using the external Nabu Casa url works just fine in Safari in both machines, so this is probably a local problem.

---

Edit 2: I’ve also noticed that if there is one tab with HA open already, opening a new tab and then going to HA will work instantly even on the ‘bad’ machine.

---

Edit 3: Per PeteRage’s point, cleaning the cache in Safari will work the first time. Subsequent calls will hang again (unless done twice in rapid succession).

[ReneNulschDE (Rene Nulsch)]

Do you have different settings on the Mac’s under settings, data privacy esp. tracker…? Are there any other special network components in the Mac 2 scenario in place? The problem will occur whenever you access a websocket based software like HA via direct IP (We can ignore HA, this would happen with other (websocket based) tools too…)

[paulbates]

I agree it is probably safari… however I am seeing it on an iPad Pro. No VPN, no other apple products on the network. HA Green. Turning iCloud private off changes nothing.

There is HomeKit bridge to Ecobee but its bonjour, no apple products.

To your point Google Sheets also stopped functioning on safari after the last major upgrade.

[jchh ((not John))]

@ReneNulschDE

Do you have different settings on the Mac’s under settings, data privacy esp. tracker…?

No, I crossed checked all the Safari settings - they are identical.

[ReneNulschDE (Rene Nulsch)]

then I’m out. All what I have seen in my tests:

• it will not work with IP directly connected
• it will work with name
• it will work with IP as long as a proxy/vpn/security-product is forcing the traffic between the client and the server to the http/1.1 protocol
• (and again) I see the same behaviour in other solutions like proxmox too… therefore I access all apps via name and never via IP with my MacOS/IOS clients

[jchh ((not John))]

Thanks, I do appreciate the help.