Community Developer
  • Posts

  • Joined

  • Last visited


  • Gender

Recent Profile Visitors

1815 profile views

dsmith44's Achievements


Apprentice (3/14)



  1. latest = 1.32.3 = 1.32 Largely a security fix for Windows versions
  2. If you can connect with 100.x.x.x:port then tailscale is working, so not sure this is the right place to ask I'm afraid.
  3. That's not quite true. The tailscale daemon runs in the container, but as the container is set to use host networking it's using the unraid network stack. @RyanRoberts210 try using the tailscale ip addresses directly instead of discovery, that should work to my mind.
  4. 1.30 = 1.30.2 = latest new version pushed
  5. What do you mean by 'I can't access anytbing'? Can you ping the IP address of the unraid box over tailscale ( the 100.x.x.x adress ) ?
  6. On that subject get a cheap USB serial adapter and connect it to something else I have mine connected to a pinhole, then I always have a serial console.
  7. I don’t think there is a Slackware build provided by tailscale. So if you want - get golang installed, compile from source (https://github.com/tailscale/tailscale) and setup, that will probably work. How you get it to start at boot, not stop with array etc I don’t know. Would probably warrant a plug-in being written or put in a feature request Dean
  8. Maybe - You are on your own however I think that if you are running tailscale in host mode, the default, then any other containers running in host mode should be able to connect to tailscale ip addresses. However I have never tested this, won't be testing it, and certainly won't be support it as a use case. Sorry.
  9. I'm sorry, this isn't really a tailscale docker issue. I would suggest talking to nextcloud maintainers and/or wider unraid community. This is behaving exactly as planned. However a few comments. Unraid isn't using the tailscale cert, so it exists in the docker container data in /mnt/user/appdata tailscale somewhere, but unraid won't be picking that up. You may not want it to anyway as then _only_ the unraid.<server-alias>.ts.net will ever be valid. If you do, I'd look into putting something inti /boot/config/go to put the certs in the right place, but you'd have to ask elsewhere for where that is.
  10. Are the routes enabled in the tailscale admin console? If not they won't work. https://tailscale.com/kb/1019/subnets/ If they are I'd check the networking mode of the docker container. From your description I think you will need to ensure it's running in host mode, ie. using the network stack of the main unraid server. To be honest this is unsupported config for this container. If you read back in the history, and is really just there via the additional flags for people that need it, understand it and can troubleshoot. I'm just not setup to do network troublshooting. My advice for exit nodes it not to run them in docker, put tailscale on a firewall/raspberry pi/anything else. Inside docker, in unraid, is always going to be complicated to diagnose without intimate knowledge of how docker networking interacts with underlying unraid config, linux kernel and tailscale.
  11. As I have said before.... Please note I normally skip 1.xx.0 releases as there are often bug fix releases shortly afterwards. In any event I will wait at least two weeks after a 1.xx.0 release before updating latest, or normally even pushing a build. I have now added this to the front page of this support article. However I have now pushed dev-1.28.0, but this is untested, so use at your own risk.
  12. 1.26.1 == 1.26 == latest - New version pushed.
  13. There quite open about how it all works, and from my understanding their piece just facilitates the setup of connections, they never see the keys. https://tailscale.com/blog/how-tailscale-works/