EDACerton

This sounds like you're using the Tailscale container, not the Tailscale plugin.

Please post plugin diagnostics.

Use Tailscale Subnets shouldn't break connectivity on reboot; however, how it behaves is highly dependent on the configuration of your tailnet. This setting is intended only for folks that understand what it does, and as such I've already applied several warnings regarding its use: The setting is only displayed when you switch to the "Advanced" mode. Immediately above the setting is a bold warning which states "These should generally be left off unless specifically needed." The quoted warning in this thread.

You can pass the passphrase to emcmd, but it's a little more complicated: emcmd "cmdStart=Start&startState=STOPPED&luksKey=key" Where "key" is your passphrase, first base64 encoded, then URL encoded.

I just pushed an update to the plugin that automatically applies the workaround. https://github.com/dkaser/unraid-tailscale/issues/110 https://github.com/tailscale/tailscale/issues/12108

1.66.1 is available via the preview version of the plugin. It will get pushed to the main version in a few days. For those posting about updates, please remember: I am a volunteer I have a family I have a full-time job to pay the bills I try to get to updates quickly, but there are other things that are higher priority, so sometimes the plugin updates have to wait for a few days 😀.

You have to switch to the editing mode by clicking the "Viewing" button in the web interface. Alternately, you can use the Tailscale CLI to enable exit node.

You're welcome to use my plugin as a starting point, but this isn't something that I intend to work on.

There's a misconception here. The base tailscale/tailscaled binaries that are installed via the plugin are open-source (they come from the repo that I linked, I've even submitted PRs for them to make things work better on Unraid). The Mac/Windows/iOS GUIs aren't open-source, nor is the control server (although there is Headscale as an alternative there, which does work with the plugin). None of those components are installed on Unraid.

FYI -- the Tailscale comment here is not accurate, all components are open source: unraid-tailscale (main plugin): https://github.com/dkaser/unraid-tailscale unraid-tailscale-utils (script package): https://github.com/dkaser/unraid-tailscale-utils unraid-plugin-diagnostics (custom diagnostics generator): https://github.com/dkaser/unraid-plugin-diagnostics tailscale: https://github.com/tailscale/tailscale

Did you configure a subnet router for that network? By default, if you're trying to remotely connect to a Tailscale device, you have to use the Tailscale IP, not the local IP. If you configure a subnet router, however, you can use the local IP remotely as well.

Adding a "delay start" isn't something that I plan to add to the plugin settings. Reason: using arbitrary delay values to solve race conditions is generally bad and should be avoided. Secondary reason: the User Scripts plugin can do what you're trying to accomplish, and since this is technically not a Tailscale problem I'd rather not start trying to build fixes into the plugin for other plugins/containers. Ideally, you'd want to build something smart that would run "At startup of array" which would: Wait for the container you want to be started (hint), then Restart Tailscale using the script at /usr/local/emhttp/plugins/tailscale/restart.sh Alternately, you could just build a simple wait by doing this in an "at startup of array" script (change the 60 seconds as needed): sleep 60 /usr/local/emhttp/plugins/tailscale/restart.sh

Are you trying to use the Tailscale IP or the LAN IP?

This isn’t something that I can really help with, you’d have to refer to the documentation for the containers to see how to replace the certificate that each uses.

Tailscale CPU load is usually traffic-dependent; how much are you sending via Tailscale? Otherwise, diagnostics would be helpful to see if there's something else going on.

I think I posted to you on Reddit as well... it looks like your server can't contact the Tailscale control servers.

You don’t have the Tailscale plugin installed. You’re probably running the docker container.

Did you run the restart command? That's necessary to get the WebGUI to start listening on the Tailscale IP.

There's nothing in the Tailscale logs that indicates an issue. I'd recommend trying to get some tailscale status output from both the server and a client while you're seeing a slow transfer, that might shed some light on the problem.

Run this from SSH: tailscale up Then, once you've logged in and you see the device in the Tailscale console: /usr/local/emhttp/plugins/tailscale/restart.sh

/usr/local/emhttp/plugins/tailscale/restart.sh

Yep, that's it. Install plugin, sign in to Tailscale through the WebGUI,

You are correct, switching from the docker to the plugin will require disconnecting Tailscale... the two fight each other if they are running at the same time. If you *really* wanted to try to do it remotely (not that I would recommend it), it might be possible if you get creative with the Tailscale admin console: Turn on device approval for your tailnet (Settings -> Device Management). Install the plugin and log in, but don't approve it yet. Stop the docker container (this will drop your connection to the server, but you should get it back in the next step) Approve the plugin connection in the Tailscale console. The catch to this being (of course) that if anything goes wrong you've just lost your remote connection until you have local access again. Managing remote connections in-band is always a fun process

(Stopping by because I saw the Tailscale mention and decided to check the diagnostics to make sure it wasn't a plugin issue) The good news: your server restarts a lot faster than you think. The bad news: your server is definitely restarting. Given that there's nothing in the syslog indicating why the reboot is happening, I would go back to what JorgeB indicated previously -- this seems like a hardware problem.

There used to be a button in the Tailscale web interface to do the reauth, but it looks like that is gone. I'll have to get in touch with the Tailscale folks on that one. In the meantime, you could disable key expiration via the Tailscale admin console, or use the CLI to do a reauth: tailscale up --force-reauth