HA on different subnet to Desktop/Mobile - cannot access

Configuration
1

My HA service runs on subnet 192.168.10.0/24, all my controlled devices sit on that subnet. I am normally connected to this subnet and I have no issues.

When I am at another site, its subnet is 192.168.20.0/24. I can access everything on my 10 subnet, except HA via web(desktop or mobile) and the mobile app. I can ping the server but getting Connection Refused errors by the HA web server.

Any idea on where/how subnets are allowed on the HA web server?

2

To the best of my knowledge, there are no such restrictions on the HA web server. If you can ping it, you should be able to access it. Are you certain you are entering the correct URL?

3

thanks, I’m am certain. Im spinning up a windows VM on the original subnet so I can connect locally and troubleshoot.

4

My only other thoughts would be either an incorrect gateway on the HA server (unlikely since you say it responds to ping), or some type of firewall or ACL between the networks.

5

Check your logs on HA, they might reveal whether it’s caused to IP-ban, credentials or “not allowed subnet”

Another site ?, or Home on same Router ?, somehow you need to be more specific how you have your network setup ( even thou it might sounds “Cool” with “another site”, it’s pretty different than connected on same router, different subnet )

… Anyhow you could maybe use HTTP: integration and add "

ip_ban_enabled: true
ip_ban_whitelist:
    - 192.168.20.0/24
6

Sorry, it was light on details, I was entering the commend from mobile phone.

My HA is at my home, running on a VM. I have my parents, and inlaws and workplace on different internet connections and all have a site to site VPN, with my home as the centre hub of all the site to site VPN’s. Each site has its own subnet. This allows me to remotely manage/collect data from other sites such as Solar Arrays, batteries and network management through a single HA install, and also share other networked devices such as NAS and other streaming like services. The reason for the VPN’s is because some of the devices are LAN connected, but not cloud connected as their manufacturer is living in the 1990’s still, but they are bloody good devices, so I need a LAN connection to collect TCPmodbus data. I would prefer to live without the hassle of it, but I also brings other benefits.

Previously, when I visit another site, such as my parents, when on the wifi, I can access everything like I am at home, including HomeAssistant, as data is permitted between subnets. When I was away last weekend, I could not, and I needed to be on the same subnet. Which was wierd, as I could access everything except Home Assistant, including the Host the VM was running on, and other VM’s on that host. I was also unable to access via NabuCasa cloud, or by opening up ports on the router and doing a port forward. I could ping the HA instance, and get a response, but no Web :8123 connectivity.

Once I got home, I jumped on locally, and was able to diagnose the SSD failed (at only 3 months old) for the cache for the Virtual Disk host the VM was running on, and HA was having write errors.

Replaced the SSD and everything is back online. Then restored to a backup before the suspected time of SSD failure just in case.

I suspected the unusual behaviour was a networking issue, as I could access locally and ping the VM. But it was a disk write error. Unusual, but now resolved, but great to get a bit of insight to the IP BAN functionality.