Moved homeassistant to new network can't connect

Installation
1

Hello everyone,

I recently moved to a new place and got a new router and internet connection. Now, when I start my Raspberry Pi with Home Assistant installed, it boots up and gets assigned an IP address successfully, but I can’t access it through the web interface. I’ve tried accessing it using both 192.xx.x.x:8123 and homeassistant.local, but neither works.

Interestingly, when I ping the IP address, it responds successfully.

Is there something I need to do in the Home Assistant CLI or any other configuration to resolve this issue? I’m relatively new to this, so any help or guidance would be greatly appreciated!

Thank you!

2

Most likely the new router is using another private ip range than the one you had, 192.168.0.0/24 vs 192.168.1.0/24 for example.

Can you connect a screen to the Pi and see that the IP it reports is the same as the one you are trying to access? You haven’t set a static IP on HA?

You don’t need to redact private ips :slight_smile:

3

When I connect the Pi to a screen, I see the same IP address as when I log into my router and check it. I don’t remember setting a static IP on Home Assistant, but I can’t find a way to reset the network settings.

4

Is the IP in the same subnet as the rest of your devices? can you access port 4357 on the same IP as your Home Assistant?

5

Yes they are the same subnet as the rest of my devices.
I get Secure Connection Failed when trying to connect to 4357.

6

Have you tried without https:// ? just http://

7

I successfully accessed the Home Assistant Observer using HTTP and the IP address. However, when trying to connect via HTTP on port 8123, it redirects to HTTPS and then displays an “unable to connect” error.

Here’s the status of the Observer:

Supervisor Connected
Supported Supported
Healthy Healthy
8

Have you set up any kind of remote access when you used it at your old network? Nabu Casa, nginx or whatever.

9

I think I set up DuckDNS some time ago, but I’m not sure if it’s still active. Could this be causing the problem? I might have also used Cloudflare to enable external access, but I’m not certain.

10

Yes I would think that is the issue. I use nginx and a self hosted domain myself so no first hand experience with DuckDNS or Cloudflare.

11

Is there a way to uninstall that from Home Assistant using the CLI, since it’s the only interface I currently have access to? Alternatively, can I reboot Home Assistant through the CLI to clear it?

I have access to my old network since It’s at my parents’ house. Would it be possible to go there, uninstall it, and then return? Would this be a good alternative?
It also seems like DuckDNS is down.

When I run ha core info, it shows an IP address that doesn’t match the subnet. Could this be causing an issue?

12

Does the non-matching IP match your previous network? One workaround could be to change the subnet on your router to match your old one (if you have access to that).

13

Unfortunately, the IP address shown by ha core info doesn’t match the other subnet either.

14

starts with 172.? If so that is not something you want to change, no.

15

Exactly it starts with 172

16

Try the IP:8123 again, but this time use httpS.

Click through the warning (in chrome it’s advanced>proceed to unsafe site) and you should be in.

When you set up Duckdns the http no longer works directly, so you have to follow the above steps to connect internally.

17

192.xx refused the connection. I dont get any warning at all

18

Automatic HTTPS is a browser “feature” that you can turn off.

19

Would it be easier to just flash the sd-card and redo?