same here, other browers also on different devices seems to work fine. Also my external connection seems to work correct.
I reset the chrome browser, stil no result.
I believe this is the culprit:
Chrome recently rolled out āPrivate Network Access preflight enforcementā, which:
- Blocks cross-origin HTTP requests from public origins (like a local web app, extension, or even devtools page) to private IPs unless the server explicitly allows it
- Sometimes misclassifies direct IP access as a cross-origin violation, especially when mixed with HTTPS, HSTS, or insecure contexts
This leads to ERR_ADDRESS_UNREACHABLE even when:
- The IP is correct
- The server is online
- Other browsers work
In a pinch you can bypass this by launching chrome with flags, but this is obviously only a bandaid (on MacOS):
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
--user-data-dir=/tmp/ha-debug \
--disable-features=BlockInsecurePrivateNetworkRequests \
--disable-web-security \
--allow-insecure-localhost \
http://homeassistant.local:8123
This workaround solves the problem. Looks like you nailed it! Thanks!!
Actually, just --disable-features=BlockInsecurePrivateNetworkRequests
is enough to let me connect to my local HomeAssistant instance.
Now I need to figure out a long-term fix, or hope Chrome gets smarter.
The posts from 2025 have nothing to do with the original thread and the Chrome issue have been fixed some time ago, but because the posts were used to a thread with unrelated topics, then no solution was posted here.
Please start a new thread instead in the future.
Chrome was working for me yesterday and stopped working for me today (after I had to apply a MacOS patch overnight, so somewhere in there I assume) this worked for me perfectly. Thank-you.