I was updating to the latest version and can't access the hub on the web UI anymore. I get an empty response like below. The updatetool responds on port 8081 and the hubitat ios app still works to pull up the dashboard. Is this a failed update I should retry or something new in hub-2.2.9.146?
I use RFC6598 space at home to avoid overlap with other things. Only mention it in case there's some new security controls (seem to be all the rage lately in other devices/software) to only allow RFC1918 space to connect directly.
Any advice/help is appreciated.
> curl <hubitat_ip>
curl: (52) Empty reply from server
Yes, it's because of the shared address space, introduced in 2.2.9 to stop people from using port forwarding to open hub UI to the rest of the world. Not that it will stop someone, but at least there will have to be some thought and effort (and hopefully risk assessment) involved.
There is an endpoint to set a "allowed" list of /24 subnets (/hub/allowSubnets?123.123.123.0,124.124.124.0), but that would involve accessing hub's web UI first. You should be able to do so from a device on the same /24 subnet as the hub itself, check the router for the list of devices that are.
@gopher.ny is there any way to turn this feature off as we have lots of different subnets like 10.0.1.0/22 which are large and we need to be able to access the hub from all IP addresses
