hey there
just recently installed bazzit on my main pc
for some odd reason chrome cant connect to homeassistant.local:8123,
homeassistant:8123 and ip :8123 works, android phone also chrome can use all three
any idea why that is?
Can you ping homeassistant.local from the cli? From your linux box, that is… This is probably related to some DNS resolution change, oe maybe mdns possibly, like .local is no longer resolving.
You might not have a mDNS client installed, so mDNS hosts, which is .local domain, can not be resolved.
i can ping it from the terminal but the browser still cant get a connection
Maybe your browser have DNS over HTTPS active and that disabled mDNS.
1 Like
funny thing is i just installed chrome like i do on my win pc so why should it be disabled?
Make sure it’s not a http vs httpS issue
in the terminal from my linux pc i can ping homeassistant.local only my browser (chrome) cant connect to it
if i enter the adress manually how can i make sure of that?
Add the protocol, check your browser settings, check the address bar what you’re using.
im using none i just enter homeassistant or homeassistant.local first one works second doesnt
wehre would that be
Not sure if you’ve figured this out yet, but wanted to chime in because I had a similar issue.
If you have HA installed as a docker container, or anything other than HAOS or I believe supervised, it doesn’t come with Avahi or some other mDNS service installed, and so it doesn’t have any way to broadcast homeassistant.local out.
Despite the configuration docs saying that the default hostname is that and you can modify it… it does absolutely nothing in a containerized install because that service is missing (at least from what I can tell).
So if that’s how you installed HA, don’t waste more time on this - it’s just not gonna work. You’ll need to install and configure Avahi yourself if you want it to work. On top of that, I think there’s issues getting mDNS to work with Docker as well if you’re not using host network.
You’re on Windows right? Maybe not… From a cmdline, can you telnet to the IP ?
telnet <ip> 8123?
You should see some basic responce…
telnet haos.wmain 8123
Trying 10.0.110.163…
Connected to haos.wmain.
Escape character is ‘^]’.
^CConnection closed by foreign host.
On linux try nc -zv <ip> 8123
Connection to <ip> 8123 port [tcp/*] succeeded!
This is mine… on a linux box, but still similar…
Another thing you can try is to add homeassistant.local to you host file. On Windows I think it’s C:\Windows\system32\drivers\etc\hosts
on linux prob /etc/hosts
Good question.
Browsers may have it activated as default, so you need to disable it.
Some browser companies see the DNS-over-HTTPS as a security feature that should be enabled as default.
I guess it is a security feature in places where the government is eavesdropping and also in places like US, where the ISPs might do it too.
1 Like
This will for sure cause chaos in mDNS.
mDNS is designed to not be hardcoded or controlled by a central server.
There is no features built in to handle such situations or avoid the chaotic outcome.
to make things clear im running homassistant green, and my bazzite(linux) pc is nely setup, i use chrome browser fresh installed on my bazzite, windows and android systems all of them except the linux one can access ha.local only the bazzite one cant, ip or ha without.local works
Sure, maybe long term, but I suggested it as a simple troubleshooting measure to see if @ZEROX could find a point that did work. I think most of eveyyone who repsonded, agrees that it sounds like an mDNS issue. But the original post leaves a lot to speculation.
In the original post there is mention of installing bazzit (which I don’t know anything about) and suddenly (maybe?!?) he can’t connect to .local anymore. Then it was 22 days later before the next responce. Then it becomes a browser thing. And even my last responce was a bit wonky (maybe one too many bourbons… tiss the season).
Anyway, I was just trying to understand if something on that device, anything, did work.
I appologize if I made your issue worse, @ZEROX !!
Trying to add an entry into mDNS that the network can’t control will make it corrupt and in the end the only way to correct it again is to rewind that change and then shut down the entire network, all machine, devices and network gear.
First when everything is down can you be sure that the mDNS is fully cleared and can start things up again.