I’m not sure if this is the correct place to put this question. I have Home Assistant running on a Pi 4 with an SSD and it has been running fine for quite some time. Today, I installed a new network. I replaced my old Google Mesh Wifi with a new Ubiquiti network setup. I had to put an access point next to the Pi so I could use the passthrough wired network port. The AP is connected to the network via wireless mesh to a wired AP. When I boot up the HA server, it will boot and get an IP address, but doing an IP scan, I normally see the ports that are open and I can get to the webpage by going to ipaddress:8123. But after moving to the new network, I see no ports open on that IP and I can’t get the webpage to come up. Was wondering what I can do to troubleshoot this. I’m not much in Linux, but I can make out ok with detailed directions. Hopefully someone has seen something like this before. Just wanted to upgrade my home network and get better connectivity, but it seems to have hosed my HA server. Just as an additional note, it was working this way before through the Google Wifi system. The HA server was connected to the network port on the Google Mesh AP and worked fine. I’m doing basically the same thing with this new setup, but it’s not working now. Any help would be appreciated!
As a test, I took my HA server and moved it to a direct wired switch to see if the problem was due to being connected to a mesh AP. It received the same IP, but still no ports are being exposed. The web interface still won’t come up. Is there something I could do with SSH to see why my server won’t completely come online on my new network?
It appears that automations are still running even though I can’t get to the HA server. I just got a notice on my phone that the mail just arrived which means that automations and notifications are working. I just can’t get to the web interface of my server. Very strange.
Thank you for your reply! I’m using an IP scanner tool to scan my network and the Pi’s host name is homeassistant, so yes, I can see the IP address. It’s a different network so it has a different IP than it had before on my old Google network. I can even ask Alexa to turn on lights and turn off lights and that works! I just can’t get to the web interface on the Pi and can’t see any ports open like I usually do. I will get a keyboard and monitor attached and see what I see. I’m not very good with Linux, so I haven’t done that yet…
Yes, sorry. I mean I’m trying to get into the HA web interface. From another device. I should be able to just put in 192.168.1.52:8123 and open the web interface, but that isn’t working now.
Sounds like port isolation is turned on. (usually used on a guest network to keep clients from seeing each other)
Your UI gear is WAY MORE capable and complex than your Google gear. Virtual networks, port isolation, on and on. There’s tons of things your UI gear could be doing to protect you - from you…
I may have just determined that I’m an idiot. I was not putting HTTPS:\ in front of the ip address. I did that, and now the GUI shows up and I can login. I’m definitely an idiot. So sorry to have wasted your time, and thank you for your suggestions. I did try to hook a monitor up (for the first time) and was not able to get it to come up. I found an HDMI to micro HDMI cable and hooked it to my monitor and to the Pi and rebooted the Pi. But it did not see anything connected at the monitor and I never got a signal. Maybe the case is too thick and the cable was not able to be inserted far enough? Not sure, but it looks like I’m good again.
)