bortsampson89

I'm having the same issue.

patching file sbin/mover Hunk #1 FAILED at 72. 1 out of 1 hunk FAILED -- saving rejects to file sbin/mover.rej Failed to install patch 20250128204439-pr271.patch Aborting I get this error when installing the latest patches for 7.0. I'm 99% sure it's because I use the mover fine tuning plugin. It seems the like other patches worked, so I will ignore.

Hi, I am using Unraid 7.0's tailscale plugin to connect to my dockers outside of my LAN. I seem to have DNS issues when I have tailscale enabled in any capacity. The only thing I've found that fixes it is to set TAILSCALE_USERSPACE_NETWORKING to true. While it's false, I can't curl google.com but I can curl the IP of google.com if I look up what it resolves to. Is TAILSCALE_USERSPACE_NETWORKING true my best option here? Or is there something I can do to get the DNS working with false? I read the FAQs and also saw someone else mention disabling tailscale's magic dns, but disabling magic dns didn't work for me, and I would also prefer to keep using the machine names in my tailscale URLs rather than IPs. I have use Tailscale's DNS turned off in Unraid's Tailscale setting's, and Override Local DNS on Tailscale admin disabled. Also, without TAILSCALE_USERSPACE_NETWORKING enabled, I can't connect to my other dockers in same custom docker network via name. IP only. Thanks in advance. EDIT: I decided to use the qbit container as a tailscale exit node for another docker, and this requires userspace networking enabled anyway, so I guess it is indeed the best option for me.

Yes, and it was working fine for the first week. And all of my dockers using Tailscale serve are still accessible via the machinename.tailnetname.net

Hi! I'm having some issues reaching my GUI via the tailscale URL. It loads fine with my .local address. And all of my dockers are accessible via tailscale. I'm on unraid 7.0rc2. I'm pretty new to this stuff. Didn't make any changes, it just stopped working. The only thing I tried doing to maybe fix the problem was changing the https port in Unraid's management access settings, and then changed it back. I've tried googling but was unable to find someone with exactly the same problem. Would appreciate any help/happy to clarify anything if needed. blockbuster-diagnostics-20241223-2337.zip Blockbuster-tailscale-diag-20241223-234613.zip