Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

7 Neutral

About dsmith44

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

597 profile views
  1. If the influx container is only listening on the ETH1 ip address, bridge mode, then I'm afraid this container probably isn't going to work for you. This will only allow you to access containers that listen on the tailscale interface ip address itself, not eth1, eth2 or any other interfaces. It is not providing a gateway to 'other networks' just exposing the Unraid server itself to tailscale.'other networks' in this context means absolutely anything that isn't the IP address of the tailscale interface. If you can make influxDB also bind to the tailscale interface then it will work. I'm not keen on trying to turn this into a VPN gateway solution, nor am I sure that's even possible with a docker container rather than a plugin.
  2. I don't know what people have against the poor venerable while loop 😎, but I have changed to use a 'sleep infinity' instead which is slightly cleaner. Whilst your method will work, and is elegant, it's less 'obvious' about ordering, so I think I'll leave that alone.
  3. Re: host vs bridge mode Having thought this through I feel host is the correct mode for this to operate in. Host means the networking is part of the base host networking so if the host can see the port tailscale will be able to as well. However that relies on the mapped ports listening on all addresses, which if I check my unraid server they do. root@unraid:~# ss -ltu Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process .. tcp LISTEN 0 128 *:8200 *:* .. However the only IP address that you'll be able to access through tailscale will be the tailscale ip address itself, trying to use a LAN address, a docker bridge network address or any other address is going to fail as we aren't doing subnet forwarding. I am not currently keen on even trying to add subnet forwarding to this container as it was never my intention to create a VPN gateway, just to allow access to Unraid services from tailscale. I am also not sure if this is even necessarily possible without additional steps outside of the container itself; if I look in the Apps list OpenVPN server is available as a plugin but not as a container. So building a plugin is likely a better route for someone to look at, but not something I'm going to get into. I would suggest using the built in wireshark support if you want to get a VPN connection to the whole network.
  4. Fixed, bit embarrasing that one... thanks.
  5. I will do some testing and perhaps change the definition to prefer bridge networking instead, my docker networking is a bit rusty so time for some reading I think.
  6. Version 0.98.1 is now available which contains the upstream fix for the issues in 0.98 :latest will contain this fix, 0.98.1 will contain this fix.
  7. My apologies, I shouldn't have pushed this as hadn't tested myself, thinking just a simple point update. This is broken currently and I don't know why. The STUN process isn't working in 0.98 in this docker container, I am going to build using their official Dockerfile and test outside of Unraid. If it doesn't work there either will submit a bug report, if it does then at least I can start narrowing down the cause. For now please use deasmi/unraid-tailscale:0.97 Update: I have recreated the issue on stand alone Ubuntu server and submitted issue to tailscale https://github.com/tailscale/tailscale/issues/368
  8. Tailscale is, in my view, scratching a sligtly different itch. It is still wireguard, but it's wireguard plus NAT busting and zero management of many to many connections. I'm not just using this to connect to my unraid server, but also virtual servers. Unraid is joining my mesh here, this isn't providing access to my LAN remotely. If you want a hub and spoke model I'd suggest still using out of the box wireguard, if you want genuine point to point this is much easier to setup.
  9. I had not intended this to be used for network access, to me tailscale is about point to point communications, so I run it everywhere. However that's just me, I'm glad you got it to work, and I might have a look at including an environmental variable to enable network routing when I get a moment. This is a slightly kludgy solution using NAT on the outbound though rather than seting up full network routability.
  10. Apologies, I wasn't watching this topic for some reason. The log in question is the docker log, just click the log button on the far right of the docker screen in the tailscale row.
  11. s3_sleep is installed and the sleep button in the top right is working fine. I have tracked this down to Dynamix System Temp plugin - uninstall that and sleep reappears on the tool bar. Re-install the System Temp plugin and it's gone again.
  12. Hi. I am having trouble with the sleep function. This used to work fine, and is very useful, but now sleep is ghosted out on the command strip. I've reinstalled the plugin, and wiped all trace from /boot first, as well as the s3_sleep plugin. Any ideas what could be causing this? The server sleeps find from the s3_sleep buttons. Thanks
  13. I have no idea I'm afraid, I would suggest a quick download of the client from https://tailscale.com to check.
  14. This is the support thread for deasmi/unraid-tailscale docker CA. TailScale - Private networks made easy Connect all your devices using WireGuard,® without the hassle. Tailscale makes it as easy as installing an app and signing in. This container sets up tailscale for unraid. Tailscale is a managed point to point VPN using wireguard. It will register as hostname unraid, if you want to change that see 'Extra Parameters' in the container config and change to the hostname you would like. ** IMPORTANT When you first start this container you must check the log file for the logon URL and then enter it into a browser and logon to tail scale. I would then also advise setting the keys to not expire for your unraid host ** You need to look for the following in the log ** Note that this will expose your whole server into your tailscale VPN network ** Do not do this if you do not understand what that means.
  15. Hello, I had an issue with an SSD that is part of my three drive cache, I think due to cabling, lots of CRC errors Reseating all the cables and booting back into rescue mode I ran Btrfs scrub on the device and it corrected some 1,000,000 errors correctly, no failed repairs. Rebooted into unraid full and it for some reason then ran a resize for two hours then settled down again. Finally I have a situation where the actual Btrfs seems fine although in need of a balance, but unraid thinks only two of the three disks are actually in the cache. Smarctl -t on affected SSD is showing nothing. Not quite sure how to progress, any ideas? Thanks root@unraid:~# btrfs fi show /mnt/cache Label: none uuid: 80776be4-065e-404e-a103-acb4b5026956 Total devices 3 FS bytes used 322.01GiB devid 1 size 256.17GiB used 256.17GiB path /dev/sdi1 devid 2 size 447.14GiB used 70.00GiB path /dev/sdg1 devid 3 size 447.14GiB used 322.17GiB path /dev/sdh1 root@unraid:~# btrfs fi usage /mnt/cache Overall: Device size: 1.12TiB Device allocated: 648.34GiB Device unallocated: 502.11GiB Device missing: 0.00B Used: 644.03GiB Free (estimated): 251.72GiB (min: 251.72GiB) Data ratio: 2.00 Metadata ratio: 2.00 Global reserve: 240.80MiB (used: 0.00B) Data,RAID1: Size:322.14GiB, Used:321.47GiB /dev/sdg1 69.00GiB /dev/sdh1 320.14GiB /dev/sdi1 255.14GiB Metadata,RAID1: Size:2.00GiB, Used:553.47MiB /dev/sdg1 1.00GiB /dev/sdh1 2.00GiB /dev/sdi1 1.00GiB System,RAID1: Size:32.00MiB, Used:96.00KiB /dev/sdh1 32.00MiB /dev/sdi1 32.00MiB Unallocated: /dev/sdg1 377.14GiB /dev/sdh1 124.97GiB /dev/sdi1 1.01MiB root@unraid:~# unraid-diagnostics-20190930-2242.zip