Hello everyone, I’ve been encountering a peculiar issue for the past few days. When I try to access Home Assistant through http://homeassistant.local:8123/, it successfully takes me to the Home Assistant homepage, but I am unable to log in. It keeps saying that the username is incorrect. However, when I access it through Nabu Casa or directly via my Home Assistant’s IP address, I have no issues logging in. Does anyone have any ideas as to what might be causing this problem? Any help would be greatly appreciated!
Do you have a static IP setup?
Have you tried going directly to the IP:8123?
If you do not have a static IP then it could be changing and your DNS is causing issues.
Yes, I have a static IP setup and can access Home Assistant without issues when going directly to the IP:8123. The problem seems to be isolated to the homeassistant.local:8123 address. I appreciate any insights you might have on this matter. Thanks!
Static is good and good that you can go to the IP.
Do you have DuckDNS setup?
What happens if you go to the same address http://homeassistant.local:4357?
4357 is the observer port so try that.
If you have DuckDNS then try https://homeassistant.local note it is https instead of http
Absolutely, having a static IP is essential and offers numerous benefits, especially for home automation applications like Home Assistant. I don’t use DuckDNS as I utilize Nabu Casa for external access. I’ve tried the observer port address http://homeassistant.local:4357 and it shows that Supervisor is connected, and the system is supported and healthy. So it seems like everything is running correctly there. Still puzzled about the issue with http://homeassistant.local:8123/. Any other suggestions would be greatly appreciated!
Try it on a different browser. And then on a different device as well.
You haven’t got 2 HA’s running at once have you?
Can you try https anyways?
I use DuckDNS instead of Nabu Casa, but I will say I have had this same issue before.
It is a DNS, SSL rabbit hole I found. Once I was able to setup a redirect (hairpin) from DuckDNS URL so I could use that URL internally I stopped hunting this down. I did get it to work at one point, but it required me to turn on a feature on my pfsense that I was not comfortable with. {I just don’t remember what it was 
}