HA only working on app, not local

Configuration
1

I have been using HA for about 4 years without issue. About 6 months a go homeassistant.local:8123 stopped working but I using the IP:8123 still worked. Now that has stopped working too but the app on my mac and iphone both still work. Also since the IP:8123 stopped working, the app also doesn’t work from my home office which has an access point in there for my home network. So i have to connect to the router in the main house that has HA on a raspberry pi connected to it for the app to work.

Pretty confused by the whole thing tbh.

2

Do you have this in your configuration.yaml?

homeassistant:
  name: HomeAssistant
  external_url: !secret external_url
  internal_url: !secret internal_url

And in secrets:

external_url: "https://flxoeefkvnotrealdksieicofoofkvisasurofkgdzd.ui.nabu.casa:8123"
internal_url: "http://home.local:8123"

(The Nabu Casa address is not real. I just let the cat walk on the keyboard).

1 Like
3

No I don’t have either!

4

Most people have this configured in the GUi now, setting it in yaml will disable the gui settings. So I’d keep it in the GUI bit check them.

Are you sure your HA instance did not get another ip from your router? Since it works from the app, I assume it uses the outside connection if the one inside is not available.

5

How can I check if its configured in the GUi?

I checked my router network and it still has the same IP for HA so that hasn’t changed. I’m using nabu casa to connect via the app.

6

Settings, System, Network.

7

What am I looking for once in Network settings? It’s been a loooong day at work so my brain is running at about 50% right now and this has been annoying me all day! Worth also mentioning we had multiple power cuts today, not sure if that could have contributed to any of these problems.

8

Sorry Ive just realised what you were saying. Yes the internal and external url’s are configured in the Network menu. The external is home assistant cloud (nabu casa), the internal is http://IPADRRESS:8123. Neither of these have been changed for about 18 months.

9

Can ou ping the ip sucessfully? Maybe some other device also tried to claim the same ip? Did you a cidentally install another server that acts as a dhcp server?

10

This is what I get when i ping the ip

64 bytes from IPADDRESS: icmp_seq=0 ttl=64 time=6.340 ms

I get the same message every couple of seconds.

11

Ok I just tried in a different brower (I use Chrome normally) and both the IP and homeassistant.local url’s work. So looks like its a Chrome issue. Does anyone have any idea what the problem might be?

12

Most probably it’s browser cache. Ctrl+F5 should fix it.
If it doesn’t, open chrome dev tools (F12), then go back to your HA browser window, right click on the refresh button & select Empty cache and hard reload.

image
image470×199 10.4 KB

13

Is it ONLY an access point or is it in fact a wireless router?

14

Just tried that and still no luck unfortunately.

15

It’s an Alta Labs AP6 Pro AP6 Professional

16

Any errors in chrome dev tools?

EDIT: Also, can you access your HA if you use incognito mode in Chrome?

17

Nope, console is clear. The page just has an error messsage “…is unreachable / ERR_ADDRESS_UNREACHABLE”

18

Check the network tab. ERR_ADDRESS_UNREACHABLE should throw a non-200 error. Click the Response for the failing request and see what the actual issue is.

Also, see my edit above - try incognito on chrome & report back.

19

Check also the monitor output on your HA installation to see if it has changed IP address.

20

Not working in incognito in chrome. The network tab looks like this with nothing in the “response” tab for the red lines

Screenshot 2025-09-15 at 19.39.39
Screenshot 2025-09-15 at 19.39.391012×298 38.3 KB