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

On 7/19/2023 at 3:57 PM, 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 7/19/2023 at 9:06 AM, 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. 

+1

 

Long time Unraid and ZeroTier user and forum lurker here. If the "fix" is to stage a reload of services after Docker starts, then that should be the default behavior of Unraid when "Include listening interfaces" is enabled, etc.

On 7/19/2023 at 2:57 PM, 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.

 

I too am experiencing this issue. I access unraid remotely via ZeroTier. I had to restart recently and then was unable to access without visiting the site, un-setting and resetting. 

 

At a fundamental level, if a user sets a parameter in a user interface, it is expected that this parameters will persist between reboots unless specifically states otherwise. Even then, if the user reboots the system and sees the parameters still set in the GUI then it should still be set, not required to be unset and reset to really be set. 

 

I shouldn't expect that anyone would disagree with this.

Sorry for bumping this thread, but to me, this is a show-stopping issue. If I can't access SMB shares over Tailscale then I'll have to roll back until the Unraid team fixes the regression. The entire point of my NAS is to be able to access my files remotely. I am not interested in modifying my go file with yet another hack that will inevitably break something in a future update.

Edited August 29, 2023 by djbrettb
typo

The issue persists as of 6.12.4.

Also on 6.12.4, can't access SSH over tailscale...  Not interested in hacking up the go file.

Just upgraded to 6.12.4 and to my surprise, tailscale stopped working for the unRaid WebUI. I'm kind of surprised that this problem was flagged two months ago and is still in the fourth patch release. Hopefully it will get a proper fix soon.