2 minutes ago, EDACerton said:

You are correct, switching from the docker to the plugin will require disconnecting Tailscale... the two fight each other if they are running at the same time.

 

If you *really* wanted to try to do it remotely (not that I would recommend it), it might be possible if you get creative with the Tailscale admin console:

1. Turn on device approval for your tailnet (Settings -> Device Management).
2. Install the plugin and log in, but don't approve it yet.
3. Stop the docker container (this will drop your connection to the server, but you should get it back in the next step)
4. Approve the plugin connection in the Tailscale console.

The catch to this being (of course) that if anything goes wrong you've just lost your remote connection until you have local access again. Managing remote connections in-band is always a fun process

That sounds very complicated, it seems like my best bet is just to wait till I've got local access. Once I have, do I just delete the docker container and install the plugin? No other setup steps or configuration required?

22 minutes ago, rama3124 said:

That sounds very complicated, it seems like my best bet is just to wait till I've got local access. Once I have, do I just delete the docker container and install the plugin? No other setup steps or configuration required?

Yep, that's it. Install plugin, sign in to Tailscale through the WebGUI,

Edited March 31, 20242 yr by EDACerton

2 hours ago, EDACerton said:

Yep, that's it. Install plugin, sign in to Tailscale through the WebGUI,

Ok thanks for your prompt replies 

On 3/15/2024 at 3:48 PM, exwebjunkie said:

Sorry for the newbie question.

 

My network is running on the 192.168.0.X network.

I have Unraid set to 192.168.0.74 (with the web UI to port 84)

All my dockers (well, most) are set with the br0 network and with dedicated IPs like 192.168.0.145 (for Sonarr for example).

 

I have installed this plugin - and I can connect to unraid vs the "new" IP.

I ran this command tailscale set --advertise-routes=192.168.0.0/24 and I can see in tailscale web gui that this has been accepted.

BUT - I can't see any of my dockers that are on the br0 network - I thought they would be found due to being on the subnet that I setup.

 

Any ideas what I need to change to make them appear so I can grab their IPs etc and connect to them?

 

Thank you!

Ran this:

tailscale up --advertise-exit-node --accept-routes --advertise-routes=192.168.1.0/24

expecting access to all my dockers, but no luck.  Could get to NAS and remotely access SMB shares just fine.

 

Then did this:

https://forums.unraid.net/topic/77390-solved-cannot-access-dockers-using-custombr0/?do=findComment&comment=849673

 

Now I can turn on IOS tailscale client, and connect to my docker services on custom bridge, by original 192.168.x.x address.

Hello!

I have some experience with tailscale but just started to try out this plugin.

I have a working custom network setup with traefik and some containers behind that. This is working just fine locally, via wireguard and public internet. Traefik listens on the unraid host IP:443.

 

I was trying to migrate some currently public containers to tailscale.

 

Basic connectivity is working fine. I have setup my public dns to point to the unraid tailscale IP instead of my public ip, connection works when in tailnet.

I have setup everything to allow direct connections whenever possible, this seems to work as far as I can observe.

 

Sadly when using the plugin I am mostly extremely limited in bandwidth >1Mbps, sometimes after restarting tailscale it works fine but then breaks down again. Much much worse than straight internet or locally, everything using the same traefik configuration.

Using the tailscale container provides better bandwidth but I would like to avoid that.

 

Right now I can only assume that some unraid internal networking is screwing with me.

 

Tower-tailscale-diag-20240401-163235.zip

On 3/31/2024 at 7:18 AM, EDACerton said:

You are correct, switching from the docker to the plugin will require disconnecting Tailscale... the two fight each other if they are running at the same time.

 

If you *really* wanted to try to do it remotely (not that I would recommend it), it might be possible if you get creative with the Tailscale admin console:

1. Turn on device approval for your tailnet (Settings -> Device Management).
2. Install the plugin and log in, but don't approve it yet.
3. Stop the docker container (this will drop your connection to the server, but you should get it back in the next step)
4. Approve the plugin connection in the Tailscale console.

The catch to this being (of course) that if anything goes wrong you've just lost your remote connection until you have local access again. Managing remote connections in-band is always a fun process

I gave this a go after all and when I stopped the docker container and approved the plugin, the new unraid instance didn't show as online in my tailscale admin console. I have SSH access so I can just delete the plugin and restart the tailscale container but is there a way to complete setup for the plugin through command line? 

Random reoccurring issue. Tailscale does not allow SMB share access after 1st server boot. Tailscale DNS name is pingable yet SMB shares are not accessible. Restarting tailscale solves the issue. Is there any way to reboot tailscale plugin with user scripts?

3 hours ago, Laov said:

