Suddenly not able to access my home assistant

Hi all,

Suddenly since yesterday I am not able to access my home assistant even though nothing has changed. I cannot access it via my app (remote connection with duckdns) but also not at home via the IP directly.

When I ping my IP I get no response, when I ping duckdns I get no response, when I ping homeassistant.local I get a response, but I cannot access my home assistant with it.

Does anyone have any idea what the issue could be, or where I could even start troubleshooting? I have backups, strange thing is I see it made a backup yesterday evening even though all in inaccessible.

I am running blind, thanks for any help.

Start troubleshooting by bringing it back online. Without any information from you (how do you run it?) it is very difficult to guess why it’s down.

This indicates that the IP you think HA is at may not actually be it’s ip address.

How did you assign the IP address to HA? Dhcp? Static address?

2 Likes

Don’t forget HA runs on port 8123 by default. Did you try http://homeassistant.local:8123?

1 Like

What are you seeing when you ping homeassistant.local? Are you getting an IP and a response?

1 Like

I remember using the function in HA to check its IP Address, always used that one to access it locally and used it as input for duckdns.

This is my response for homeassistant local:

and for the IP I always used:
image

Could it be that the IP suddenly changed? I am not so knowledgable in this area…

I’d say yes because you are getting a reply just not with the IP you think it is.

Enter this again in CMD ping homeassistant.local

You should see the IP or you can check your router for the IP

2 Likes

Thanks to your replies I was able to realize that the IP changed, I updated it in Duckdns and now I can reach HA again.

Thanks again!

It’s solved, thanks for getting me on the right track.

2 Likes

Look into making the HA IP address static in your router admin page. It will prevent this going forward. Happy you are back online with HA!!

2 Likes

Try “ping homeassistant.local -4” to force using ipv4 instead of ipv6. That should tell you what the current ipv4 address is.

1 Like

This is a good tip for next time, thank you

2 Likes

Hi, I am experiencing a similar issue here.
I’m running HAOS on a VM in ProxMox. It was working well for a while, then suddenly stopped working.
I can’t reach it’s IP anymore. Can’t ping it also.
From inside the VM I can’t ping any other IP of the network.
Strangely, I can ping it’s IP during the shutdown and startup of the VM but when the prompt of the shell shows its IP the pinging stops again.
I have restored a backup of the working VM but the problem is still there. Nothing has changed in the midtime.
Going crazy…
Thank you for any suggestion.

Update:
The problem could be related to a restore of a Full Backup from a different virtual machine. Maybe the system is trying to communicate using a different network device, not present on the actual VM. How can I check this?
The underlying zigbee system is working, it responds as if the HA automation is working

Open Proxmox > Your HA VM > Click Console.

You should see your IP displayed just below the banner

Thank you for your time.
Of course I have checked this. I can’t ping that IP and, from the console of the VM, I can’t ping any other IP of the network, gateway included and ProxMox pve included. Strangely pinging is working during start and shutdown of the HAOS VM.

Hmm weird.

Here’s what I would try (in the following order)

  • Reboot the entire HA VM from proxmox.
  • Check your router for IPs you don’t recognise and try those.
  • Mess around with the ha network commands in that console and try to assign a different IP address.
  • Go nuclear & fire up a fresh VM & restore backup.

Everything already done.
what I see, is that I can ping the HAOS VM during its boot until the network script starts.
The same when the HAOS VM shutdown, just before it switches off.

Then I’m all out of ideas, sorry.
Double check your network config in Proxmox just in case, but otherwise, I’m as lost as you are.

How did you install the VM? I used tteck’s scripts and never had an issue.

tteck’s script too.
It runs well until I restore a HA full backup.
I think this backup contains some network configurations that forbid the VM to connect properly.