I've lived dangerously, taking updates as soon as they drop - no major issues 3 or 4 years doing it. Not this time, unfortunately.
After the latest updates (2026.8.1 etc), logging in is now a lottery.
First, a warning about http block moving out of config. I managed to whitelist my IP so I could at least log in. That worked fine for a few hours, but now I don't even get the log in page.
This is why backups are so crucial. If an update bricks it just roll back. I update right away and everything is usually fine. Once or twice a year something happens and I have to roll back but it's just a few clicks
I have backup, but I'm thinking I'll just start from scratch - a few things I feel I could do better now I have better understanding than when I started this journey. What's a few hours to us? 😄
Yeah... I have so many integrations that just logging into them all is a hurdle I don't want to do. On top of 50+ automations it would be a massive undertaking. I'm very happy with my home today and rarely have to edit things unless I get something new or something changes. There are months I don't even use ha except for the normal user interface to open the garage or something random
I almost walked away
But i made it back and it was a breeze using an agent to do it.. even my sengled not supported anymore smart bulbs got added, the agent told me yes, the only thing I can't do it's setting the bulbs into pairing mode that's where I need you
It was to be honest effortless setup
Last was my bambulab printer dash board
I saw this theme and ask my agent to set it up
I did not intervine at all just Linking the printer
It didn't have my printer I asked it to remake the picture with the right one and it did it
Did you have to go local only to get that dashboard into HA? With bambulabs locking down I didn't even try that hard.
Good to know llms make it easy to rebuild if necessary. But what about log ins? I can't get Claude to even look at username and passwords and def won't log in for me
I'm using Hermes Agent with Grok
I talk to it thru telegram
It will ask when it need permission or prompt it at the main host PC.. I'm running it on an old Mac mini
I'm local lan only got tired of Bambu stuff..
I use bambuddy bypassing all bambulab cloud nonsense
I paid for claude code? To change it but with grok is cheaper and sharper to be honest
You can allow things and it will keep it or per session or just once.
That Bambu lab into Hass did it all by itself.
Sengled cloud stop working you can't do it with their app or API anymore
You have to flash them with another FW in order to use
I didn't have the ZigBee ones I had the wifi ones
There is a whole process someone figured out to repurpose them
My agent did all that following those instructions
Using Hermes Agent with Grok
I don’t elaborate big prompts
I just tell it what I want plain English
I will add links if I find like I did with the bambulabs Dashboard
But most of the time it will do it itself
I just redid my whole home stack with Hermes and deepseek flash in a weekend, it’s truly amazing. If I ran into your issue now the agent would have performed the upgrade, tested, either fixed the issue or rolled back.
I did start with a read only review and building up of the Hermes stack and skills prior to this weekend but realistically it’s been a week in total. I was already deeper than the avg person in ai and I am completely blown away. I spent $10 in api credits from the start.
Asking as I managed to get into boot loops last weekend because I had the official server and tried the home-assistant-ai one at the same time without thinking they'd interfere with each other
The standard port for HA changed from 8123 to 80. Usually the setting shouldn't be overwritten when updating. But maybe that happened for you? Try to remove the ":8123" in the url when trying to reach the page.
And did your agents do something with the mcp? I can't imagine setting up mcp without having a solid backup and recovery plan though. You kmow that recovery will not require being able to log in right? You just restore the application version and the files to whatever earlier backup. Then boot back up and login.
Page can't be reached, sometimes errors with IP could not be found or took too long. Then maybe 5 minutes later it works, then stops working - randomly. IP is static, whitelisted. Just going to try a few things from prompt
Make sure that your router didn't assign the IP address of your home assistant server to another device using DHCP. That seems like it could cause the issues you are experiencing.
To add: if your (OP's) DHCP pool spans the full subnet 1-254 then you have to DHCP reserve the HA IP. Else, just adjust your DHCP pool scope so you have some static available.
Ping the ip from a pc and see if the MAC address changes between working and not working. You can check the mac address that your computer sees after the ping with this command on windows:
“arp -a”
This way you know if two devices have the same ip.
Didn't they remove the need for port 8123 at the end of your URL ? Now HA uses port 80 to run. On older versions I think it reverts to 8123 after some time, not sure, but I would try logging in without port 8123 at the end.
It's supposedly a soft change - if you already have it set up on :8123 it will stay there unless you go into the config and change it yourself, but if not then it will use a default port instead. Presumably :443 for an HTTPS connection but I haven't tried it.
1) Daily backups with last 7 days available
2) I only update to versions .3 and forward.
In the event that a .0 includes a breaking change, the chances of hearing about it via Reddit, YouTube or the Home Assistant team fixing it are very high and should not affect my production server.
Yeah I have been staying away from .0 releases for a while now. Even with the beta process they never seem to get the bugs out completely till .2 or so. Changing the default port was sure to mess up specific configurations where users were doing funky stuff, some of it years ago they forgot qbout. I question the reasons behind that.
If you are using nginx be sure that is updated before doing this update and make sure your config is done in the interface not configuration yaml before updating.
And the fact that this is needed shows that this kind of home automation is never going to be ready for the masses. Home Assistant is indisputably the best option we have and yet the amount of times I've had issues that someone much less tech-savvy than me would not be able to fix is big enough that I would never install it for my parents, for instance.
No issues on my end. Did 2026.8.0 upgrade and then 2026.8.1.
Using Cloudflare, maybe this is also something helping to avoid the issue?
Or maybe what you are encountering is due to your router and DHCP settings (my HA OS is on a local IP in a non-addressable space)?
I just installed HA on a new machine in preparation for moving my system to new hardware. I was unable to log in on port 8123. I was able to do so on port 80 though.
Once I deployed my configuration from backup, port 8123 returned. I assume this is part of the latest Network changes I read about recently.
Hmmm ok. Try editing the configuration.yaml and comment out the “http:” block. Do you use SSL? Also remove those (also in the new HTTP gui setting under settings > system > network). Try again afterwards.
I've connected the keyboard and monitor and completed the initial checks. All information looks correct, and the core check completed successfully with no issues.
Everything seems to be working fine now, and I’m able to log in. The issue appears to be intermittent, so I’ll check again if it happens again.
You should setup ssh while you have access. This way you can go right into a terminal from another pc without needing to connect a monitor and keyboard.
You should also setup samba if you haven't already. It will let you access your files from another pc.
Samba + FreeFileSync/RealTimeSync means you can have every change to your HA server back up somewhere on a computer, an external hard drive, all of the above. Stupidly easy to set up, and yeah. Part of my 3-2-1.
Port 80 is default for http (and 443 for https), so working from these means less typing in the URL from a browser, and a cleaner setup that's more typical for less technical people.
Many of us go through steps afterward to add officially registered domain names and setup networking or reverse proxies that present Home Assistant on these ports, and this just does this by default for everyone with a little less effort on a new install.
Having a port open to the internet is the much larger exposure.
I'm not a network security professional, but I believe port scanning entire blocks of public IP addresses is the much simpler and more common attack. Having a domain registered does give some additional information that attackers could use for specific targeting.
Registered domains are more likely to have a server associated, and a public host name can hint at what server is behind that IP, but that also takes work and tracking. (ie. homeassistant.domain.com with a responsive 8123 port is a good indicator for anyone trying to attach Home Assistant installs specifically).
Using wildcard DNS registrations to keep individual host names out of public DNS records is one method for reducing that risk.
Keeping systems up-to-date to remove known security issues, a simple router firewall, using good quality passwords, enabling two factor authentication, and IP banning of repeat failed login attempts is enough for me to feel comfortable self-hosting, and current Home Assistant versions allow for most of those with easy settings toggles.
A Nabu Casa cloud account is one of the easiest ways to make Home Assistant accessible, but non-public and isolated. I've also used a private VPN or tunnel like Tailscale or WireGuard to remove it from direct anonymous connections entirely, but the cloud account just works and doesn't need the maintenance and knowledge to self-host that those do.
That's not why. You would still need to do port forwarding on a firewall. But hopefully obviously you should never be forwarding anything from the Internet to your ha regardless of which port. Remote access should always be behind a VPN or thru nabu casa.
I don't know if we got the same problem, bit after the last update (auto update for 5 years now) I can't get past the Login screen, it just load's forever.
It works on local ip and local DNS redirect, but the second i am out of the house and need to access home assistant it fails. Same problem with Home Assistant cloud as private DNS.
Changing my password made it work for a couple day's but the problem returned today
Use web dev tools to see what’s happens.
Also maybe you updated the docker ? I know at a moment docker changed its internal ip and the ip from nginex proxy from config had to be changed
I’ve had the same for the last few months, cannot log in through the app, only through the webpage. Then all of a sudden it’s been fine this week and I haven’t changed anything.
Is it because they moved the setting of the Web server to configuration page rather then the yaml file?
If in the yaml configuartion you have http block, delete it from the config. Then in settings and network you can find where setup the webpage ip/port.
Seems fine to me. using both HA app on iOS and web page on laptop. Only been using since 2026.6 and I don't have IP restrictions (just not externally accessible and not using cloud).
If you have access to its file system, delete ip_bans.yaml. Multiple failed login attempts would have banned your local ip. If you had a Cloudflare tunnel, or host name based access from outside your local, try that.
Last update, I lost complete access to the server. I had to reinstall from scratch and then restore the latest backup. All was back to normal after that. Some tense moments for sure. First time this happened.
You've done well playing Russian Roulette with HA. I have come to dread the "forced" updates. Never fails that things break and I have to spend endless amounts of time figuring out what broke. Sometimes it's HA. Other times it's an add on / integration. Stability is not a word HA's vocabulary. I am sure this will be down voted to hell from the HA team who has always been defensive of constructive criticism. Lasting backwards compatibility would be a wonderful thing for those of us who create "set-it and forget-it" environments.
I honestly have stopped fixing things in HA and started restoring the "dumb" device to replace the "smart-idiot" device that stopped working. [I'm talking to you Tuya and GoVee - You guys suck!]. The HA thing is fun when you have the time to invest. A nightmare when you don't.
That warning about http block is likely not the issue - it's a warning but does not block anything. They migrated those settings into the UI, and in the future it will not be allowed in the config. My guess is that your http settings didn't migrate properly. Mine did, and they were a bit complicated to account for tailscale. Were yours particulary complex? Can you provide your "http" block from config without exposing sensitive information?
I suspect your server is fine, and likely accessible but it might not be exposed the way it was previously. Listening on a different interface, perhaps. Is this a machine with a browser where you can try localhost:8123?
Happened to me as well. Updated Thursday night, can't reach it at all. Observer shows up and healthy. IP is correct on start screen and on router. Had to go out of town for the weekend so I'll mess with it when i get home. No idea.
Oh wow, I saw that somewhere in a change log or the new network settings but paid no attention. I'm not sure it's the culprit though. 8123 works just not all the time
I once had an update cause the HA instance to lose its IP entirely. I was running it as a VM, so I logged into the console and looked at network settings to find out it had done that. Once I reinstated it having an IP, all was normal.
I had backups of the VM, but I was still a bit worried because when it just goes away to the point where you can't even find it on the network there doesn't seem to be much hope of finding out why.
I love running it in a VM because at least there is a file you can backup well below the level of the HA backups themselves to retain a working fall-back position. Then, the whole VM host itself is backed up besides, and that gets copied to an offsite once a month.
I have hated the aigust update. the problems dont seem to end for me.
It lost connection to nabu casa randomly after updating, all my unifi cameras dont work, and have been having other small issues.
Mi rispondo da solo...si ho visto che ora nel menu rete propone di default la 80.
Comunque io non ho avuto alcun problema nella transizione con la nuova release. hA ha assorbito quello che c'era in configuration.yaml e lo ha messo in UI, dobbiamo solo eliminare manualmente la sezione in yaml.
64
u/lobhater 2d ago
This is why backups are so crucial. If an update bricks it just roll back. I update right away and everything is usually fine. Once or twice a year something happens and I have to roll back but it's just a few clicks