Random reoccurring issue. Tailscale does not allow SMB share access after 1st server boot. Tailscale DNS name is pingable yet SMB shares are not accessible. Restarting tailscale solves the issue. Is there any way to reboot tailscale plugin with user scripts?

 

/usr/local/emhttp/plugins/tailscale/restart.sh

 

5 hours ago, rama3124 said:

I gave this a go after all and when I stopped the docker container and approved the plugin, the new unraid instance didn't show as online in my tailscale admin console. I have SSH access so I can just delete the plugin and restart the tailscale container but is there a way to complete setup for the plugin through command line? 

 

Run this from SSH:

 

tailscale up

 

Then, once you've logged in and you see the device in the Tailscale console:

 

/usr/local/emhttp/plugins/tailscale/restart.sh

 

Edited April 1, 20242 yr by EDACerton

6 hours ago, Rykzon said:

Hello!

I have some experience with tailscale but just started to try out this plugin.

I have a working custom network setup with traefik and some containers behind that. This is working just fine locally, via wireguard and public internet. Traefik listens on the unraid host IP:443.

 

I was trying to migrate some currently public containers to tailscale.

 

Basic connectivity is working fine. I have setup my public dns to point to the unraid tailscale IP instead of my public ip, connection works when in tailnet.

I have setup everything to allow direct connections whenever possible, this seems to work as far as I can observe.

 

Sadly when using the plugin I am mostly extremely limited in bandwidth >1Mbps, sometimes after restarting tailscale it works fine but then breaks down again. Much much worse than straight internet or locally, everything using the same traefik configuration.

Using the tailscale container provides better bandwidth but I would like to avoid that.

 

Right now I can only assume that some unraid internal networking is screwing with me.

 

Tower-tailscale-diag-20240401-163235.zip 172.31 kB · 1 download

There's nothing in the Tailscale logs that indicates an issue.

 

I'd recommend trying to get some tailscale status output from both the server and a client while you're seeing a slow transfer, that might shed some light on the problem.

4 hours ago, EDACerton said:

 

Run this from SSH:

 

tailscale up

 

Then, once you've logged in and you see the device in the Tailscale console:

 

/usr/local/emhttp/plugins/tailscale/restart.sh

 

Thank you, the device came up as connected as soon as I ran tailscale up. Now I can access all my docker containers when adding the port numbers but can't get the Unraid webgui up. I saw this is a common issue when enabling subnets but I can't get the webgui up even when I put in the tailscale IP address

1 hour ago, rama3124 said:

Thank you, the device came up as connected as soon as I ran tailscale up. Now I can access all my docker containers when adding the port numbers but can't get the Unraid webgui up. I saw this is a common issue when enabling subnets but I can't get the webgui up even when I put in the tailscale IP address

Did you run the restart command? That's necessary to get the WebGUI to start listening on the Tailscale IP.

Yeh I ran this in SSH:

/usr/local/emhttp/plugins/tailscale/restart.sh

 

I just tried it again but it didn't help. Anything else you can recommend to troubleshoot? I can access all the docker containers fine, just not the webgui. I'll try and get the diagnostics but it could be hard since I don't have local access right now 

On 4/2/2024 at 8:26 AM, rama3124 said:

Yeh I ran this in SSH:

/usr/local/emhttp/plugins/tailscale/restart.sh

 

I just tried it again but it didn't help. Anything else you can recommend to troubleshoot? I can access all the docker containers fine, just not the webgui. I'll try and get the diagnostics but it could be hard since I don't have local access right now 

Still can't get the webgui to work. Checked ifconfig and it's tailscale1 listening. My unraid network settings has both tailscale1 and tailscale0 listening. Tried deleting tailscale0 from listening interfaces with no luck. I can access all docker containers, just not webgui. Here are the diagnostics too

Unraid-tailscale-diag-20240402-142821.zip

Quick, and probably a dumb question.  I see people posting their Tailscale settings from within Unraid, and I do not see this option under settings, nor under settings/Network Settings.  I thought it was because I was running 6.12.5, but I went ahead and upgraded to 6.12.9 this morning, and I still do not have tailscale settings anywhere in the Unraid Gui.  Any ideas?

 

First screenshot is a picture on this thread, second screenshot is a picture from my Unraid.

6 hours ago, Roncore said:

Quick, and probably a dumb question.  I see people posting their Tailscale settings from within Unraid, and I do not see this option under settings, nor under settings/Network Settings.  I thought it was because I was running 6.12.5, but I went ahead and upgraded to 6.12.9 this morning, and I still do not have tailscale settings anywhere in the Unraid Gui.  Any ideas?

 

First screenshot is a picture on this thread, second screenshot is a picture from my Unraid.

You don’t have the Tailscale plugin installed. You’re probably running the docker container. 

3 minutes ago, EDACerton said:

You don’t have the Tailscale plugin installed. You’re probably running the docker container. 

 

