On 4/21/2025 at 5:51 PM, EDACerton said:

What do you mean by "not seeing the Tailscale Plugin Webgui"? Is it not showing up under Settings -> Network Services?

 

I've just installed the plugin and am not seeing the Tailscale icon under Settings -> Network Services. On Unraid 7.0.1.

EDIT: Scratch that...Rebooted the server and now it is showing.

Edited May 23, 20251 yr by dukedevil0

Hi all,

Looking for a bit of help with my setup - using the Tailscale plugin and TSDProxy to label things up.

All settings are default on the Tailscale plugin.

On the Tailscale control panel, MagicDNS is enabled (required for TSDProxy - that won't start without it), as is HTTPS.

Currently, I can reach the Unraid server GUI, and the GUI of various dockers using tailscale unraid IP:PORT using a subnet. However, the magicDNS version (i.e unraid.tailscale.ts.net) does not work, it just throws an error saying DNS probe possible.

Allow Tailscale DNS is set to No, as is Allow Tailscale subnets, there are no exit nodes, and no funnels set up.

Using TSDProxy I am able to authenticate various dockers, and successfully ping them, their GUI remains inaccessable, throwing up either SSL errors when looking at the IP (this defaults to https://IP if relevant, and I can't get the http version to load) or DNS errors when using the magicDNS name.

I almost certainly have a DNS setting incorrect somewhere, but I've tried what I think are all the TSDProxy label combinations to no success including defining the container port, so I'm hoping one of you will call me an idiot and tell me I've missed a setting somewhere!

Thanks all

On 5/30/2025 at 12:27 PM, cut_chemist said:

Hi all,

Looking for a bit of help with my setup - using the Tailscale plugin and TSDProxy to label things up.

All settings are default on the Tailscale plugin.

On the Tailscale control panel, MagicDNS is enabled (required for TSDProxy - that won't start without it), as is HTTPS.

Currently, I can reach the Unraid server GUI, and the GUI of various dockers using tailscale unraid IP:PORT using a subnet. However, the magicDNS version (i.e unraid.tailscale.ts.net) does not work, it just throws an error saying DNS probe possible.

Allow Tailscale DNS is set to No, as is Allow Tailscale subnets, there are no exit nodes, and no funnels set up.

Using TSDProxy I am able to authenticate various dockers, and successfully ping them, their GUI remains inaccessable, throwing up either SSL errors when looking at the IP (this defaults to https://IP if relevant, and I can't get the http version to load) or DNS errors when using the magicDNS name.

I almost certainly have a DNS setting incorrect somewhere, but I've tried what I think are all the TSDProxy label combinations to no success including defining the container port, so I'm hoping one of you will call me an idiot and tell me I've missed a setting somewhere!

Thanks all

Do you have Tailscale DNS turned on for your client? (Not on Unraid, on your laptop/phone/etc.)

8 hours ago, EDACerton said:

Do you have Tailscale DNS turned on for your client? (Not on Unraid, on your laptop/phone/etc.)

I had it turned off - having it on didn't help either (on both PC and phone)

2 hours ago, cut_chemist said:

I had it turned off - having it on didn't help either (on both PC and phone)

MagicDNS names won't work if it's turned off on the client, so you'll need to turn that back on.

After that, I'd restart the client and try again.

7 hours ago, cut_chemist said:

I had it turned off - having it on didn't help either (on both PC and phone)

Also, if you have that OFF, you won't be able to access devices on your LAN by FQDN when you're outside as your device won't be able to resolve their addresses on a public DNS

Turning the Tailscale DNS on and restarting the clients has allowed the long names (e.g. docker.tailscale.ts.net) to work, but not the IPv4 ones - presumably because the web page defaults to https://IP/ . This is not an really an issue for me but I thought I'd sanity check to make sure this is working as designed to avoid future issues.

I've added a few more dockers to the Tailnet now and they all work perfectly with the docker.tailscale.ts.net address with the exception Traefik, which gives a 404 error. Any advice here would be appreciated, though I'm aware this question is drifting off topic.

Lastly, just to say thank you, I very much appreciate your help.

8 minutes ago, cut_chemist said:

Turning the Tailscale DNS on and restarting the clients has allowed the long names (e.g. docker.tailscale.ts.net) to work, but not the IPv4 ones - presumably because the web page defaults to https://IP/ . This is not an really an issue for me but I thought I'd sanity check to make sure this is working as designed to avoid future issues.

I've added a few more dockers to the Tailnet now and they all work perfectly with the docker.tailscale.ts.net address with the exception Traefik, which gives a 404 error. Any advice here would be appreciated, though I'm aware this question is drifting off topic.

Lastly, just to say thank you, I very much appreciate your help.

IP addresses don’t work with Tailscale serve/TSDProxy/reverse proxies… they rely on the server name provided by the client to know how to route the request. That is working by design.

Perfect, thank you for the reassurance.

2 hours ago, EDACerton said:

IP addresses don’t work with Tailscale serve/TSDProxy

If he gives this up and instead uses only the plugin and Tailscale client software for non-unraid systems, along with any reverse proxy that sits inside/on ones of these systems, local IP addresses work as expected in addition to FQDN to hosts serviced by the reverse proxy. Along with TS 100* series IPs and MagicDNS if that's turned on. Basically connect "any which way" :)

Edited June 1, 20251 yr by Espressomatic

Hello,

I'm trying to use my Unraid machine as an exit node, however I want to assign Tailscale to a VPN already setup and active in Unraid. This VPN is setup using the default VPN Manager within Unraid. In using your plugin though, I don't see any options at all in the exit node drop down.

Recognizing VPN's installed and allowing us to select them would be a great feature if you could put it on the roadmap for this plugin!

In the meantime, would something along the lines of this suffice or be recommended? I'd love any input you have on how to accomplish this.

# Allow IPv4 forwarding

echo "net.ipv4.ip_forward=1" >> /etc/sysctl.conf

sysctl -p

# Add NAT rule for forwarding Tailscale traffic through Host's VPN gateway

iptables -t nat -A POSTROUTING -o wg1 -j MASQUERADE

Thank you,

host-diagnostics-20250605-2236.zip

Issue: Tailscale Plugin v2025.05.25 (Tailscale v1.84) Causes Unraid Network Inaccessibility

Dear Development Team,

I am writing to report a network connectivity issue I encountered after upgrading the Tailscale plugin to version 2025.05.25 (with built-in Tailscale version 1.84) on my Unraid system.

Problem Description: Following the plugin upgrade to version 2025.05.25, my Unraid host experiences a loss of network connectivity within the Tailnet.

System Information:

• Unraid OS Version: 7.1.2 (This issue has also been reproduced on version 7.1.3)

Specific Symptoms:

• When other devices within the Tailnet attempt to tailscale ping the Unraid host, they consistently receive a time out response.

• Conversely, when the Unraid host attempts to tailscale ping other devices within the Tailnet, it also receives a time out response.

• Concurrently, the Unraid host appears as 'online' in the Tailscale admin console (https://login.tailscale.com/admin/devices).

Troubleshooting & Verification: To further isolate the issue, I confirmed that Tailscale version 1.84, deployed on a Debian 12 host in another home network environment, functions correctly without any connectivity problems. This suggests the problem may not lie with Tailscale 1.84 itself, but rather with the Unraid plugin's specific integration or its behavior within the Unraid 7.x environment.

Current Status (Temporary Workaround): Currently, I have manually downgraded the Tailscale plugin to version 2025.04.17. Following the downgrade, all Tailscale-related functionalities have returned to normal, and the Unraid host is accessible to other devices within the Tailnet, and vice-versa.

Request: I kindly request the development team to investigate this issue, to understand why version 2025.05.25 causes this bidirectional connectivity failure, and to provide a solution.

If further diagnostic information is required, please let me know how I can provide relevant system logs or diagnostic files.

Thank you for your time and support.

尊敬的开发团队，

在使用 Unraid 系统时，Tailscale 插件升级到 2025.05.25 版本（内置 Tailscale 版本 1.84）后，我遇到了一个网络连通性问题。

问题描述： 在插件升级到 2025.05.25 版本后，我的 Unraid 主机在 Tailnet 内失去了网络连通性。

系统信息：

• Unraid OS 版本：7.1.2 (该问题在 7.1.3 版本上也得到了复现)

具体表现：

• 在 Tailnet 内的其他设备尝试 tailscale ping Unraid 主机时，收到 time out 响应。

• 反之，当 Unraid 主机尝试 tailscale ping Tailnet 内其他设备时，同样收到 time out 响应。

• 与此同时，Unraid 主机在 Tailscale 管理后台（https://login.tailscale.com/admin/devices）中显示为 '在线' 状态。

排查与验证： 为进一步排查问题，我确认了在另一家庭网络环境下部署的 Tailscale 1.84 版本（宿主系统为 Debian 12）运行正常。这表明问题可能并非出在 Tailscale 1.84 版本本身，而是与 Unraid 插件的特定集成或其在 Unraid 7.x 环境中的行为有关。

当前状态（临时解决方案）： 目前，我已手动将 Tailscale 插件降级到 2025.04.17 版本。降级后，所有 Tailscale 相关功能均恢复正常工作，Unraid 主机在 Tailnet 内可被其他设备正常访问，反之亦然。

请求： 希望开发团队能调查此问题，了解为何 2025.05.25 版本会导致这种双向连通性故障，并提供解决方案。

如果需要进一步的诊断信息，请告知我如何提供相关的系统日志或诊断文件。

感谢您的时间和支持。

Tailscale stopped working over here at some point in the past few weeks. No settings changes have been made. Only updates to TS releases that take place automatically.

Specifically:

1. using an exit node won't work, whether the exit node is on my LAN or a VPS - DNS works, but nothing can connect/communicate

Example: from a terminal ON a Debian or Unraid exit node, I can ping apple.com - from my Mac connecting through either exit node, I get no response to the same ping

2. using Tailscale outside my LAN from my mobile - zero connectivity

I can't see this being plugin-specific as I run also Mac OS, iPhone and multiple Debian systems, local and remote. But with the Plugin following closely Tailscale updates, no doubt it also breaks at the same time as everything else.

If I had to support anyone else other than myself with this type of solution... shudder.

Edited June 9, 20251 yr by Espressomatic

Sure enough....

I downgraded Tailscale versions from 1.84.x on my Mac to 1.82.5, Debian VPS to 1.82.5, pfSense (FreeBSD) to 1.80 and I can now use the VPS and pfSense systems as exit nodes again.

My iPhone is now also able to use the Tailnet again from mobile connection - still on version 1.84 - with or without exit node.

I still can't use my Unraid 7.1.3, 7.1.2 or 7.0.1 systems as exit nodes after downgrading Unraid & the plugin to a version from April 17 with TS 1.82.5

Edited June 10, 20251 yr by Espressomatic

I have also experienced a loss of functionality in the last week or so. I have several Docker containers whose networks run through a NordLynx VPN tunnel. I used to be able to access the webuis for these containers through my Tailnet when away from the LAN. But now I can't anymore. All my other Dockers--which aren't running through the VPN--are still accessible.

Rolling back to the previous version of the plugin fixes the issue.

Edited June 11, 20251 yr by MrMastodonFarm

Hello,

I tried to hook up Shinobi docker container with tailscale and received the following exception:

Executing Unraid Docker Hook for Tailscale

Detecting Package Manager...

Detected Advanced Package Tool!

Installing packages...

Please wait...

ERROR: Installing packages!

Err:1 http://deb.debian.org/debian buster InRelease

Temporary failure resolving 'deb.debian.org'

Err:2 http://security.debian.org/debian-security buster/updates InRelease

Temporary failure resolving 'security.debian.org'

Err:3 http://deb.debian.org/debian buster-updates InRelease

Temporary failure resolving 'deb.debian.org'

Reading package lists...

W: Failed to fetch http://deb.debian.org/debian/dists/buster/InRelease Temporary failure resolving 'deb.debian.org'

W: Failed to fetch http://security.debian.org/debian-security/dists/buster/updates/InRelease Temporary failure resolving 'security.debian.org'

W: Failed to fetch http://deb.debian.org/debian/dists/buster-updates/InRelease Temporary failure resolving 'deb.debian.org'

W: Some index files failed to download. They have been ignored, or old ones used instead.

Reading package lists...

Building dependency tree...

Reading state information...

ca-certificates is already the newest version (20200601~deb10u2).

ca-certificates set to manually installed.

wget is already the newest version (1.20.1-1.1).

The following NEW packages will be installed:

jq libjq1 libonig5

0 upgraded, 3 newly installed, 0 to remove and 6 not upgraded.

Need to get 355 kB of archives.

After this operation, 1072 kB of additional disk space will be used.

Err:1 http://deb.debian.org/debian buster/main amd64 libonig5 amd64 6.9.1-1

Temporary failure resolving 'deb.debian.org'

Err:2 http://deb.debian.org/debian buster/main amd64 libjq1 amd64 1.5+dfsg-2+b1

Temporary failure resolving 'deb.debian.org'

Err:3 http://deb.debian.org/debian buster/main amd64 jq amd64 1.5+dfsg-2+b1

Temporary failure resolving 'deb.debian.org'

E: Failed to fetch http://deb.debian.org/debian/pool/main/libo/libonig/libonig5_6.9.1-1_amd64.deb Temporary failure resolving 'deb.debian.org'

E: Failed to fetch http://deb.debian.org/debian/pool/main/j/jq/libjq1_1.5+dfsg-2+b1_amd64.deb Temporary failure resolving 'deb.debian.org'

E: Failed to fetch http://deb.debian.org/debian/pool/main/j/jq/jq_1.5+dfsg-2+b1_amd64.deb Temporary failure resolving 'deb.debian.org'

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

ERROR: Unraid Docker Hook script throw an error!

Starting container without Tailscale!

Starting container...

Does tailscale attempt to resolve these URLs through the network specified in the docker container instead of the servers network?

I also tried this in Emby container which is in standard docker bridge mode. App started and I was unable to find any URL which would add the container to my tailscale network in container startup log. This log seems to scroll way to fast to find any info about Tailscale in it and there is no intuitive way to view the previous page as only the latest 90 entries are displayed in Unraid UI. I checked /var/lib/docker/ and saw same errors:

{"log":"Detecting Package Manager...\n","stream":"stdout","time":"2025-06-26T12:43:45.321664192Z"}

{"log":"ERROR: Detection from Package Manager failed!\n","stream":"stdout","time":"2025-06-26T12:43:45.325385113Z"}

{"log":"ERROR: Unraid Docker Hook script throw an error!\n","stream":"stdout","time":"2025-06-26T12:43:45.325427283Z"}

{"log":" Starting container without Tailscale!\n","stream":"stdout","time":"2025-06-26T12:43:45.325439817Z"}

Was this feature ever validated to work?

Edited June 26, 20251 yr by Laov

Is this plugin removed from apps since i cannot find it?

1 hour ago, twiikker said:

Is this plugin removed from apps since i cannot find it?

????

On 6/26/2025 at 8:27 AM, Laov said:

I tried to hook up Shinobi docker container with tailscale and received the following exception:

I'm confident this isn't the correct thread for your issue. You might be looking for the thread about Unraid Tailscale docker integration. This plugin isn't responsible for that.

11 minutes ago, Espressomatic said:

????

My search only finds docker. Or does it mean that i need to install it manually on 6.12.15?

5 minutes ago, twiikker said:

does it mean that i need to install it manually on 6.12.15?

Yes

1 minute ago, Espressomatic said:

Yes

Thanks. Just wanted to make sure. I was in impression that you dont need plugin on 7+ since builtin and since main post says plugin is maintained on 6.12.0 and newer i though latest version is in apps on 6.12.15.

Edited July 3, 20251 yr by twiikker

The Plugin serves a different purpose than the built-in docker support. Instead of using the built-in support with a docker container, I just spin up LXC container and install Tailscale into them on the command-line. IMO, this is much more stable, as is the case with my Nginx Proxy Manager and AdGuard Home LXC.

• 6.11.5: https://raw.githubusercontent.com/unraid/unraid-tailscale/2025.03.05/plugin/tailscale.plg

• 6.12.x: https://raw.githubusercontent.com/unraid/unraid-tailscale/2025.04.17/plugin/tailscale.plg

These both go to 2025.03.05 version of plugin on main post

Edited July 4, 20251 yr by twiikker

On 7/3/2025 at 3:45 PM, twiikker said:

Is this plugin removed from apps since i cannot find it?

This plugins latest version only supports Unraid 7 thus you cant find it on the previous versions.