Sometimes machine not reachable in Tailscale network

We have a Home Assistant instance running in the office. I use Pixel 5 on latest Android to access it and it works fine.

However a couple of colleagues use Mi 3 (Android 11, Tailscale 1.16.1) phones and once or twice a week they notice that it is not possible to reach Home Assistant via Tailscale (we use Home Assistant to open gates).

Usually the workaround is to turn off Tailscale and turn it back again. That does not always fix the issue, but after a couple of toggles it starts working.

What information would be useful to report from an Android phone when we notice Tailscale network not reachable next time?

On the desktop platforms it is possible to send a bugreport which helps locate telemetry to focus on, but this doesn’t fit in the UI of the mobile device platforms.

As exact a timestamp as we can get, with timezone, along with the Tailscale IP address of the device which cannot connect would be most useful.

The ideal would be if the device works, and then a short time later does work, as it gives us a relatively small amount of telemetry to dig through looking for clues.

Okay. So here is the timeline and more details from yesterday.

Couple of minutes before 2021-11-11 11:50 UTC Pixel 4a device with Tailscale account0 having IP address was not able to access Home Assistant device on Tailscale account2 having address

Shortly after we tried to reach the same Home Assistant from Mi 3 android device with Tailscale account1 having IP address That was also not successful. Then we tried to toggle Tailscale connection off and on in the Tailsale app. After first toggle Home Assistant was still not reachable. After second or third try connection to Home Assistant started to work.

account2 has Home Asisstant device shared with account0 and account1 via Tailscale Admin panel.

We are working on the internal issue which has the same symptoms as you described in your email. We will notify you once this issue is fixed and then you can try again.


I am seeing a similar behaviour. Was the fix implemented ?

Would you please try Tailscale version 1.18.1? if you still see the issue, please share the tailscale bugreport when issue happens and the Taiscale IP of both ends on