Argus9

@Kilrah @ZappyZap that's what I ended up doing too; the tailscale sidecar works beautifully. For any readers coming here with the same question: Spin up a Tailscale docker container, then change your Bambuddy container configuration's network type to "container", and then select the Tailscale container. Bambuddy will then piggyback off of the Tailscale container's connection to your tailnet. Be sure to give your container an appropriate name (i.e. tailscale-bambuddy) and make sure to set the tailscale node name to "bambuddy" so that MagicDNS works the way you'd expect. Thanks for the feedback!

Hey, thanks for packaging the app, it works great! I'm trying to enable Tailscale but the app is failing to start up when that's toggled on. The container installed tailscale and let me authenticate with my account, but after that the app just stops without any error message. Is there more setup that needs to be done out-of-the-box to get Tailscale working?

Hello @binhex! Another fantastic container build. Thank you! I'm having an issue accessing the WebGUI and I'm hoping you can help. After I start the container, I attempt to access the webgui by going to the Unraid webGUI, then going to Docker, clicking the binhex-rclone icon and selecting "WebGUI". When the new web page appears, I'm asked to log in with my WebGUI credentials I set in the docker container's settings, and after logging in, I'm taken to a page that says "404: not found". I'm on v1.69.0, and unraid v7.0.0. I've enabled Tailscale in the container settings, but I'm accessing the webGUI via the non-tailscale webGUI option in the docker page popup. Is there any other info I can give to help? Thank you!

Sure thing! Here you go. Thanks to you and @Espressomaticfor any (further) help you can provide! unraid-server-tailscale-diag-20250103-130405.zip

I've uninstalled the plugin and removed the `tailscale` folder from my plugins directory on the Unraid flash drive, and fully reconfigured the unraid server in my Tailscale account, but unfortunately, the issue persists. Now that we're past what's supposed to be the fix-all solution of starting from scratch, I'm thinking about what other info I can provide that might help, and there's a few things I can mention: - I am using PiHole in my setup. It's running as a Docker container on my unraid server, but I'm using the `br0` network interface so I can give it a unique IP address on my network. I'm also on Unraid 7.0.0rc3 and have enabled Tailscale for the pihole container, so it has an IP address within my tailnet. I've set up the DNS settings for my tailnet to use that IP address as the sole global nameserver, and have "override local dns" enabled. This works fine for all of the devices on my tailnet. - I've also enabled Tailscale for a few other docker containers on my unraid server, and they are accessible in the browser using their MagicDNS address, i.e. `pihole.foo-bar.ts.net`. So the unraid server really is the outlier here, and specifically, the webGUI, since I'm able to access Docker containers with Tailscale enabled on them. Just to be sure, I also wanted to check on the current status of tailscale DNS on the unraid server using `tailscale dns status`. This is the result, with certain sensitive data redacted: root@unraid-server:~# tailscale dns status === 'Use Tailscale DNS' status === Tailscale DNS: enabled. Tailscale is configured to handle DNS queries on this device. Run 'tailscale set --accept-dns=false' to revert to your system default DNS resolver. === MagicDNS configuration === This is the DNS configuration provided by the coordination server to this device. MagicDNS: enabled tailnet-wide (suffix = xxxx-xxxx.ts.net) Other devices in your tailnet can reach this device at unraid-server.xxxx-xxxx.ts.net. Resolvers (in preference order): - 100.xxx.xxx.xx Split DNS Routes: - ts.net. -> xxx.xxx.xxx.xx - ts.net. -> xxxx:xxx:xxxx::xx Search Domains: - xxxx-xxxx.ts.net === System DNS configuration === This is the DNS configuration that Tailscale believes your operating system is using. Tailscale may use this configuration if 'Override Local DNS' is disabled in the admin console, or if no resolvers are provided by the coordination server. Nameservers: - xx.xxx.xxx.xx - xx.xxx.x.xx Search domains: (no search domains found) [this is a preliminary version of this command; the output format may change in the future] One thing I noticed is that Nameservers doesn't have the values I expected; there's only one Global nameserver listed in my Tailscale admin console's DNS tab, and "Override Local DNS" is enabled. However, it's not showing under "Nameservers" and there's two other ones here. Does this give you any other ideas?

