EDACerton
Community Developer
-
Joined
Everything posted by EDACerton
-
Please follow the instructions in the pinned post and provide Tailscale diagnostics.
-
If you're needing to run an actual executable file, you would need to have your script copy it somewhere on the RAM filesystem (like /usr/local/bin/), set +x there, then run the file.
-
Everything works fine for me.
-
I'd guess that you turned on "Use Tailscale DNS Settings" and/or set --accept-dns from the CLI. If that's the case, you should turn that off.
-
My general take on Headscale is pretty simple: If you want to run Headscale because you think it's fun to do, go for it If you want something simple/easy/that just works, use Tailscale. If you don't want to trust the Tailscale control servers, but still want something simple/easy/that just works, use Tailscale with Tailscale Lock. I generally put Tailscale in the "better to use a service" category, similar to how folks would use Dynamic DNS services instead of trying to self-host their own public DNS.
-
MagicDNS doesn’t have any impact on whether a connection is relayed or not. Putting in server.something.ts.net should be no different than connecting to 100.x.y.z.
-
https://tailscale.com/kb/1257/connection-types
-
If I had to guess, you were sending traffic through a relay connection and not getting a direct connection. This can happen due to some firewall/router configurations. Without seeing specific details, though, all I can really do is guess on that. I don't have any speed issues with Tailscale; I even use Tailscale for LAN connections. (The only thing that doesn't run over TS is the 10Gbps backup server connection).
-
You could technically install a Headscale container on your server and expose it to the internet, although in general I wouldn't recommend doing so. (The whole reason I started writing the Tailscale plugin was because, when I was using the Tailscale docker image, if the array was stopped I would lose access to the WebGUI... if you put the control server on the Unraid server, you're right back in the same spot 🤪).
-
I've created a bug report for beta 4 for this:
-
References: User report in Tailscale support thread re: Samba failing after upgrade to 7.0b4, https://forums.unraid.net/topic/136889-plugin-tailscale/?do=findComment&comment=1477994link Github commit modifying rc.samba, https://github.com/unraid/webgui/commit/3c007fa1d0ed8fb08c70b304702123942430b0fd#diff-476bdaaff21a471f91a251c41b5198d90aad63470eca00ad7de8dc675e33310eR193 I reviewed the diagnostics file that this user provided and can see that the Tailscale IP is being added to smb-names.conf as expected. However, Samba is still not listening on the Tailscale IP after the reload. It seems that reload-config might not be applying the interfaces. If this is the case, a race condition is created between the array and Tailscale, particularly if auto-start is enabled: If Tailscale obtains an IP before the array starts for the first time, Samba works correctly. If the array starts before Tailscale obtains an IP, Samba will not respond on the Tailscale IP, even after it is reloaded.
-
Do you know what startup script it was that did this? I’m curious to see what can interfere that way.
-
I never said it was supported, I said it was out of the box 😂
-
If anyone would like to try something out of the box, I started playing with Grub2 as a bootloader for Unraid instead of syslinux. IMPORTANT DETAILS This will only change the UEFI bootloader; if you are using legacy boot, it will do nothing. Before installing, you should have access to both the Unraid server and a computer that you can use to modify the flash drive (in case you need to restore the default loader). If you have problems booting via the new bootloader, remove the EFI folder and restore the EFI- folder. Installation Rename the existing EFI folder on the flash drive back to EFI- (this is your backup folder in case you have issues) Copy the EFI and grub folders from the ZIP file to the flash drive. Details on the creation process and boot config here: https://gist.github.com/dkaser/18064a5a7d282c3d1b59eb4ee901242b grub-test.zip
-
I'm not quite sure what to make of your logs. It looks like Tailscale isn't installing completely, but I can't tell why. The files all look like they're present, but the Tailscale services aren't actually starting. What happens if you open up a console and run: tailscale status ?
-
Slackware (the upstream Linux distro) has has similar issues with "black screen" booting. With the latest release, they switched to Grub2 instead of LILO/ELILO (which, like syslinux [that Unraid uses] haven't been updated since 2014/2015). Hopefully, at some point Unraid can look at making a similar switch.
-
This would be better posted in the Programming forum, this thread is for support of the CA plugin itself. One thought to consider before posting there: I don't know of any plugins that exist to install specific containers. Why not use Docker Compose for this? Multi-container applications is it's specialty
-
You’re out of scope for the plugin at that point, questions about setting up pihole/etc. as the DNS for your tailnet would be better addressed by either whoever made the guide you’re following (if you’re using one) or a more Tailscale-focused forum. I’m happy to help with issues with the plugin itself, but I don’t have the time to do personal consulting for how to set up your tailnet services.
-
You don’t need —accept-routes to be able to advertise a subnet route. They are opposite sides of the same function.
-
It allows Tailscale to send traffic to the networks advertised by subnet routers. It’s helpful for client devices that roam. It’s usually not helpful for servers.
-
https://selfhosters.net/remote/tailscale/advanced/ For your connectivity problem — my guess is that you can probably get to the WebGUI using the Tailscale IP, if you can, turn off accept-routes. If that doesn’t work, disable the routes on the Tailscale admin console side and you will get back in. Then turn off accept-routes.
-
Try switching to the Preview version, that has version 2024.10.19 now, let me know if that fixes it for you.
-
Give me about 10 minutes and I should have a fix to the preview branch.
-
And in the meantime, I'm looking to see what could cause that particular error... have either of you previously disabled Tailscale in the settings?
-
Upload as an attachment here.
