[6.12.0] Tailscale: SMB, SSH, and Gui unable to connect

To make this work you need to have the docker service and autostart for tailscale containerr enabled

 

There is a bug in SMB not properly updating when interfaces change, this will be corrected in the next release.

 

Changed Priority to Annoyance

7 minutes ago, bonienl said:

To make this work you need to have the docker service and autostart for tailscale containerr enabled

 

There is a bug in SMB not properly updating when interfaces change, this will be corrected in the next release.

 

Alrighty, I made the changes to the docker service & autostart for Tailscale container. It did start the container successfully. However, it’s still denying me to use SSH & the GUI. Unless I delete the tailscale0 then re-add it back in, then it works. 
 

I’ll be looking forward for the next release for SMB! 
 

Thank You! 

10 minutes ago, DC_Interstellar said:

However, it’s still denying me to use SSH & the GUI. Unless I delete the tailscale0 then re-add it back in, then it works. 

 

This requires additional scripting.

What do you have in your 'go' file?

 

34 minutes ago, bonienl said:

 

This requires additional scripting.

What do you have in your 'go' file?

 

I’ve added this code above the emhttpd in the go file

 

# reload services after starting docker with 20 seconds grace period to allow starting up containers
event=/usr/local/emhttp/webGui/event/docker_started
mkdir -p $event
cat <<- 'EOF' >$event/reload_services
#!/bin/bash
echo '/usr/local/emhttp/webGui/scripts/reload_services' | at -M -t $(date +%Y%m%d%H%M.%S -d '+20 sec') 2>/dev/null
EOF
chmod +x $event/reload_services

 

Edited June 17, 2023 by DC_Interstellar

That looks alright and should enable tailscale properly.

 

For me GUI and SSH access over tailscale work fine after array stop/start. I access by IP address.

 

17 minutes ago, bonienl said:

That looks alright and should enable tailscale properly.

 

For me GUI and SSH access over tailscale work fine after array stop/start. I access by IP address.

 

Interesting… It might be my coding?  To double make sure of myself. This is what I currently have in my “go” file. Please correct me if the coding is incorrect. 

 

#!/bin/bash
# Start the Management Utility
# reload services after starting docker with 20 seconds grace period to allow starting up containers
event=/usr/local/emhttp/webGui/event/docker_started
mkdir -p $event
cat <<- 'EOF' >$event/reload_services
#!/bin/bash
echo '/usr/local/emhttp/webGui/scripts/reload_services' | at -M -t $(date +%Y%m%d%H%M.%S -d '+20 sec') 2>/dev/null
EOF
chmod +x $event/reload_services
/usr/local/sbin/emhttp &

 

9 hours ago, bonienl said:

To make this work you need to have the docker service and autostart for tailscale containerr enabled

 

There is a bug in SMB not properly updating when interfaces change, this will be corrected in the next release.

 

 

Okay that is very good to know, because I can't get SMB to work at all with any interface that is not the default bond0.

Edited June 17, 2023 by Spiritreader

I also have the SMB not working issue with ZeroTier.

 

This seems to be an urgent problem for many, as many seem to use Zerotier, Tailscale, Netbird, Netmaker or others. GUI and FTP work fine, but SMB not.

Edited June 17, 2023 by TBT

Yup. I'm encountering this issue as well (both ZT and Tailscale). The only temporary workaround for me at the moment is downgrading back to 6.11 since everything was working up until this 6.12.0 update. 

 

Issue persists with both the plugin Tailscale and the docker Tailscale/ZeroTier

Have the same issue here with Tailscale for both plugin and docker

Edited June 19, 2023 by harguna

I wonder if this is an IPv6 issue as mentioned here:

 

I'm also having trouble connecting to SMB over the Tailscale plugin. With SSH I am able to connect by patching the rc.d file while the server is running. Maybe SMB requires a similar patch/fix?

Changed Status to Retest

UPDATE: v6.12.1 was just barely released to fix the SMB issue. Retesting to confirm that after reboot of the Unraid Server that the "go" file code will allow the "Include listening interfaces" in Settings>Network Settings to work and stay the same without manually editing it every time the server restarts.

The code in the 'go' file needs a small revision.

The 'at' command does not support a waiting time in seconds, eventhough it can be given.

The updated code below properly waits 20 seconds.

 

# reload services after starting docker with 20 seconds grace period to allow starting up containers
event=/usr/local/emhttp/webGui/event/docker_started
mkdir -p $event
cat <<- 'EOF' >$event/reload_services
#!/bin/bash
echo 'sleep 20;/usr/local/emhttp/webGui/scripts/reload_services' | at -M now 2>/dev/null
EOF
chmod +x $event/reload_services

 

