Hello,
Running an HA instance for the last 4 years without any issue.
A few days ago Home Assistant stopped working and I am unable to connect. When I try to connect via browser I get a “This site can’t be reached 192.168.1.100 refused to connect”
I can ping the HA ip on my network. Connecting both with IP and DNS name throw the same result above. Automations are not running.
When I try to connect on 192.168.1.100:4357 i get a message saying; “Home Assistant observer / Supervisor: Disconnected”.
I have checked the sd card for errors but it doesn’t throw any. I can browse the sd card files on another computer and I’ve checked for data corruption (no issues).
This happened out of nowhere - didn’t do any update or mess with it, it just stopped working one day.
Anyone has any ideas?
Thanks in advance for your help.
I have the same and i still cant fix it. I followed the directions then supervisor shut it down. Im running it barbones on a beelink. I hope there is a fix for this.
You have most likely enabled HTTPS this is why the error. I still do not understand why people try to implement HTTPS on their local network. If someone has managed to infiltrate your LAN you have more serious issues to protecting your HTTP traffic.
I did not enabled HTTPS or anything else, as mentioned on my post.
I don’t understand why people answer without reading the original post
I’m experiencing the same type of problems after upgrading to Supervisor 12 using HAOS. Web UI makes the tab crash, and using the app (Android) is SUPER sluggish.
Tried rebooting, didn’t help. Any advice?
Errors of this type: “This site can’t be reached 192.168.1.100 refused to connect” are usually HTTPS errors.
So you don’t think that is because supervisor is disconnected?
How does https gets enabled by itself?
A typical scenario with users is after years they forget what things were enabled in their instance. A certificate failing to update, which can go undetected, is reason enough for HA to refuse to connect. Other reasons are network security updates, misconfigured proxies, etc.
In your case HTTPS might not be the cause of your problems, however this type of error is usually HTTPS related and therefore my first comment, check if HTTPS was enabled in your HA instance, which might be the cause of your failure.
I did not make the comment to scold you; I made the comment to help you.
I just installed the newest version of HA, and I do not even know how to enable HTPPS. I am having the same issue has anyone set up an on GitHub? When I run the command to download HACS again, it won’t download, so I don’t know what to do. I’m a complete beginner. Where would this be downloaded so I could not download it and try to install it through SSH again?
If you are running HAOS try this guide for HACS, you might be successful.
A clean install on the x86 platform will NEVER create issues, unless you are running on marginal/obscure hardware or are skipping installation steps.
Try my guides, you might be pleasantly surprised. My focus is HAOS on x86 platform bare-metal or virtualised. I maintain more than 100 instances with no issues.
I have also been experiencing this for the last few days. Been running HA in HA OS for several years. Only recent changes i can think of is an update of HA and HA OS. It happened one yesterday and twice today.
I do not have https enabled in HA. I do have https proxy though so that i can link it to Google Assistant but when this happens, i don’t get any response from http://[IP]:8123 either. If it was related to https, why would automations stop working?
Restarting HA OS solves it for a while. HA IP is still responding to ping.
Edit:
Forgot to mention that i run x86 on a virtual machine. VM is still alive and i can still interact with it in the console.
Edit2:
Won’t even reboot nicely:
Asking the VM to restart from ESXi does work but takes a very long time, while waiting i’m seeing this in the console:
No Home Assitant worked great took the out SSD of my beelink put it in an external case and flashed it that way. Booted up perfectly the first time. When I ran the command for HACS it told me it was successfully downloaded. Then a message came up from the supervisor I forgot exactly what it said but it was not allowing me to install it. I went into intergrations and no hacks. And’ve tried running the command again and it won’t download probably because it already is. Idk where to delete it so I can try to download it again. But I’m so confused at why the supervisor would shut it down like all these other people are saying happened to them. Edit: Reading his issue it’s not the same the supervisor is just telling me I can’t install HACS and it won’t install.
I suggest try my guide and let me know if it worked for you.
That is not usually HTTPS errors, that means that nothing is listening on that particular port.
Anyway, chirpin in and confirms that this hit me today too.
Supervisor “died”:
Tried to rebuild it but found that the docker-network does not even route correctly anymore:
Post "http://supervisor/core/rebuild": dial tcp 172.30.32.2:80: connect: no route to host
Hello ladies and gents. My first post here after reading and trying so many possible solutions but the problem persist.
I have the same issue. I have tried a fresh install which reports no error until you start HA then error Login attempt or request with invalid authentication from 172.17.0.3 (172.17.0.3). See the log for details.
Perhaps the problem is in the new version of Docker and you need to roll it back
sudo apt install
docker-compose-plugin=2.21.0-1~debian.12~bookworm
docker-ce-cli=5:24.0.7-1~debian.12~bookworm
docker-buildx-plugin=0.11.2-1~debian.12~bookworm
docker-ce=5:24.0.7-1~debian.12~bookworm
docker-ce-rootless-extras=5:24.0.7-1~debian.12~bookworm
The downgrading of Docker packages worked for me in x86_64 and aarch64 Debian GNU/Linux 12 systems. Thanks!
I am running Docker version 25.0.0, build e758fe5, on debian 11. Can you please advice how to downgrade?
My Home Assistant observer says that Supervisor is disconnected. Do you maybe know how to connect?
thanks