On 5/5/2025 at 3:33 AM, Calidor said:

i has the same Issue, The AIO Container Interface loop, I use the TSDProxy as well. With Funnel (with Label Manager) i make the Nextcloud AIO accesable for the Internet, works but loops.

 

Solution was TSDProxy change from Latest to Next. Now it works fine.

I had the same issue too! Anyone hv update on this?

On 5/2/2025 at 6:59 AM, EDACerton said:

snat-subnet-routes is for subnet routers.

 

TSDProxy / tailscale serve is actually a reverse proxy. What you should be looking for is the X-Forwarded-For header that gets added to the request.

I see, thanks for the clarification.

With that said, can TSDProxy support this functionality? No combination of adding the X-Forwarded-For variable to the TSDProxy Docker container is allowing any of the containers under the proxy to grab the "real" IP address.

I understand the X-Forwarded-For header is just HTTP, and setting it up with NPM/SWAG/Traefik is simple enough, but none of the configuration documentation for TSDProxy that I have seen suggests this is possible with TSDProxy.

Thank you so much for this! Are containers that are set up with this able to advertise as exit nodes? This is a feature I would really like to use if possible.

Can I put my own domain via this? Like nginx.mysite.com for original tailscale.domain.com?

Trying to get this working on Linkwarden container as a funnel. Container shows connected and "funnel" in tailscale dash. Here's my label config:

Any advice? I can't connect to this container via tailscale funnel, or just via my regular tailnet. But local IP works fine. thanks!

Figured it out. Needed scheme to be: HTTP, and TLS Validate to be: No.

Edited September 8, 2025Sep 8 by akshunj
removed another question I answered myself

Is this docker depreciated? Still runing 1.80 from 6 months ago.

1 hour ago, Gragorg said:

Is this docker depreciated? Still runing 1.80 from 6 months ago.

It is still fine to use. 1.80 is the tsnet version (programmers version of Tailscale), it doesn’t usually need to update like tailscaled does.

Does this work both ways? I'm trying to setup zabbix with tailscale, and my host can connect to zabbix-server using this method, but server cannot see host (cannot ping it, do not detect it)
So I guess it is only one way connection?

On 8/7/2025 at 1:23 AM, dontelother said:

Can I put my own domain via this? Like nginx.mysite.com for original tailscale.domain.com?

Would love to know the answer here, in case anyone else has run into this.

I can't seem to install this container (see attached)

does anyone know what im doing wrong?

Invalid Hostport 88080, i think thats the reason.

My connections are crazy slow. Not sure what is happening but I use tailscale all the time without issue except in this case. Haven't been able to determine a cause but I can connect via unRAID tailscale option and I don't see the insane amount of lag I'm seeing with TSDProxy.

Edited February 18Feb 18 by BrandonG777

unless your funneling, your client machien also needs to client conect to teh tail net to access the application.

see also
https://forums.unraid.net/topic/190620-docker-compose-enable-tailscale-funnel-for-docker-uses-tsdproxy/

Edited February 18Feb 18 by bmartino1

1 hour ago, bmartino1 said:

unless your funneling, your client machien also needs to client conect to teh tail net to access the application.

see also
https://forums.unraid.net/topic/190620-docker-compose-enable-tailscale-funnel-for-docker-uses-tsdproxy/

all client machines have Tailscale. I understand how Tailscale works and use it everyday without issue. TSDProxy or how I have it configured is adding so much latency, the containers are unusable but they do connect.. if I give them 10 minutes to load up. If I connect a container via unRAID Tailscale option, lag is minimal. Has to be some sort of routing/DNS issue I'm thinking but I'm struggling to identify the cause.

Just now, BrandonG777 said:

all client machines have Tailscale. I understand how Tailscale works and use it everyday without issue. TSDProxy or how I have it configured is adding so much latency, the containers are unusable but they do connect.. if I give them 10 minutes to load up. If I connect a container via unRAID Tailscale option, lag is minimal. Has to be some sort of routing/DNS issue I'm thinking but I'm struggling to identify the cause.

your configurations are bad and off I have ver minaml latecy if any at all... But I also have Fiber internet i don't have to wait at all for my services over tsdproxy via CA,. compse etc...

that is entrely configuration and per client internet bandwith...

Well, looks like there is some sort of overall Tailscale issue with my unRAID server. Even the built in containers are experiencing the lag. I suppose playing with my Tailscale options/routes is first order of business but will need to wait until I get home tomorrow before I do all that.

Is it normal to be accessible via tailnet magicDNS but not IP using TSDProxy? I can't figure out how to use IP instead of ts.net

Use this Settings on local Lan Machines, than you can use Ip´s, with magiDNS only Names works on my local Machines.

Edited March 17Mar 17 by Calidor

Updated this, and see is running V2 now. Now having issues, nothing I try to run through it will connect, logs showing errors.

I see they have information on the site about upgrading from V1 to V2 https://almeidapaulopt.github.io/tsdproxy/docs/upgrading/from-v1/

V2 is broken for me as well. Deleted the tsdproxy.yaml and docker was able to start and webUI works, but not able to connect to any of my services running through TSDProxy.

V2 is broken for me also. I removed the tsdproxy.yaml and started tsdproxy like @Tethgar . I compared the old tsdproxy.yaml file to the newly generated one and it looks like a bunch of the settings have uppercase letters added to them. Otherwise the two files are pretty much the same. On my tailscale list of Machines, they are showing the green dot now, but I cannot connect to any of them.

From tsdproxy.yaml

defaultproxyprovider: default

to new tsdproxy.yaml

defaultProxyProvider: default

There are sever others that have been updated as well

targetHostname:, controlUrl:, and proxyAccessLog:

and these have been added:

tryDockerInternalNetwork:, and preventDuplicates: (both are set to false)

Label Manager is not working correctly either, probably due to the same issue.

This broke for me as well with the latest update.

Any solutions in sight yet? Or a temporary workaround?

I just installed the latest version of TSDProxy and it fixes the Label Manager issue,but I still can't access my sites/

I can also confirm that this broke for me also with the new update to Unraid OS Version: 7.2.6