12 minutes ago, bonienl said:

The code in the 'go' file needs a small revision.

The 'at' command does not support a waiting time in seconds, eventhough it can be given.

The updated code below properly waits 20 seconds.

 

# reload services after starting docker with 20 seconds grace period to allow starting up containers
event=/usr/local/emhttp/webGui/event/docker_started
mkdir -p $event
cat <<- 'EOF' >$event/reload_services
#!/bin/bash
echo 'sleep 20;/usr/local/emhttp/webGui/scripts/reload_services' | at -M now 2>/dev/null
EOF
chmod +x $event/reload_services

 

 

Perfect! That worked!! Thank you so much @bonienl and the Unraid development team for all the hard work ya'll put in!!

 

Marking issue as resolved. Closing it in a couple of days from now.

Edited June 20, 2023 by DC_Interstellar

Changed Status to Solved

6 hours ago, bonienl said:

The code in the 'go' file needs a small revision.

The 'at' command does not support a waiting time in seconds, eventhough it can be given.

The updated code below properly waits 20 seconds.

 

# reload services after starting docker with 20 seconds grace period to allow starting up containers
event=/usr/local/emhttp/webGui/event/docker_started
mkdir -p $event
cat <<- 'EOF' >$event/reload_services
#!/bin/bash
echo 'sleep 20;/usr/local/emhttp/webGui/scripts/reload_services' | at -M now 2>/dev/null
EOF
chmod +x $event/reload_services

 

 

 

Sorry, really stupid noob question: Where is this 'Go' file and how do I configure/access it from a Mac?

2 hours ago, calvintse said:

 

 

Sorry, really stupid noob question: Where is this 'Go' file and how do I configure/access it from a Mac?

/boot/config/go

Best if you do this change directly into your Unraid GUI

Edited June 21, 2023 by DC_Interstellar

Closing issue

Changed Status to Closed

On 6/22/2023 at 8:37 PM, DC_Interstellar said:

Changed Status to Closed

 

I'm sorry, but I disagree with this issue being closed. Tailscale used to work perfectly fine on Unraid 6.11.x and now it's broken even on 6.12.3 (which is what I'm on), due to whatever reason that didn't exist on the previous minor release.

 

I don't see myself fuzzing in the go file just to get a particular docker container working that should be working out of the box as it used to be.

39 minutes ago, drdebian said:

 

I'm sorry, but I disagree with this issue being closed. Tailscale used to work perfectly fine on Unraid 6.11.x and now it's broken even on 6.12.3 (which is what I'm on), due to whatever reason that didn't exist on the previous minor release.

 

I don't see myself fuzzing in the go file just to get a particular docker container working that should be working out of the box as it used to be.

So, you’re saying you will not go into the go file & add the short script that’ll take you a couple seconds? If you can’t do that. Then okay.

Not be rude or anything, we can’t help you if don’t add it in. All of us were able to get working & it’s great! I, myself, suggest adding it in, but again. It’s up to you if want to or not. 

40 minutes ago, DC_Interstellar said:

So, you’re saying you will not go into the go file & add the short script that’ll take you a couple seconds? If you can’t do that. Then okay.

Not be rude or anything, we can’t help you if don’t add it in. All of us were able to get working & it’s great! I, myself, suggest adding it in, but again. It’s up to you if want to or not. 

 

It's definitely not that I couldn't add something to the go file, quite to the contrary.

 

The problem I have with this is that this feels like an ugly hack that should not be necessary. I really don't understand what has changed from 6.11.x to 6.12.3 that suddenly prevents Unraid from listening to the tailscale network without having its services reloaded in the go file. Something this fundamental should be made available somewhere in the Unraid settings IMHO, especially if people confronted with this new behaviour see downgrading to the previous minor release as their only option.

On 7/19/2023 at 8:57 AM, drdebian said:

 

It's definitely not that I couldn't add something to the go file, quite to the contrary.

 

The problem I have with this is that this feels like an ugly hack that should not be necessary. I really don't understand what has changed from 6.11.x to 6.12.3 that suddenly prevents Unraid from listening to the tailscale network without having its services reloaded in the go file. Something this fundamental should be made available somewhere in the Unraid settings IMHO, especially if people confronted with this new behaviour see downgrading to the previous minor release as their only option.

 

+1 on this sentiment.