HA unaccessible after IP/subnet change. But it's pingable and some addons are working also accessing to internet

Installation
1

Hi all!

I’ve read a lot during last months here and on other websites trying to figure out what can be the root cause of this… but I’m unable to fix it! :frowning: I’m really tired to try new actions without results, so finally I decided to ask here :slight_smile:

Some time ago I’ve changed my ISP & router, which forced to change old subnet (192.168.0.1/24) to a new one (192.168.1.1/24).

I’m running HA in a Raspbery running HASSIO, and it’s wired connected to the network, being configured with a static ip address.

I’ve been able to change -using command line- the old ip to the new one, and the raspberry/hassio seems to be working a bit fine. Also some addons are

Thing working fine:

  • From another PC in the same subnet I can ping homessistant.local , it resolves the correct IP (192.168.1.15).
  • Connect thru shh from localhost to 192.168.1.15 (with “ssh hassio @192.168.1.15”)
  • I can successfully other PC’s in the same subnet. Also ping the gateway, and also ping to www. google .com
  • Uptime Kuma (monitoring addon) seems to be working fine as I’m receiving telegram messages from my HA account warning me about public IP’s when they fail/recover.
  • I can work with the Raspberry using the Home Assistant command line, because I’ve connected it to a display using an HDMI cable.
  • Ports scan done from the same subnet, detecting the following ports open:

IP: 192.168.1.15
Ping: 1 ms
Hostname: HOMEASSISTANT
Ports: 22,53,111,139,443,445,1880,1883,1884,3001,3306,3765,4357,8883,8884

Things NOT working:

  • Unable to ssh from another computer in the same network (ssh hassio @192.168.1.15, gives the following error: “kex_exchange_identification: read: Connection reset by peer”). It neither works doing the same to homeassistant.local
  • Unable to access Home Assistant URL (http://homeassistant.local:3765/ neither http://192.168.1.15:3765/) from the same subnet. I receive the following error: This site can’t be reached The connection was reset.".
  • Unable to access Observer URL (http ://homeassistant.local:4357/ neither http ://192.168.1.15:4357/) from the same subnet. I receive the following error: This site can’t be reached The connection was reset.".

What’s missing to get this fixed??

It seems like the Raspberry itself works fine, and also some addons are working as expected -and connecting to internet!-, but seems that the Home Assistant or the Supervisor doesn’t get the network change well… probably is something missing to be updated in some config somewhere… ¿?
also some addonds

2

I recently changed my router as well, first thing I did is change the routers IP back to the old one (192.168.0.1 instead of 192.168.1.1) to avoid the hassle you’re experiencing.
can’t you change the routers IP back to 192.168.0.1?

1 Like
3

You SSH to the PI…are you sure you SSH to the home assistant?

4

I have a similar issue. I set up HA on a router with ip 192.168.1.254 then used it on another router using 192.168.0.1 and now it won’t boot on the original router. The htmi interface on the RP says index out of range and panic during panic after it does:

github.com/home-assistant/cli/cmd.Execute()
/home/runner/cli/cmd/root.go:71 …

followed by a load of runtime. errors.

I tried swapping the original router back to 192.168.0.1 but that makes no difference.

My backups are on the SD card, how can I get at them?

6

To answer my “how do I get at the backups” question.

I put the SD card in an SD card reader and used a RPi with desktop to mount the card. There are 4 partitions as follows:
hassos-data
hassos-overlay
hassos-boot
25 MB Volume

The backups were in a folder hassos-data/supervisor/backup all .tar files.

I still can’t get HA to boot from the disk and I am beginning to wonder if the router ip address had anything to do with the problem.