41 minutes ago, boxer74 said:

I am already using tailscale through a docker container. It is working as I would like. What is the advantage to the plugin? I suppose it would stay connected even if the array is down. Is that about it?

Basically that and no docker overhead. Perhaps a bit more support as the docker guy only releases versions and rarely answers questions. As he himself said - the only reason to use docker is if you are doing something interesting with routing docker containers through tailscale.

On 7/26/2023 at 1:48 AM, EDACerton said:

1. Just open the Unraid console and run:

 

tailscale set --advertise-routes=192.168.0.0/24

 

2. There have been problems with SMB on some of the more recent Unraid builds.... please generate plugin diagnostics (from the Help page in Tailscale settings) and I can take a look at what your server is doing.

@EDACerton Have you been able to remidy the issue concerning the SMB not working over Tailscale? Just switched to the plugin  version and now my host "tower" is not accesible via SMB using Tailscale. I can work around it by exposing the IP as a sub-route but that is sub-optimal. Seems to work fine with all other services though.

Tower-tailscale-diag-20230807-103715.zip

Edited August 7, 20232 yr by InvicTech
Added Diagnostics

I just upgraded from 6.12.2 to 6.12.3

I had the plugin enabled before the upgrade (as well as the Tailscale docker container) and could access my Docker containers URLs over Nginx Proxy Manager

After rebooting I lost the means to access any of those urls

Luckily I also had CloudFlareD to access my main UI, and I have removed the plugin and I can once again access my URLs
 

I am unclear why I was prevented from accessing anything with the plugin enabled (tailscale1 [the plugin interface] was added in the "Include listening interfaces:", I checked)

Any insight into this would be appreciated

12 hours ago, martial said:

I had the plugin enabled before the upgrade (as well as the Tailscale docker container)

This is not a supported configuration... you have to use either the Tailscale plugin or the docker, not both. If you have both, they'll fight with each other and cause connection issues.

On 8/7/2023 at 4:25 AM, InvicTech said:

@EDACerton Have you been able to remidy the issue concerning the SMB not working over Tailscale? Just switched to the plugin  version and now my host "tower" is not accesible via SMB using Tailscale. I can work around it by exposing the IP as a sub-route but that is sub-optimal. Seems to work fine with all other services though.

Tower-tailscale-diag-20230807-103715.zip 227.01 kB · 0 downloads

I'm looking into this more... SMB via the Tailscale IP works on my server, so there must be something weird in the newer Unraid versions that varies based on other network settings.

 

One thing that I did notice is that there's a difference in how the SMB configuration is being generated for some reason... in my smb_names.conf file, the interfaces line has CIDR entries (e.g., my.tailscale.ip.here/24). The smb_names.conf file on your instance just has IP addresses (e.g., your.tailscale.ip.here).

 

I'm guessing that difference has something to do with why yours isn't working, but I need to dig some more to see what would cause that. (smb_names.conf is created by the Unraid scripts, not the plugin itself).

Edited August 9, 20232 yr by EDACerton

On 7/25/2023 at 8:19 PM, Laov said:

DataServer-tailscale-diag-20230726-030227.zip 279.31 kB · 1 download

 

On 8/7/2023 at 4:25 AM, InvicTech said:

 

Tower-tailscale-diag-20230807-103715.zip 227.01 kB · 1 download

I think I figured out what's happening in the Unraid scripts....

 

Try setting "Enable NetBIOS" to No in the SMB settings.

3 hours ago, EDACerton said:

 

I think I figured out what's happening in the Unraid scripts....

 

Try setting "Enable NetBIOS" to No in the SMB settings.

You're a legend mate! Hopefully, I don't have any devices that still rely on SMBv1 (Looking at you old Samsung Printer/Scanner)

Setting "Enable NetBIOS" to "No" also fixed my issue, coming from a Linux client to an Unraid 6.12.3 server over the Tailscale plugin.

Holy cow! I can finally access my files from the server via SMB over Tailscale. From 6.12 to 6.12.3, nothing fixed the issue. This NetBIOS setting should also be state in the changelog notes.

Thank you for sharing this!

Just received official email around 5 hours ago on a vulnerability, seems like we need to upgrade to at least 1.48.1 on the Tailscale binary, does anyone know how we can patch that immediately before the UnRAID plugin releases an upgrade tho?

The security vulnerability isn't something to be worried about. Tailscale is telling the older versions not to use the affected functionality. From their security bulletin:

 

Quote

UPnP on vulnerable versions was disabled by the coordination server.

 

The only problem now is that NAT traversal won't work as well until I get an update published, which will probably be in about an hour

