Ethernet connection: Safari, Duck Duck Go ok, Chrome not ok - Personal problem?

Long time network configuration, long time user: DHCP recently reassigned IP addresses. I updated my HA network settings accordingly. Safari and Duck Duck Go browsers connect to my HA with the new Ethernet IP address 192.168.1.244:8123 and old URL homeassistant.local:8123. Chrome connects by to the new 192.168.1.244:8123 but not the old homeassistant.local:8123.

I have confirmed network settings, followed suggestions in Network configuration - Home Assistant, reset cookies in Chrome, checked all Chrome settings, tried http:// and https://, checked router settings, checked computer network settings. Years ago I read that Chrome is the better browser to use. I’m surprised by this on my iMac 2024 running Sequoia, HA on Yellow, LAN on AT&T BGW320, wired connection, WiFi turned off.

I ask for suggestions to resolve what might be a personal problem. I hate it when my technology doesn’t work right.

Edit: The HA app is on an Android phone

Hello Dennis Page,

Your firewall / router / network is not passing MDNS packets properly.
This is very common. It’s why I don’t use any .local anything.

No, I don’t know how to fix it, but searching the internet for that might help you. It is not (to my knowledge) a Home Assistant problem.

.local works with Safari and Duck Duck Go but not Chrome.

I assume you are using an Apple device. To help, I think it is relevant to know whether you are experiencing this on the same device or on different devices.
Next, is it iOS/iPadOS (since they all use WebKit) or not.

Have you cleared your Chrome cache too, or just the cookies*?

I don’t use Chrome, but it looks like the DNS name is cached within the browser, where the others might rely more on the DNS cache of the operating system.


* I don’t think cookies have anything to do with it.

1 Like

Do you have any extensions or ad blockers installed?

homeassistant.local:8123 still works with Chrome

The problem is local to your Chrome browser and has nothing to do with HA, because then the other browsers would be affected too.

I recently read somewhere on this forum about a new setting in Chrome that prevents connections to HA at times, so make a search for Chrome on the forum within the last 2 months and it should be among the hits then.

I found the post you mentioned: HA now refusing to open in a Chrome browser window - #17 by gdudek

I wish I had found this before my posting.

This article discusses why Chrome added private network access control: Chrome will limit access to private networks, citing security reasons | The Record from Recorded Future News

This article discusses strategies Nabu Casa can use: Techniques for bypassing CORS Preflight Requests to improve performance

Edit: corrected link