It works, but every so often (can be as low as 15 minutes or as high as few hours) the service becomes unhealthy before immediately coming back up:
Server unhealthy for render-subnet-router
| dial tcp 10.1x.x.x:10000: connect: connection refused
Server healthy for render-subnet-router
| Server healthy for render-subnet-router
Looking at the logs, it looks like the Tailscale service is restarting at those times, which would explain why it’s briefly unavailable. However I have no idea what’s causing it to restart in the first place. Has anyone observed something similar when using Tailscale on Render?
I was actually experiencing exactly this behaviour myself for a Tailscale router I have deployed. We’ve made some updates to the repo last week including changing the service type to a background worker instead of a private worker and since then I’ve not see any repeats of the server unhealthy. If you’ve deployed directly from our repo you may find you have a new background worker service that you’ll need to reauth to tailscale, approve the subnets and hopefully things will improve,