Jump to content

EDACerton

Community Developer
  • Posts

    358
  • Joined

  • Last visited

  • Days Won

    1

Report Comments posted by EDACerton

  1. 6 minutes ago, zarkoff said:

    Hi,

    Just to make sure I understand (I'm not an expert).

    On 6.11.5, you have Tailscale docker running and that's all. So I can connect on my phone for example.

    On 6.12.0, you have Tailscale docker running and you have to add something extra interface and edit a config file somewhere (this part looks very complex for me, no clue what is the "go" file) ?

    Is that correct ? If so, I'll be sticking with 6.11.5 for a while yet...

    You can also use the plugin, which does all of the work for you. 😃

    • Like 1
  2. 1 minute ago, bmpreston said:

    Is anyone else having issues with accessing the UI of unraid after the RC8 launch, USING the MagicDNS name of Tailscale?

     

    I can ping the box, I can access ANY AND ALL webui of any hosted Docker with my magicDNS; I can access the box with the interface IP; I CANNOT access the box with the MagicDNS name of the box on port 80.  

     

    • Ping 10.0.0.250. 
    • Ping unraid 
    • ping FULL unraid tailnet name 
    • WebUI of http://10.0.0.250 
    • WebUI of http://10.0.0.250:8989 <--Docker of Sonarr 
    • WebUI of http://Unraid:8989 <--Docker of Sonarr 
    • WebUI of http://Unraid:80 (Port Number not necessary; clarifying) 

    Which version of Tailscale? The plug-in or the docker container?

  3. 50 minutes ago, Monark said:

     

    After upgrading to rc8 I reinstalled the Tailscale plugin, took me a while to notice ssh was no longer functional. If I uninstall the Tailscale plugin and /etc/rc.d/rc.ssh start it works as expected.

     

    There will be a plug-in update released tomorrow that might help with this. 

  4.  

    7 minutes ago, exico said:

     

    I understand that they are working on it for another release but there is a fix or configuration that i can set to make it work in the mean time?

    Maybe in the Samba Extra configuration?

    I use Wireguard to connect two servers in different locations and this will break things

     

    Unfortunately, there's not a simple workaround that I could find based on how the change was done in rc6. I could kind of make it work, but it was super hacky and wouldn't be reliable in some network configurations :(.

     

    I just figure that we'll have to wait until the fix is released to get a good solution for this one.

  5. 30 minutes ago, baujahr said:

    These changes need to be optional, I'm using Tailscale (via Docker) and a Wireguard tunnel to access the server and this has stopped smb and ssh from working.

    Automatically adding the only Wireguard tunnel solves half of my problem as remote users access via Tailscale.

    This is already being worked on:

     

     

  6. What's the motivation for these changes?

     

    Quote
    • rc.samba - let smb, nmb service listen on regular interfaces only which have an IP address, this includes the primary interface + set ipv4 / ipv6 support (also for wsdd2)
    • rc.ssh - listen on regular interfaces only which have an IP address, this includes the primary interface + set ipv4 / ipv6 support

     

    As implemented, this breaks Samba and SSH access for plugins which bring VPN connections (specifically in my case, Tailscale).

×
×
  • Create New...