PaulieW

7.2.6

I precleared a disk using the plugin, but when added to the array it still needed to format the disk and rebuild the array... Is this because updates on the unraid's OS don't support precleared disks anymore? Before, the array would accept precleared disks straight away.

Ah I see. I indeed have MagicDNS enabled, TAILSCALE_USERSPACE_NETWORKING is already set to FALSE. So MagicDNS is probably my issue then. I have lots of containers like radarr.my-tsname.ts.net, sonarr.my-tsname.ts.net, etc for which I would like to keep using MagicDNS Edit: I see here https://tailscale.com/kb/1235/resolv-conf that: So it should be possible to only disable MagicDNS for the qBittorrent container, right? Would I just run this command tailscale set --accept-dns=false in the console window of the binhex-qbittorrent container? Edit2: I believe I've done it, by adding the parameter --accept-dns=false to the Extra Parameters field: For some reason I can now connect to it using the MagicDNS address, but not the IPv4 address. I was expecting it to be the other way around. Maybe it has to do with the HTTPS certificate I put in place. Anyways, I think this does the job.

Hi there binhex, I've started using Tailscale recently and am now configuring it for your qBt container. The wireguard and tailscale network interfaces clash, as you pointed out in Q30: So I've added "100.64.0.0/10", which should cover the full Tailscale range from 100.64.0.0 to 100.127.255.255, to the LAN_NETWORK key of the docker container. I can see it in the docker logs when I start it like this: 2025-04-22 11:34:42.545004 [info] LAN_NETWORK defined as '192.168.2.0/24,100.64.0.0/10' 2025-04-22 11:34:42.566671 [info] LAN_NETWORK exported as '192.168.2.0/24,100.64.0.0/10' Unfortunately I am still stuck in the wireguard up/down loop, as seen from the logs below. What am I doing wrong? 2025-04-22 11:41:55,441 DEBG 'start-script' stderr output: [#] sysctl -q net.ipv4.conf.all.src_valid_mark=1 2025-04-22 11:41:55,442 DEBG 'start-script' stderr output: [#] iptables-restore -n 2025-04-22 11:41:55,443 DEBG 'start-script' stderr output: [#] '/root/wireguardup.sh' 2025-04-22 11:42:46,031 DEBG 'watchdog-script' stdout output: [info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure... 2025-04-22 11:42:51,504 DEBG 'start-script' stdout output: [info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure... 2025-04-22 11:42:51,506 DEBG 'start-script' stdout output: [info] Attempting to get external IP using 'http://checkip.amazonaws.com'... 2025-04-22 11:42:51,513 DEBG 'start-script' stdout output: [info] Failed on last attempt, attempting to get external IP using 'http://whatismyip.akamai.com'... 2025-04-22 11:42:51,519 DEBG 'start-script' stdout output: [info] Failed on last attempt, attempting to get external IP using 'https://ifconfig.co/ip'... 2025-04-22 11:42:51,525 DEBG 'start-script' stdout output: [info] Failed on last attempt, attempting to get external IP using 'https://showextip.azurewebsites.net'... 2025-04-22 11:42:51,530 DEBG 'start-script' stdout output: [warn] Cannot determine external IP address, performing tests before setting to '127.0.0.1'... [info] Show name servers defined for container 2025-04-22 11:42:51,531 DEBG 'start-script' stdout output: # resolv.conf(5) file generated by tailscale # For more info, see https://tailscale.com/s/resolvconf-overwrite # DO NOT EDIT THIS FILE BY HAND -- CHANGES WILL BE OVERWRITTEN nameserver 100.100.100.100 search [REDACTED].ts.net 2025-04-22 11:42:51,531 DEBG 'start-script' stdout output: [info] Show contents of hosts file 2025-04-22 11:42:51,531 DEBG 'start-script' stdout output: 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters 172.17.0.9 8e9ea6256209 2025-04-22 11:42:51,532 DEBG 'start-script' stdout output: [info] VPN provider 'airvpn' not supported for automatic port forwarding, skipping incoming port assignment 2025-04-22 11:42:51,533 DEBG 'start-script' stdout output: [info] WireGuard interface 'up' 2025-04-22 11:43:21,533 DEBG 'start-script' stdout output: [info] Sending 'down' command to WireGuard due to dns failure... 2025-04-22 11:43:21,534 DEBG 'start-script' stdout output: [info] Attempting to bring WireGuard interface 'down'... 2025-04-22 11:41:55,441 DEBG 'start-script' stderr output: [#] sysctl -q net.ipv4.conf.all.src_valid_mark=1 2025-04-22 11:41:55,442 DEBG 'start-script' stderr output: [#] iptables-restore -n 2025-04-22 11:41:55,443 DEBG 'start-script' stderr output: [#] '/root/wireguardup.sh'

My god! Then why is it turned ON by default in Windows installation. I thought this was a fool-proof/VPN-for-dummies program, i.e. for me!

You were correct not to mess around in routing tables. I tried uninstalling Tailscale on Windows, and after I had done that, I could enable/disable Tailscale on unraid and I would still connect to it on my PC using 192.168.2.9. So that confirms it was a Tailscale-on-Windows issue. After a bit more back and forth with ChatGPT, I found the solution (I think?) by simply unticking this setting in the Windows app: Use Tailscale subnets With this unticked, I can now enable/disable Tailscale on unraid and I can still connect to it on my PC using 192.168.2.9. And I can also still connect to all the devices using the tailnet on PC. When I additionally untick "Use Tailscale DNS settings", I can still connect to unraid on my PC using 192.168.2.9 regardless of whether Tailscale is enabled/disabled on unraid, but then I can't browse to unraid.my-tailnetname.ts.net/login anymore. So I have to keep this ticked. Is the problem potentially coming from my unraid server is advertising routes? I just followed spaceinvaderone's yt guide, didn't think much of it so I just did it. This wouldn't explain the fact that I can still access 192.168.2.9 (when unraid's Tailscale is disabled) through my phone though.

With Tailscale enabled, and I run "route print" in cmd on my Windows PC I see this: C:\Users\[REDACTED]>route print =========================================================================== Interface List 8...........................Tailscale Tunnel 7...d8 bb c1 96 cb f7 ......Intel(R) Ethernet Controller (3) I225-V #2 11...d8 bb c1 96 cb f6 ......Intel(R) Ethernet Controller (3) I225-V 17...60 dd 8e 0f 11 76 ......Intel(R) Wi-Fi 6E AX211 160MHz 14...60 dd 8e 0f 11 77 ......Microsoft Wi-Fi Direct Virtual Adapter 21...62 dd 8e 0f 11 76 ......Microsoft Wi-Fi Direct Virtual Adapter #2 1...........................Software Loopback Interface 1 15...00 00 00 00 00 00 00 e0 Microsoft Teredo Tunneling Adapter =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.2.254 192.168.2.13 25 100.79.[REDACTED] 255.255.255.255 On-link 100.93.[REDACTED] 5 100.93.[REDACTED] 255.255.255.255 On-link 100.93.[REDACTED] 261 100.99.[REDACTED] 255.255.255.255 On-link 100.93.[REDACTED] 5 100.100.100.100 255.255.255.255 On-link 100.93.[REDACTED] 5 127.0.0.0 255.0.0.0 On-link 127.0.0.1 331 127.0.0.1 255.255.255.255 On-link 127.0.0.1 331 127.255.255.255 255.255.255.255 On-link 127.0.0.1 331 192.168.2.0 255.255.255.0 On-link 192.168.2.13 281 192.168.2.0 255.255.255.0 100.100.100.100 100.93.[REDACTED] 5 192.168.2.13 255.255.255.255 On-link 192.168.2.13 281 192.168.2.255 255.255.255.255 On-link 192.168.2.13 281 224.0.0.0 240.0.0.0 On-link 127.0.0.1 331 224.0.0.0 240.0.0.0 On-link 192.168.2.13 281 255.255.255.255 255.255.255.255 On-link 127.0.0.1 331 255.255.255.255 255.255.255.255 On-link 192.168.2.13 281 =========================================================================== These two lines I think that are of interest: 192.168.2.0 255.255.255.0 On-link 192.168.2.13 281 192.168.2.0 255.255.255.0 100.100.100.100 100.93.[REDACTED] 5 Do I understand correctly that Windows currently redirects all connections on 192.168.2.0/24 to the tailscale network over the on-link one, because it has a lower metric value of 5 compared to the on-link one of 281? If I increase the metric from 5 to 300, would the PC then always take the on-link route? I'm a bit cautious to mess around with this. Curious to see what other people have in their output when they run "route print" and whether my setup differs a lot or not.

Wireguard's IPv4 is 10.185.*.* apparently, what's the problem with that? When I turn off wireguard the behaviour is the same; can't connect to 192.168.2.9 when I disable Tailscale, when I re-enable I can connect to it. So I don't think the wireguard interface is the problem.

Correct, so yea this definitely seems like a Windows problem. Let's see if EDA has something to add. Thank you for your help.

Correct Both Management access and Network settings remain unchanged when I turn off Tailscale. Unraid: root@[REDACTED]:~# ip addr show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 3: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc fq master bond0 state UP group default qlen 1000 link/ether 9c:6b:00:12:1c:0c brd ff:ff:ff:ff:ff:ff 4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UP group default qlen 1000 link/ether 9c:6b:00:12:1c:0c brd ff:ff:ff:ff:ff:ff 5: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 9c:6b:00:12:1c:0c brd ff:ff:ff:ff:ff:ff inet 192.168.2.9/24 brd 192.168.2.255 scope global dynamic noprefixroute br0 valid_lft 46469sec preferred_lft 35669sec [REDACTED] 67: tailscale1: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc fq state UNKNOWN group default qlen 500 link/none inet [REDACTED]/32 scope global tailscale1 valid_lft forever preferred_lft forever inet6 [REDACTED]/128 scope global valid_lft forever preferred_lft forever inet6 [REDACTED]/64 scope link stable-privacy proto kernel_ll valid_lft forever preferred_lft forever [REDACTED] root@[REDACTED]:~# ip route default via 192.168.2.254 dev br0 proto dhcp src 192.168.2.9 metric 1005 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 172.18.0.0/16 dev br-45768f7136a9 proto kernel scope link src 172.18.0.1 linkdown 172.19.0.0/16 dev br-24e2ea19d2ed proto kernel scope link src 172.19.0.1 linkdown 192.168.2.0/24 dev br0 proto dhcp scope link src 192.168.2.9 metric 1005 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown root@[REDACTED]:~# cat /etc/resolv.conf # Generated by dhcpcd from br0.dhcp domain home nameserver 192.168.2.254 root@[REDACTED]:~# Windows 11 PC C:\Users\[REDACTED]>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : [REDACTED] Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : [REDACTED].ts.net home Unknown adapter Eddie: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : WireGuard Tunnel Physical Address. . . . . . . . . : DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : fd7d:76ee:e68f:a993:165c:4222:93b2:f69c(Preferred) IPv4 Address. . . . . . . . . . . : 10.185.109.78(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.255 Default Gateway . . . . . . . . . : DNS Servers . . . . . . . . . . . : fd7d:76ee:e68f:a993::1 10.128.0.1 NetBIOS over Tcpip. . . . . . . . : Enabled Unknown adapter Tailscale: Connection-specific DNS Suffix . : [REDACTED].ts.net Description . . . . . . . . . . . : Tailscale Tunnel Physical Address. . . . . . . . . : DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : [REDACTED](Preferred) Link-local IPv6 Address . . . . . : [REDACTED](Preferred) IPv4 Address. . . . . . . . . . . : [REDACTED](Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.255 Default Gateway . . . . . . . . . : NetBIOS over Tcpip. . . . . . . . : Disabled Connection-specific DNS Suffix Search List : [REDACTED].ts.net Ethernet adapter Ethernet 2: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : home Description . . . . . . . . . . . : Intel(R) Ethernet Controller (3) I225-V #2 Physical Address. . . . . . . . . : D8-BB-C1-96-CB-F7 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Ethernet adapter Ethernet: Connection-specific DNS Suffix . : home Description . . . . . . . . . . . : Intel(R) Ethernet Controller (3) I225-V Physical Address. . . . . . . . . : D8-BB-C1-96-CB-F6 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2a02:a459:9298:0:1b16:e70e:5582:dd07(Preferred) IPv6 Address. . . . . . . . . . . : 2a02:a459:9298:1:c562:4e54:72fe:123(Preferred) IPv6 Address. . . . . . . . . . . : fd5a:5445:4547:0:aa5f:1bc:6684:80c9(Preferred) Temporary IPv6 Address. . . . . . : 2a02:a459:9298:0:382e:e578:6923:b22e(Preferred) Temporary IPv6 Address. . . . . . : 2a02:a459:9298:1:382e:e578:6923:b22e(Preferred) Temporary IPv6 Address. . . . . . : fd5a:5445:4547:0:382e:e578:6923:b22e(Preferred) Link-local IPv6 Address . . . . . : fe80::6a1e:c2bc:5713:c092%11(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.2.13(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : 15 April, 2025 08:25:48 Lease Expires . . . . . . . . . . : 16 April, 2025 08:25:48 Default Gateway . . . . . . . . . : 192.168.2.254 DHCP Server . . . . . . . . . . . : 192.168.2.254 DHCPv6 IAID . . . . . . . . . . . : 114867137 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2D-E0-93-85-D8-BB-C1-96-CB-F6 DNS Servers . . . . . . . . . . . : fd7d:76ee:e68f:a993::1 10.128.0.1 NetBIOS over Tcpip. . . . . . . . : Enabled Connection-specific DNS Suffix Search List : home Wireless LAN adapter Wi-Fi: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : home Description . . . . . . . . . . . : Intel(R) Wi-Fi 6E AX211 160MHz Physical Address. . . . . . . . . : 60-DD-8E-0F-11-76 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Wireless LAN adapter Local Area Connection* 9: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter Physical Address. . . . . . . . . : 60-DD-8E-0F-11-77 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Wireless LAN adapter Local Area Connection* 10: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2 Physical Address. . . . . . . . . : 62-DD-8E-0F-11-76 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Tunnel adapter Teredo Tunneling Pseudo-Interface: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:0:284a:364:107d:e8:2a67:4419(Preferred) Link-local IPv6 Address . . . . . : fe80::107d:e8:2a67:4419%15(Preferred) Default Gateway . . . . . . . . . : DHCPv6 IAID . . . . . . . . . . . : 251658240 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2D-E0-93-85-D8-BB-C1-96-CB-F6 NetBIOS over Tcpip. . . . . . . . : Disabled C:\Users\[REDACTED]> Does anything seem off? When I turn Tailscale off, login on my phone and uninstall the Tailscale plugin there, I still can't connect to unraid using my PC. When I then reinstall it, Tailscale is still turned off and still can't connect on my PC, obviously. I re-enable it then on my phone, and I can connect to unraid again on my PC.

So in default state when Tailscale is up and everything is working, these are my interfaces: Current listening interfaces: br0 tailscale1 Include listening interfaces: tailscale1 Is this ok or not? When I disable tailscale and go on my phone to network settings I see: Current listening interfaces: br0 Include listening interfaces: tailscale1 Is this ok or not? My PC is 192.168.2.13 and my unraid machine is 192.168.2.9. I am trying to connect to unraid on my PC both using LAN IP (http://192.168.2.9/login) as well as http://tower.local/login, both do not work anymore after I have disabled tailscale. And both work again when I re-enable Tailscale. "What network segments are your machines attached to when you take Tailscale down?" Nothing special, I think? I've never setup complicated things, all my devices are on 192.168.2.0/24. I don't have any other active subnets. I just installed tailscale because it's now integrated into unraid, that's all. Very happy to use it btw, but would like to be able to turn it off as well, is all. "There are multiple things that can go wrong here but it all depends on how all the systems you're looking at are set up, not just the Unraid system." Ok I haven't really setup anything special. The router just has assigned IPs to my devices and I have made them static in DHCP, that's about it. I have installed the Plugin diagnostics, but do I now still need to place a diagnostics.json file somewhere? "All this is why I have my set up such that Tailscale can't/won't alter how any system on the LAN resolves or routes. So whether TS is up or down on one, multiple or all machines, they all continue communicating with each other as normal/expected. While on the LAN." Yes this is exactly what I'm trying to achieve as well.

Thanks for trying to help me again. I installed the plugin diagnostics, not sure how where to find the info to share here. I set "Enable Tailscale" to "No" in the advanced settings of the tailscale plugin, and the same happened: lost complete connection on my PC, but on phone still working. So I browse to network settings on my phone and see: Current listening interfaces: br0 Include listening interfaces: tailscale1 So the same result as when I did "tailscale down". It's weird though that since it's still listening to br0, the connection is lost. I reinstated the connection again by setting "Enable Tailscale" to "Yes". How do I check if my unraid server is set up to advertise a subnet? I'm a complete noobie at all of this. Maybe useful info: all my devices are on subnet 192.168.2.0/24, so subnet 2.

I tried a bit of back and forth with ChatGPT on this. In Network settings, I have: Current listening interfaces: br0 tailscale1 Include listening interfaces: tailscale1 Exclude listening interfaces: And ChatGPT is saying that when I run "tailscale down", the web UI is no longer bound to br0 (your LAN interface) — hence no access via LAN IP. I changed listening interfaces from tailscale1 to br0 tailscale1. Then opened terminal and did tailscale down. I lost connection again. But on my phone it was still working, so I go to network settings again, and then I see this: Current listening interfaces: br0 Include listening interfaces: tailscale1 ChatGPT: Problem: tailscale down dynamically removes the tailscale1 interface — and since “Include listening interfaces” is set to tailscale1, Unraid drops back to its default behavior (which can mean it stops listening altogether or just on one interface like br0, depending on other configs). But crucially: Unraid is saving Include listening interfaces: tailscale1 to its config. So when tailscale1 disappears, the UI reverts to something unpredictable (or at least not what we want). So I now I empty "Include listening interfaces" ("This tells Unraid to listen on all available interfaces (0.0.0.0)"). But then it says this: Current listening interfaces: br0 Include listening interfaces: tailscale1 had disappeared! Even though I executed tailscale up. And in this state I started losing API connection frequently. webUI was disconnected, then I had to relogin etc. Terminal window closing all by itself. Some stuff was going on in the background. Now I have rebooted the machine and we're luckily back to: Current listening interfaces: br0 tailscale1 Include listening interfaces: tailscale1 Maybe I'll just keep tailscale on forever, lol...

I just opened terminal window and executed "tailscale down", then I lost complete connection to my server on the PC... For some reason I could still enter the unraid dashboard using my phone, so I logged in there, opened terminal window and exectued "tailscale up". Now I can connect to my server again on my PC. No idea what just happened but I realize this is not the way to go.

Can you also just temporarily disconnect from tailscale, without losing the credentials, then turn it back on later?