Can't connect to homeassistant:8123

Configuration
,
21

Hi there, I am having the same issues with a Pi 4B. I can see it on the network, but can’t connect to the web service. Were you able to solve your issues?

22

FYI, I believe this was a problem with the balenaEtcher. I downloaded and used the official Raspberry Pi Imager. And was able to get it running right away.

I did have the use http://ipaddress:8123

24

Hi there, I also have the same issue

I can’t connect with - http://homeassistant.local:8123/
but it works with - http://192.168.178.19:8123/

The funny thing is that I’m not directly connected with my router but via a wifi booster power plug because I was connecting to it from the first floor.

When I went downstairs and was connected to the wifi of my router, using the first link did work. Does this have to with some kind of DNS setting?

1 Like
25

Did you end up figuring this out? I’m having a similar issue; I can connect to homeassistant.local with my hardwired pc, but not over WiFi on my phone. Only my local IP works on my phone.

2 Likes
26

I’m having the same problem. Was running fine, ran the update then it disconnected and I can’t access it now. Tried local:8123 and IP:8123

27

I’m having the same issue with my new install. I can ping homeassist.local, and everything is working fine. However, I can’t get connected to the server on port 8123 through my browser. That tells me the network connection is OK, but perhaps the server is not?

28

I ended up connecting both my computer and the Pi via ethernet to the router, i could then connect for a period of time where I initiated all the software updates and this fixed it. Still not 100% sure what the issue was, occasionally i get the same issue and a software update fixes it.

1 Like
29

I got my server up and going. Since this was my first install, I just wiped the disk image and started fresh. I think I broke something by not shutting down properly.

30

I moved home so changed also internet provider. I have another router now. I connected rasberry thorugh ethernet cable and got the ip in the rounter which is 192.168.0.38/24.

Then I tried with the ip 192.168.0.38:8123 from a computer which was also connected in the same network with the cable. It says that is not available.

I have duckdns configured, donno if I need to deactivate this:

#Uncomment this if you are using SSL/TLS, running in Docker container, etc.
http:
    base_url: xxxx.duckdns.org added:8123
    ssl_certificate: /ssl/fullchain.pem
    ssl_key: /ssl/privkey.pem
31

Hello,
I have an issue to connect to HA.
it is installed on a mini PC (VM) which is connected to network via WiFi extender.
It’s having an assigned ip in the router.
I can connect from a tablet but not from my phone.
My phone has as well installed the app which is connected to another HA installed on synology.
Before switching to mini PC I wanted to try the version installed on it (supervised version with add-ons).

32

Try this:

Disconnect all the wired devices from your router.
Only the Raspberry Pi should be connected, then try to access again.

33

I had the same problem but there were two things I needed to do to resolve the issue:

  1. The DuckDuckGo search engine that was failing the resolution. I went into Chromium and set the search engine to Google.
  2. I also needed to add 192.168.1.x HomeAssistant.Local to the end of /etc/hosts file.

That was it!

3 Likes
34

I lost access to HA in the moment I did the same configuration you mention here. Did you solve your issue? can you share how?

35

Hi, i am facing the same. Out of a sudden the connection is not working anymore

identified possible reason.

  1. IP was banned; so i changed config…yaml added trusted networks but doesnt work; set up ban ip to false
    unfortunately no effect. for a short period like minutes i was able to use the android app to connect.

But now i dont have an idea. pls dont ask for external/internal ip/dns i tried all the stuff. but only internal. which is fine for me.
when i use an vpn and get another ip it works then again.

But i dont have any idea! Maybe the best to remove HA and go back to Domoticz which worked like a charm

36

Had he same issue. My mistake was as simple as adding https://x.x.x.x:8123

6 Likes
37

This work for me:

ha core update --version 2022.8.2

banner
1 Like
38

thank you so much! spent a lot of time until i read your comment. thanks!

39

Had similar issue where I needed to log in using the 192.168.1.x:8123 (found out what the “x” was from my network’s modem page). I have a NetGear modem, which may require me to do many factory resets and that requires reauth of my DuckDNS, so I ended up abandoning them and going through a different secure server provider.

You can find the HA hub’s IP address through a program like Wireless Network Watcher or Glasswire

40

I use Home Assistant on a virtual machin Virtual Box for 1 year
I was developing some dashboards as an update for the HA supervisor was proposed to me (I accept)

Now when I start the VM hHA seems to be started correctly, give me the IP address and the URL to reach my server : http://homeassistantpc.local :8123 as usual.

information from CLI:

When I try to connect with this address I get the answer:

*Unable to connect

An error occurred during a connection to homeassistantpc.local:8123.

The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the web.

What are the reasons for that?
Is it possible to restore a backup from the CLI interface ?
Is it possible to download the backup of my application from the backup repository?..

41

I just had the same issue. It was somehow tied to duckdns that i had set up previously. When I made some changes to my config file I got locked out. I added the “s” to the http and that fixed the issue. Thank you!

1 Like