2023.08.22

• Update Tailscale to 1.48.1

Just an FYI, on my server the UnRaid Docker apps would NOT update or install when the Tailscales plugin was active. Had to issue "tailscale down" on the command line to get Docker working again.

Let me know if you want me to explain, do or test more.

 

12 hours ago, Tomputer said:

Just an FYI, on my server the UnRaid Docker apps would NOT update or install when the Tailscales plugin was active. Had to issue "tailscale down" on the command line to get Docker working again.

Let me know if you want me to explain, do or test more.

 

A plug-in diagnostic package while tailscale is running would be helpful… can’i can’t help much without that. 

9 hours ago, EDACerton said:

A plug-in diagnostic package while tailscale is running would be helpful… can’i can’t help much without that. 

I had a Rapid Unexpected Termination yesterday due to a power cut 😞

So the parity check is running ... and docker seems to work as expected.

What I got was a docker error "parsing http 408 response body".

Which is basically due to docker not finding a way to the outside world.

It found its way again after shutting down tailscale.

Sorry, can't replicate it anymore.

Post installing tailscale on unraid and a windows machine where I had setup my unraid shares as drives, the drives aren't accessible. Just wanted to check if others have faced this issue?

25 minutes ago, maverhick said:

Post installing tailscale on unraid and a windows machine where I had setup my unraid shares as drives, the drives aren't accessible. Just wanted to check if others have faced this issue?

 

On 8/8/2023 at 11:43 PM, EDACerton said:

 

I think I figured out what's happening in the Unraid scripts....

 

Try setting "Enable NetBIOS" to No in the SMB settings.

 

Noobie questions.

 

I want to be able to access unraid server console, home assistant, etc. with local IPs

 

I successfully installed the plugin.  I see my unraid server in the admin console in Tailscale.  Have my laptop connected as well.

 

Can't figure out what to do next.  I see an IP address associated with the server in the console but this doesn't work if I try to access it through the web browser.

 

I am sure this is a simple configuration step that I am missing.  Thanks for the help.

5 minutes ago, The Transplant said:

Noobie questions.

 

I want to be able to access unraid server console, home assistant, etc. with local IPs

 

I successfully installed the plugin.  I see my unraid server in the admin console in Tailscale.  Have my laptop connected as well.

 

Can't figure out what to do next.  I see an IP address associated with the server in the console but this doesn't work if I try to access it through the web browser.

 

I am sure this is a simple configuration step that I am missing.  Thanks for the help.

You just need to advertise the IPs you want to be visible with advertise-routes command.

 

Example:

1. Just open the Unraid console and run:

tailscale set --advertise-routes=192.168.0.0/24

8 minutes ago, Laov said:

You just need to advertise the IPs you want to be visible with advertise-routes command.

 

Example:

1. Just open the Unraid console and run:

tailscale set --advertise-routes=192.168.0.0/24

Thanks, I substituted 192.168.2.0 for my local IP network, which I assume I was supposed to do, and it worked.

 

Next question - how do I access other IPs on my local network without having to install Tailscale on each one?

Just now, The Transplant said:

Thanks, I substituted 192.168.2.0 for my local IP network, which I assume I was supposed to do, and it worked.

 

Next question - how do I access other IPs on my local network without having to install Tailscale on each one?

You just set that up 😁 that’s what advertised routes does. 

4 minutes ago, EDACerton said:

You just set that up 😁 that’s what advertised routes does. 

Then I must have done something wrong as I can't access any local IPs remotely.  I am able to get to the Unraid server through the IP in the Tailscale console screen - 100.X.X.X.  But anything with 192.2.168.X is not responding.  Looked in Tailscale log and it doesn't show any errors - just activity around the 100.X.X.X IP address.

2 minutes ago, The Transplant said:

Then I must have done something wrong as I can't access any local IPs remotely.  I am able to get to the Unraid server through the IP in the Tailscale console screen - 100.X.X.X.  But anything with 192.2.168.X is not responding.  Looked in Tailscale log and it doesn't show any errors - just activity around the 100.X.X.X IP address.

Did you approve the route in the Tailscale console?

2 minutes ago, EDACerton said:

Did you approve the route in the Tailscale console?

Nope, but I figured out what that mean't and just did it.  And it's working.  Thanks for that.  Does the advertise command need to be run on reboot of unraid or is this once and done?

Just now, The Transplant said:

Nope, but I figured out what that mean't and just did it.  And it's working.  Thanks for that.  Does the advertise command need to be run on reboot of unraid or is this once and done?

One and done 😁