Using tsdproxy via docker compose

I am trying to set up homeassistant using tailscale and tsdproxy. I have fiddled through all possibilities I could think of, but I cannot make HA available as a ts machine, that is reachable on their ts name.

I use docker compose to setup my containers. Tailscale is installed on both my rpi and my laptop, In the admin console of tailscale, I can see them both as machines. tsdproxy is running on my rpi and is reachable under rpi.funny-name.ts. net:8080 as per default configuration.

Now I want to set up HA. I insert into the default HA compose file:

labels:
tsdproxy.enable: “true”
tsdproxy.name: “homeassistant”`

This is already enough to make HA appear as a tailscale machine.
Although I cannot reach HA under homeassistant.funny-name.ts. net. I tried both with and without https and :8123

I can reach it under rpi.funny-name.ts. net:8123 though as I have network_mode: "host" in the default config. If I take that out, I can’t reach HA at all. I already tried

  • using tsdproxy.container_port: "8123" as a label,
  • deliberately exposing ports: - 8123:8123 ,
  • putting both tsdproxy and homeassistant on the same docker network

in literally every combination possible. I am pretty sure I am somewhere messing up the networking so that tsd, tailscale and HA are just not able to communicate with each other, but I do not understand enough of this part of docker & tailscale.

What do I need to change in my HA compose file, to make this work?

Every bit of help is much apprechiated!
Thanks!

Same here, any update ?

Hello,
in the described case, you are using the tsdproxy docker provider, and you need to declare some labels on containers, who’s sucking in HA configuration.

But tsdproxy have also a list provider (Proxy List – TSDProxy) who’s simply a declarative configuration.
Just change you tsd config file to include the option, and you have access on ha, but also on any other declared web service. One entry multiple targets.

Have fun with selfhosting !

Best Regards