VampyreVK

Followed Todo88's advice and managed to get it working! Thanks for the help! I am not sure if this made a difference, but in case it might help someone, this was the command I used when I got everything working: "tailscale set --advertise-routes=192.168.0.0/24,192.168.1.0/24 --advertise-exit-node", formerly I had --accept-routes enabled, but I just left it out this go and it seems to work just fine. The thing that finally pushed it over the edge to working was adding the tailscale gateway to the routing table with my IPv4 192.168.0.6 UnRAID address, which caused the web ui to become inaccessible from all routes, but after a restart, it started working again, and tailscale finally started acting as expected.

I am having the same issue as letum00, adaughe2, and biohazard32. I am switching from the docker container to the plugin, and I am able to access everything on my local subnet, such as other devices from within Tailscale, but not the main Unraid server GUI whichever way I go about it(the local IP:192.168.0.6, the Tailscale IP, the hostname, or the Unraid connect url). I cannot access anything running as a port under that main IP either (192.168.0.6:8989 etc.). VM's or other devices on the network with a different assigned IP work just fine, but anything under that 0.6 ip address is unable to connect from Tailscale. VivNAS-tailscale-diag-20240103-191059.zip