Thanks, I will give the full reset a try. But that last thing you said caught my attention - is the plugin bugged? Does the "use Tailscale DNS" dropdown in the tailscale settings page not function? Nevermind, I see the difference. One's for outbound traffic, the other's (I assume) for inbound traffic. I'll try setting the "accept-dns" flag to true and restart the plugin, see if that helps. If it doesn't, I'll do the full reinstall. Thanks for all of your help!

Huh. Funny enough, `tailscale ping` _does_ work, both from the unraid-server to another machine, and from a machine to the unraid server. Odd. So it seems like when we explicitly invoke Tailscale, the machines can contact each other. Is it possible that the Tailscale plugin isn't working or active, even though we think it is? I tried uninstalling the plugin and reinstalling it, but should I try a full uninstall (including deleting config files) and reinstall and re-authorizing the machine?

Looks like it's still timing out. It's the same case if I try to use nslookup on other devices on my tailnet. So something seems to be putting the unraid server in a sort of "black box" where nothing goes in or out through the tailnet to or from it.

I don't think it's just my browser. I get the same timeout issue if I ping the unraid server in a terminal: I've also tried this using other browsers on a Mac and the issue persists.

It does seem to be going through Tailscale DNS (done from a Windows 11 machine in a Powershell terminal):

The problem still affects both the Tailscale domain and the Tailscale IP address. I'm still getting that ERR_CONNECTION_TIMED_OUT error in the browser.

Sadly, changing this to "Yes" doesn't resolve the issue with accessing the webui through the Tailscale URLs. Hopefully this narrows things down though. I also tried restarting the Tailscale plugin after changing this setting to see if that would help. No dice.

Hi, thanks for your reply. The digits in the Tailscale URL do, in fact, match the Unraid IP for my unraid machine. If I try to enter that IP address in the address bar and navigate, I still get the connection timeout error I mentioned above. Same goes for the two Tailscale URLs on this management access settings page, both time out. One thing I just noticed that might be relevant: I can enter my machine's local (non-tailscale) IP to hit the dashboard, but the URL will change in my address bar to one of my Local access URLs, specifically the one that looks like this: https://192-168-1-2.asdlfkj2l34kj23of9asdflasidfjalsdfkj.myunraid.net/. It seems like it's auto-redirecting me to this URL, and I'm not sure what's doing that, or if it somehow interferes with loading the webGUI through Tailscale, but it seems plausible. Figured I'd bring it up.

Hi folks, First off, great job on this plugin! It works great for letting me connect to all of my docker containers securely from all of my devices. It works great for almost every use case. I'm having trouble accessing one thing through Tailscale though - my Unraid webGUI dashboard. When I try to access it via the device's magicDNS device name or its Tailscale IP address, I get a ERR_CONNECTION_TIMED_OUT error. I've already tried the steps in the first/pinned post about disabling subnets (they were already disabled). I've also done some research and tried a few other things, such as ensuring that tailscale1 is included under "Include listening interfaces" in Network settings. I've generated plugin diagnostics, please find them attached to my post. I'd appreciate any help you can offer to figure this out. Thank you! unraid-server-tailscale-diag-20241229-014837.zip

I can't interact with my GitLab repos over SSH. I've generated an ed25519 key pair and added the public key to my Profile > SSH Keys section. However, I'm trying to push a branch to a repo I created, but when trying to push I'm asked to enter the password for `[email protected]` (mydomain.com is a fake name here). I can push/pull over HTTPS just fine, but I'd rather use SSH for ease and security. I'm also a GitHub user and I don't have this problem with repos I try to access over GitHub. It seems like the problem is isolated to this GitLab instance. What should I do to try and debug this?