How to update to the latest Tailscale version?
-
I stopped using the logout command in the last update; as far as I could tell, it does nothing after 'service tailscaled stop'.
At the end of last year, I decided to do a clean restart and, afterward, apply all Tailscale updates and settings changes via SSH. I uninstalled the tailscale package, then deleted all leftover tailscale files and settings. After that, I reinstalled the package and then updated Tailscale via SSH from Freshports. Since then, no errors, no need to generate new keys or re-authenticate.
I always need to re-advertise routes after every update and after the rare pfSense reboot. I have searched for a solution, but none of the suggestions have seemed worth pursuing.
-
tailscale logout is not required to prevent the corruption event. The only thing that is absolutely required is to manually stop the tailscale service, whether by disabling Tailscale in the VPN menu of the Web Configurator or by command-line as @CarlMRoss alluded to. I just tested this myself as my pfSense box was still running 1.94.1 and had no issues.
-
New Tailscale pricing. Positive changes overall
https://tailscale.com/blog/pricing-v4
+Unlimited devices, up to 6 users
-3 ACL groups, 50 tagged resources
?1000 (Temporary) ephemeral resources
-
No login or authentication issues this time.
Updated CE 2.8.1 to 1.96.4_1
pkg add -f https://pkg.freebsd.org/FreeBSD:15:amd64/quarterly/All/tailscale-1.96.4_1.pkg -
@elvisimprsntr said in How to update to the latest Tailscale version?:
No login or authentication issues this time.
Wasn't the case for me. Even though I stopped the Tailscale service before updating, I still had to reauthenticate using the existing key. Thankfully it didn't take much time to fix thanks to the discussion here.
It's weird that it's so unpredictable though.
-
Updated to version 1.96.4_1, no issues, no errors.
System: pfSense+ 26.03, Tailscale Package 0.1.9_2, Package Dependencies: tailscale-1.94.1, Freshports-tailscaled version 1.96.4_1
I’ve seen unpredictable behavior since I started doing FreshPorts updates on pfSense+ 24.x. What has worked better for me is stopping the service before the update and restarting it afterward. After reboots, I’ve sometimes had to run some version of service tailscaled stop, service tailscaled start, and tailscale up to get things stable again.
-
said in How to update to the latest Tailscale version?:
Updated to version 1.96.4_1, no issues, no errors.
Updated to version 1.96.4_2
service tailscaled stopfetch https://pkg.freebsd.org/FreeBSD:16:amd64/latest/All/tailscale-1.96.4_2.pkg || exit 1 && pkg-static add -f tailscale-1.96.4_2.pkg && rm -f tailscale-1.96.4_2.pkg && service tailscaled startAfter upgrading pfSense+ to 26.03, I added advertised routes in the Tailscale web GUI, and there have been no issues with Tailscale updates or pfSense reboots since then.
-
Updated CE 2.8.1 to 1.98.2
pkg add -f https://pkg.freebsd.org/FreeBSD:15:amd64/quarterly/All/tailscale-1.98.2.pkg -
Updated CE 2.8.1 to 1.98.3
pkg add -f https://pkg.freebsd.org/FreeBSD:15:amd64/latest/All/tailscale-1.98.3.pkg -
Updated CE 2.8.1 to 1.98.4
pkg add -f https://pkg.freebsd.org/FreeBSD:15:amd64/latest/All/tailscale-1.98.4.pkg -
Updated CE 2.8.1 to 1.98.5_1
pkg add -f https://pkg.freebsd.org/FreeBSD:15:amd64/latest/All/tailscale-1.98.5_1.pkg
