That is because MDNS (Multicast DNS), that resolution of the URL to an IP address relies on, is meant to be local to the subnet. It is not meant to traverse network boundaries. Though there are ways around this. Just use the IP address.
I’ve only just started using Tailscale so had to look this up:
New here, and also interested in this as I just deployed HA at our camper. I have Raspberry Pis installed at two other locations acting as subnet routers.
I can access everything at the two locations from the camper, but from the camper I can’t get to any other remote resources.
I think I need to have my router set to route traffic to those other locations set as a ‘next hop’ of the HA IP address, but the packets die there. I suspect it is an issue with Docker networking, but not entirely sure what to do. Maybe the tail scale add-on needs to somehow be set to MACVLAN for a network type? I read a GitHub request that implies this is possible since an upgrade but I don’t see where to enable.
I am also interested in the answer to this question. I was able to get the Tailscale addon installed and setup. However, it automatically defaulted to adding subnet 192.168.0.0/24 based on what I learned from the following video, I would prefer to only advertise the specific IP address for my HomeAssistant Yellow, not my whole network.
I tried entering the following command in the Terminal: tailscale up --advertise-routes=192.168.0.89/32 but I get an error saying “bash: tailscale: command not found”