May 12May 12 Same story for me, v2 of TSDProxy as is seems like it's a breaking change for Unraid users at the moment. Reverting to latest stable v1 (setting TSDProxy Docker repository to almeidapaulopt/tsdproxy:1.4.7 and reverting the tsdproxy.yaml file to previous version) gets everything back up and available for me. Reading the changelog it looks like there's a lot of good useful stuff in v2, look forward to getting this fixed and able to upgrade.
May 12May 12 Author So, long story short...The author of TSDProxy disappeared for a year, then came back and suddenly dropped v2, which completely breaks every existing config. So Label Manager doesn't work with it anymore, existing labels need to be rewritten for the new format, etc.I'm not quite sure what my plan for this is going to be at this point. It might be to try to update to support TSDProxy v2. It might be to recommend tsbridge, and to add support for that to Label Manager.
May 12May 12 Everything is down and no idea how to fix it. Followed the migration guide to the T and still doesn't work.
May 12May 12 7 hours ago, Joe Friesen said:Same story for me, v2 of TSDProxy as is seems like it's a breaking change for Unraid users at the moment. Reverting to latest stable v1 (setting TSDProxy Docker repository to almeidapaulopt/tsdproxy:1.4.7 and reverting the tsdproxy.yaml file to previous version) gets everything back up and available for me. Reading the changelog it looks like there's a lot of good useful stuff in v2, look forward to getting this fixed and able to upgrade.Thanks for this. I am working on mine now, hopefully my stuff will be available again soon. Have to remember what settings I used in the past for Plex
May 12May 12 6 hours ago, EDACerton said:So, long story short...The author of TSDProxy disappeared for a year, then came back and suddenly dropped v2, which completely breaks every existing config. So Label Manager doesn't work with it anymore, existing labels need to be rewritten for the new format, etc.I'm not quite sure what my plan for this is going to be at this point. It might be to try to update to support TSDProxy v2. It might be to recommend tsbridge, and to add support for that to Label Manager.Fair enough, just do what is best for you with all this
May 12May 12 After a good bit of trial and error I managed to get version 2 to work. I left the TSDProxy container settings and the labels that I had set on the other containers untouched. I modified the yaml and had to reauthenticate each "machine" to the tailnet but it's working without a problem now. I also have the TSDProxy container running through TSDProxy as before, which is handy to use as a kind of dashboard. Here's my updated yaml if it helps.defaultProxyProvider: default docker: local: host: unix:///var/run/docker.sock targetHostname: host.docker.internal defaultProxyProvider: default tryDockerInternalNetwork: true lists: {} tailscale: providers: default: controlUrl: https://controlplane.tailscale.com dataDir: /data/ http: hostname: 0.0.0.0 port: 8080 log: level: info json: false proxyAccessLog: true
May 12May 12 15 hours ago, Joe Friesen said:Same story for me, v2 of TSDProxy as is seems like it's a breaking change for Unraid users at the moment. Reverting to latest stable v1 (setting TSDProxy Docker repository to almeidapaulopt/tsdproxy:1.4.7 and reverting the tsdproxy.yaml file to previous version) gets everything back up and available for me. Reading the changelog it looks like there's a lot of good useful stuff in v2, look forward to getting this fixed and able to upgrade.This also fixed it for me, thanks!
May 12May 12 Thanks @Joe Friesen for the link to older version. I now have an issue where my links show up. But my links no longer work to my shares.. sonarr.tailf****.ts.net. It worked fine before. Been playing for around rsh. Wondering if my tailscale config is correct.. See pic..
May 22May 22 I've also encountered the issues and have reverted back to :1.4.7 .It appears that :latest is using TS 1.98.1, as this is what my Tailscale dashboard shows for the machines when running v2/:latest of the proxy.The TS RN's say:LinuxNote: 1.98.1 introduced a regression in the interaction between Tailscale and MagicDNS on Linux. The Linux release has been withdrawn pending a fix.I'm wondering if what we're seeing is related to this? Maintainer has already checked-in an update to TS to 1.98.2 as of last week, but it doesn't seem as if it's been released to :latest (yet). Edited May 22May 22 by jmaino
May 23May 23 I missed some of the detail prior to my earlier comment.But, I now also have v2 working by following @Endling 's suggestions and edits to the config file.The 3 changes I needed to make in mine from v2's default were: targetHostname: host.docker.internal defaultProxyProvider: default tryDockerInternalNetwork: trueOnce these changes were made, I was up and running properly again using the :latest tag on TSDProxy.
May 24May 24 On 5/23/2026 at 8:45 AM, jmaino said:I missed some of the detail prior to my earlier comment.But, I now also have v2 working by following @Endling 's suggestions and edits to the config file.The 3 changes I needed to make in mine from v2's default were:targetHostname: host.docker.internaldefaultProxyProvider: defaulttryDockerInternalNetwork: trueOnce these changes were made, I was up and running properly again using the :latest tag on TSDProxy.Thanks for this and thank you @Endling , it's working perfectly. I have no idea what these changes do, but it looks like it shouldn't be problematic long term?
June 5Jun 5 For mine, those three changes almost got me there. For targetHostname: host.docker.internal I had to change host.docker.internal to my server's actual LAN IP (like 192.168.x.x). That's when mine worked. Note I am on :latest
June 20Jun 20 Thanks @Endling. I'm actually using the CA template and the :latest tag on TSDProxy. In the tsdproxy.yaml the targetHostname was already set to 172.x.x.x, so I didn't change it and the defaultProxyProvider was also set to "default". I just changed tryDockerInternalNetwork to "true" and it's up and working with Label Maker.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.