EDACerton

Make sure that you're switching to edit mode for the GUI: https://selfhosters.net/remote/tailscale/advanced/#advanced-tailscale-settings

Ignore everything about TCP/UDP above, exit nodes can handle UDP just fine (and I don't know where the idea "TCP is a lot more common... so you might not ordinarily notice bad handling of UDP datagrams." came from... there's lots of things wrong with that statement). It's hard to say for certain what's causing the issue in your setup. My initial hunch would be that it's related to DNS -- if your containers are set to use a local DNS server, but you turn on exit node, they won't be able to access the server. This could be remedied by adding something like this to the container's extra params: --dns=8.8.8.8

If you run tailscale serve --bg 5055 It will save it in the state file, and you won't have to run the command again at all.

I'm not going to keep discussing it. The behavior of the plugin is correct. So is the behavior of Tailscale. If you choose to create a complicated setup, then you're responsible to understand the implications of those design choices. If you think there is a better way to make the system behave, you're welcome to submit a pull request on Github

resolv.conf.head/tail means nothing to the actual DNS resolution. It's just used by the network scripts to help control when DHCP is providing DNS vs. when they're defined in the config. resolv.conf is authoritative. It always has been.

You can do this... 100.100.100.100 will respond to DNS even if --accept-dns is false.

If you're configuring --accept-dns, Tailscale is doing exactly what you're asking it to by overwriting resolv.conf. This is not a failure on the part of the plugin or of Tailscale (since actually it's Tailscale that manages that file, not the plugin itself). Writing files into resolv.conf.tail would be ineffective, as Unraid has a much simpler network architecture than other Linux distributions. There's no resolvconf or systemd-resolved, all that Unraid has is resolv.conf. Therefore, when you ask Tailscale to handle DNS, the only option that it has is to overwrite resolv.conf. If you want for Tailscale to use other local DNS servers, you can make those available on the tailnet and then configure split DNS in the Tailscale admin console: https://tailscale.com/kb/1054/dns If you want to have the host accept DNS (and therefore use the Tailscale), but want containers to use other DNS servers, you can tell Docker to use different DNS settings by adding a --dns option in extra parameters for the containers: https://docs.docker.com/engine/network/#dns-services

See here: https://forums.unraid.net/topic/136889-plugin-tailscale/page/51/#findComment-1520760

There’s an “enable” option in the advanced settings already… just disable, save, then enable again

Does your Unraid server really need `--accept-dns=true`? That's very rarely needed, and there's a reason that I keep the "Use Tailscale DNS" in the advanced plugin settings with a big warning message.

This appears to be caused by a security fix that was added in Tailscale 1.80.0. It breaks the "Login" button when accessing the WebGUI over HTTP. I'm opening a case with Tailscale for that. In the meantime, if you enable SSL/TLS for the WebGUI via "Management Settings", you should be able to complete the login. You can also open the CLI and run "tailscale up", then go to the link it gives you. I've also rolled back the "main" plugin version to 1.78.1 while I work on getting a better fix for this. I will keep 1.80.0 on the "preview" branch for anyone that wants it (1.80.0 allows Unraid to use exit nodes again, so some folks might want that).

I'm guessing that you enabled "tailscale serve" or "tailscale funnel" via the CLI with the WebGUI running on port 443 too... this creates a port conflict since you've told both services to listen on the same port on the Tailscale IP.

You could put it on br0 so it gets its own IP. If it's on bridge/host, you can't exempt it.

No.... if you've enabled an exit node at host level, everything will be routed through the exit node. I don't know of any way to exempt traffic.

Yes, I would just do an "Erase Configuration" (might need to toggle advanced settings), then wait 30 seconds and reload the page.

The plugin is still needed on 7 for the host Tailscale installation. That allows Tailscale to update without needing an OS release every time.

The docker settings are unrelated to the plugin, please make a post in the Tailscale forum for support with that.

I can look into this.

The plugin is still needed on 7 for the host Tailscale installation. That allows Tailscale to update without needing an OS release every time.

No. The docker settings are unrelated to the plugin, please make a post in the Tailscale forum for support with that.

It shows that way because TSDProxy uses tsnet (a library that Tailscale provides) to manage connections. The admin interface doesn’t have a good way to distinguish that from the “traditional” Tailscale clients, so you end up with the weird version string. For the plex UI, you might need to specify the port in the advanced settings in Label Manager, it could be trying to proxy the wrong port from the container.

Please follow the pinned post and provide plugin diagnostics.

Try going to the “Settings” tab and use the restart button there. Those errors can occur if Tailscale doesn’t start properly. If that doesn’t work, you can check the logs page, or follow the instructions in the pinned post to create plugin diagnostics.

The “Use Tailscale” option in Docker and the Tailscale plugin are two independent things. The plugin has nothing to do with the option in the Docker settings.

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. As another consideration, that’s a LSIO container. LSIO has its own Tailscale mod that will likely work better with the container: https://selfhosters.net/remote/tailscale/docker/#using-the-tailscale-docker-mod-for-linuxserverio-containers