EDACerton

Turn off “Use Tailscale DNS” in the advanced settings of the plugin.

I believe that nextcloud-aio serves HTTPS directly, you need to tell TSDProxy this. In Label Manager, click the button to switch to Advanced, and then set: Scheme = HTTPS TLS Validate = No

That's a limitation of `tailscale serve`, which is the functionality that TSDProxy uses internally. I know that the developer for TSDProxy is planning to include a workaround/solution for that in an upcoming release.

Version 2025.01.15 was just released, which provides support for the LinuxServer.io SWAG auto-proxy: https://github.com/linuxserver/docker-mods/tree/swag-auto-proxy Thanks to @illegal-deference8464 for their work to get this added!

This sounds like you're trying to use the docker integration. This is not an issue with the Tailscale plugin, please make a post in the Tailscale forum if you have issues with the integration. However, I recommend using other methods to attach containers to Tailscale that do not involve the code injection that the Docker integration employs: TSDProxy (which even works on Unraid 6): https://forums.unraid.net/topic/184654-container-tsdproxy/ Sidecar Containers: https://selfhosters.net/remote/tailscale/docker/#running-tailscale-as-a-sidecar-container

I created an upstream issue regarding the behavior, and I also just released an update for Label Manager that always sets tsdproxy.ephemeral if tsdproxy is enabled. (Previously, it wouldn't set tsdproxy.ephemeral because false is supposed to be the default, but apparently that's not working right upstream, so this should fix it as a workaround.)

This seems to be an issue on the Tailscale side... tsdproxy.ephemeral defaults to "no" (hence why it isn't added), and Tailscale shouldn't be adding those nodes as ephemeral (the only way that I know of to add an ephemeral node is with an ephemeral auth key, which isn't the case if you're using the web login). The fix for that seems to be to restart the affected container and log in again... I've only seen it happen on the first container that is connected. I'm going to open an issue upstream to see about getting a proper fix.

There is no connection between the Tailscale plugin and the option in the docker container settings.

Do you have Tailscale installed and connected on the device you are using to manage the server?

If you're already using Compose, I would recommend using either TDSProxy or Tailscale sidecar containers instead of trying to invoke the Tailscale injection provided by Unraid 7. Either of those tools are better/safer than trying to modify containers on the fly.

You should not do this. The other containers just need the labels.

I also have a new plugin called "Label Manager" coming that makes it easier to configure.... just waiting for Community Apps to pick it up.

Label Manager Label Manager adds a page to the WebGUI to easily apply container labels for services that use container labels to enable/control features. Currently, the plugin supports TSDProxy; support for Traefik is planned for a future release. Usage Install Label Manager from Community Applications. Install TSDProxy from Community Applications. In the Unraid WebGUI, open Settings -> Label Manager. Select the container to configure. Select the desired settings and click Apply. The container will be restarted to apply the updated labels.

TSDProxy automatically creates Tailscale machines for your containers without requiring changes to the container. Easy to configure and deploy, based on Docker container labels. This provides similar functionality to the "Use Tailscale" feature in the container settings, but without the problems resulting from that feature taking over the initialization of the container. Configuration Install TSDProxy from Community Applications. (Optional) Install Label Manager from Community Applications. If you choose not to install Label Manager, see the instructions to manually configure the container. In the Unraid WebGUI, open Settings -> Label Manager. Select the container to configure. Select the desired settings and click Apply. (Usually, this will just be the "Enable" option.) The container will be restarted to apply the updated labels. Open the TSDProxy dashboard to connect the container to Tailscale: Click TSDProxy on the Docker tab, then WebUI Click the container, and log in to Tailscale. Manually Configuring Containers Edit the container. In the container settings, click Add another Path, Port, Variable, Label or Device. Create a label to enable TSDProxy: Config Type: Label Name: tsdproxy.enable Key: tsdproxy.enable Value: true Create a label to make the machine persistent: Config Type: Label Name: tsdproxy.ephemeral Key: tsdproxy.ephemeral Value: false Save the container. Open the TSDProxy dashboard to connect the container to Tailscale: Click TSDProxy on the Docker tab, then WebUI Click the container, and log in to Tailscale.

It should work fine. My main server has been on the 7 beta/rc/release for a while with the "default Unraid OS" workaround. My test GRUBified box also handled the 7 upgrade with no issues.

If that Unraid box is also running as a subnet router, I think this is expected... subnet routers SNAT traffic by default. That behavior can be disabled via CLI, but if you do so you'd need to add static routes on your gateway to route return traffic correctly.

Sorry, was on my phone and couldn't get to the code block easily.

I believe you need to use tailscale set —advertise-routes “”

I’ve already been in communication with staff about this.

That is not tied to the plugin. That integration works by trying to inject Tailscale into the target container. As we’ve seen, that works in some cases, but not in all. My preference would be to use sidecar containers or tsdproxy instead of the Docker integration.

You can do that through the web interface: https://selfhosters.net/remote/tailscale/advanced/

I would continue to use the docker mod method for enabling Tailscale in LSIO containers. That will continue to work fine as long as you don't toggle the Tailscale option in the container settings.

The core of the plugin works the same as it always has. There are a couple of tweaks in the WebGUI to work better with Tailscale: If you have HTTPS enabled for your tailnet, the WebGUI will automatically get a certificate to use for the Tailscale interface. Tailscale routes are now shown on the network settings page The plugin is still installed via CA and updated via the normal plugin update process. This was intentional so that Tailscale can update independent of Unraid (Tailscale updates more frequently than Unraid does).

My initial question would be -- why are you trying to switch? If what you had was working fine / met your needs, then I would just keep it the way it was.

This is not an issue with the Tailscale plugin, please make a post in the pre releases forum if you have further issues: https://forums.unraid.net/bug-reports/prereleases/