Yes! Any advantage to using the plugin?  Honestly I had no idea there was one, I've always ran the docker.

5 hours ago, Roncore said:

 

Yes! Any advantage to using the plugin?  Honestly I had no idea there was one, I've always ran the docker.

Yes, with the docker version if you stop your array, then docker stops and so does your Tailscale docker, so you lose remote access - this caught me out a few times when I wasn't thinking and doing some remote management. With the plugin, Tailscale is up even if the array is stopped.

I finally just got it all working so that when I use the Tailscale app on my phone I can access all my dockers via local IP wherever I am plus my NZB360 app that I use to manage my arrs also works with no need to add or change IP details of my docker containers.

I ran into many issues like other people have on this thread and found that I:

1. Had to ensure my Tailscale docker wasn't set to autostart (obvious but I accidentally forgot this bit and I want to keep it around while I make sure Tailscale plugin all works, so I've just disabled it and set it not to auto start with the array, I'll remove it soonish).

2. I advertised my subnets and set exit node but local IP still didn't work from my phone - Tailscale IP did work as expected. I found I needed to reboot my Unraid machine to ensure this worked.

Did this in the CLI of Unraid with this command: tailscale up --advertise-exit-node --accept-routes --advertise-routes=192.168.1.0/24 (replacing the IP with my own so it could be 192.168.100.0 if that was my internal network IP) - when I did that it said it needed to add some extra flags and gave me that full command which I then copy and pasted, something about disallowing DNS advertising I think?

Then you log in to the Tailscale web admin console at login.tailscale.com and approve the route settings against the machine in the menu accessed via the three dots on the right hand side of the machine listing in the Machines tab (and I also turned off key expiry).

3. In the Unraid GUI I had to go to Settings -> Network Settings -> Interface Extra -> Include Listening Interfaces and ensure that tailscale1 was applied in that.

4. Under Settings -> Docker I had to ensure Host access to custom networks: was Enabled (I have all my dockers on a custom network).

5. I could then access my dockers but a lot of them thought I was outside the network and required logins. In the pinned comment on this thread it states that you should have the "Use Tailscale Subnets" feature turned off if you're experiencing issues with access, but once I turned that to ON I found that all local IP access worked and the Tailscale plugin now thinks my phone is on the local network and everything works as expected.

That's found in Settings -> Network Services -> Tailscale -> Settings


NOTE: this is what worked for me, it may be different for others and what they need it to do.

Shout out to the great community on here.

I wish I never updated from version 11 to 12 of unraid Before Tailscale just worked with no configuring or anything, now I can't get it to work. This is so annoying. Any ideas of updates to the plugin or unraid that will make the plugin just work like before instead of messing with all these settings and possibly messing up my unraid server? 

I also noticed that when installing the plugin for tailscale it seems to name my device tower which disconnects me unraid server on my local networked computer because i'm guessing its getting confused with 2 devices with the same name. I can log into the tailscale admin and change the name from tower to something else like unraid but then it stops pinging remotely. 

Is there a way to install this plugin and make the tailscale plugin give it another name besides tower?

Edited April 4, 20242 yr by localh67
more information

HI there,

 

After setting up my new Unraid server, I installed the Tailscale Docker container. I then spoke to Spaceinvaderone, who recommended I use the plugin instead. I uninstalled the Docker container and installed the plugin. But when I try to open the app (Settings > Tailscale), I get an error that says "404 Not Found. nginx." So it doesn't even open the login page etc.

 

I've attached the log file and diagnostics from when I got this error.

 

Any help appreciated.

EDIT: Solved

 

log.txt NAS-tailscale-diag-20240404-101502.zip

Edited April 7, 20242 yr by icarus69
Added necessary attachments

12 hours ago, JebusJones said:

Yes, with the docker version if you stop your array, then docker stops and so does your Tailscale docker, so you lose remote access - this caught me out a few times when I wasn't thinking and doing some remote management. With the plugin, Tailscale is up even if the array is stopped.

I finally just got it all working so that when I use the Tailscale app on my phone I can access all my dockers via local IP wherever I am plus my NZB360 app that I use to manage my arrs also works with no need to add or change IP details of my docker containers.

I ran into many issues like other people have on this thread and found that I:

1. Had to ensure my Tailscale docker wasn't set to autostart (obvious but I accidentally forgot this bit and I want to keep it around while I make sure Tailscale plugin all works, so I've just disabled it and set it not to auto start with the array, I'll remove it soonish).

2. I advertised my subnets and set exit node but local IP still didn't work from my phone - Tailscale IP did work as expected. I found I needed to reboot my Unraid machine to ensure this worked.

Did this in the CLI of Unraid with this command: tailscale up --advertise-exit-node --accept-routes --advertise-routes=192.168.1.0/24 (replacing the IP with my own so it could be 192.168.100.0 if that was my internal network IP) - when I did that it said it needed to add some extra flags and gave me that full command which I then copy and pasted, something about disallowing DNS advertising I think?

Then you log in to the Tailscale web admin console at login.tailscale.com and approve the route settings against the machine in the menu accessed via the three dots on the right hand side of the machine listing in the Machines tab (and I also turned off key expiry).

3. In the Unraid GUI I had to go to Settings -> Network Settings -> Interface Extra -> Include Listening Interfaces and ensure that tailscale1 was applied in that.

4. Under Settings -> Docker I had to ensure Host access to custom networks: was Enabled (I have all my dockers on a custom network).

5. I could then access my dockers but a lot of them thought I was outside the network and required logins. In the pinned comment on this thread it states that you should have the "Use Tailscale Subnets" feature turned off if you're experiencing issues with access, but once I turned that to ON I found that all local IP access worked and the Tailscale plugin now thinks my phone is on the local network and everything works as expected.

That's found in Settings -> Network Services -> Tailscale -> Settings


NOTE: this is what worked for me, it may be different for others and what they need it to do.

Shout out to the great community on here.

 

 

This is amazing, thank you so much!  I will switch over to the plugin next week and hope for the best!!  Somebody should sticky this post.

18 hours ago, JebusJones said:

Yes, with the docker version if you stop your array, then docker stops and so does your Tailscale docker, so you lose remote access - this caught me out a few times when I wasn't thinking and doing some remote management. With the plugin, Tailscale is up even if the array is stopped.

I finally just got it all working so that when I use the Tailscale app on my phone I can access all my dockers via local IP wherever I am plus my NZB360 app that I use to manage my arrs also works with no need to add or change IP details of my docker containers.

I ran into many issues like other people have on this thread and found that I:

1. Had to ensure my Tailscale docker wasn't set to autostart (obvious but I accidentally forgot this bit and I want to keep it around while I make sure Tailscale plugin all works, so I've just disabled it and set it not to auto start with the array, I'll remove it soonish).

2. I advertised my subnets and set exit node but local IP still didn't work from my phone - Tailscale IP did work as expected. I found I needed to reboot my Unraid machine to ensure this worked.

Did this in the CLI of Unraid with this command: tailscale up --advertise-exit-node --accept-routes --advertise-routes=192.168.1.0/24 (replacing the IP with my own so it could be 192.168.100.0 if that was my internal network IP) - when I did that it said it needed to add some extra flags and gave me that full command which I then copy and pasted, something about disallowing DNS advertising I think?

Then you log in to the Tailscale web admin console at login.tailscale.com and approve the route settings against the machine in the menu accessed via the three dots on the right hand side of the machine listing in the Machines tab (and I also turned off key expiry).

3. In the Unraid GUI I had to go to Settings -> Network Settings -> Interface Extra -> Include Listening Interfaces and ensure that tailscale1 was applied in that.

4. Under Settings -> Docker I had to ensure Host access to custom networks: was Enabled (I have all my dockers on a custom network).

5. I could then access my dockers but a lot of them thought I was outside the network and required logins. In the pinned comment on this thread it states that you should have the "Use Tailscale Subnets" feature turned off if you're experiencing issues with access, but once I turned that to ON I found that all local IP access worked and the Tailscale plugin now thinks my phone is on the local network and everything works as expected.

That's found in Settings -> Network Services -> Tailscale -> Settings


NOTE: this is what worked for me, it may be different for others and what they need it to do.

Shout out to the great community on here.

Thank you so much for writing this up, I'd been wrestling with all of this for probably a week.

On 4/4/2024 at 10:13 AM, icarus69 said:

HI there,

 

After setting up my new Unraid server, I installed the Tailscale Docker container. I then spoke to Spaceinvaderone, who recommended I use the plugin instead. I uninstalled the Docker container and installed the plugin. But when I try to open the app (Settings > Tailscale), I get an error that says "404 Not Found. nginx." So it doesn't even open the login page etc.

 

I've attached the log file and diagnostics from when I got this error.

 

Any help appreciated.

 

log.txt 19.01 kB · 0 downloads NAS-tailscale-diag-20240404-101502.zip 133.24 kB · 0 downloads

 

Bump

This plugin seems to be averaging around 42% cpu which seems a bit on the high side. 

It's a newish 13-600H with aes chip built in etc. 

 

I run tailscale on my pfsense router but added this plugin as a backup.

 

What do others see cpu wise?

Edited April 5, 20242 yr by dopeytree

On 4/5/2024 at 9:32 AM, icarus69 said:

 

Bump

I think I posted to you on Reddit as well... it looks like your server can't contact the Tailscale control servers.