Viktor Jaep
Part of the Furniture
You may be able to use this command... (untested)Is there a way I can retry this upgrade?
(How) Can I downgrade to 1.66.4 to test this?
Code:
Tailscale update --version="1.66.4"
You may be able to use this command... (untested)Is there a way I can retry this upgrade?
(How) Can I downgrade to 1.66.4 to test this?
Tailscale update --version="1.66.4"
I tried this once on the Router but it didn’t work; it worked on my RPi4 though.You may be able to use this command... (untested)
Code:Tailscale update --version="1.66.4"
Did not work for me either:I tried this once on the Router but it didn’t work; it worked on my RPi4 though.
If the above doesn’t work I think the next easiest way is to just copy any custom command lines and screenshot configs, uninstall TAILMON then reinstall it. The base Entware Tailscale version is v1.58.2.-1; and then just update from there.
➜ tailscale update --version="1.66.4"
installed stable version 1.68.0 is newer than the latest available version 1.66.4; no update needed
Assuming you used the (P) method under the setup/config menu? When it failed to start?Did not work for me either:
Code:➜ tailscale update --version="1.66.4" installed stable version 1.68.0 is newer than the latest available version 1.66.4; no update needed
I don’t want to risk my setup now; I’ll have a look at the next Tailscale update.
Yes.Assuming you used the (P) method under the setup/config menu? When it failed to start?
Running 1.0.17b1? The beta includes a key press event after the update to pause for any errors or abnormalities.Yes.
Just remembered this post where the downgrade didn’t work.Did not work for me either:
Code:➜ tailscale update --version="1.66.4" installed stable version 1.68.0 is newer than the latest available version 1.66.4; no update needed
I don’t want to risk my setup now; I’ll have a look at the next Tailscale update.
No, 1.0.14, but if the below instructions indeed work (and I think they will), I can test both.Running 1.0.17b1? The beta includes a key press event after the update to pause for any errors or abnormalities.
Excellent! I hope to give this a try later today or this weekend.Just remembered this post where the downgrade didn’t work.
But I remember what I did now.
IIRC I got the Tailscale binaries from pkgs.tailscale.com/stable/, then selected the older version using the dropdown. You need to navigate to static binaries (other distros) and select arm64. I have linked the 1.66.4 directly in any case.
Extract the two Tailscale files and use WinSCP to copy the two files into /opt/bin/. You can just overwrite the existing ones.
Per my older post you will need to stop Tailscale (via TAILMON) to be able to copy the files across (and please turn off Keep Alive and Restart ). After copying the files, restart Tailmon and you should have the older version installed. Make sure it is running with your system (as before) and then upgrade.
It’s literally a 3 minute downgrade, just turn off one setting (Keep Alive).
k.
curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/TAILMON/develop/tailmon.sh" -o "/jffs/scripts/tailmon.sh" && chmod 755 "/jffs/scripts/tailmon.sh"
curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/TAILMON/master/tailmon.sh" -o "/jffs/scripts/tailmon.sh" && chmod 755 "/jffs/scripts/tailmon.sh"
The downgrade instructions from @jksmurf worked (as expected).@XIII ... just wanted to let you know I attempted the upgrade from v1.66.4 to v1.68.0 on my test router, and went flawless... Again, I'm on v1.0.17b1...
Messages:
Executing: tailscale up --advertise-exit-node --advertise-routes=192.168.1.0/24
Error: changing settings via 'tailscale up' requires mentioning all
non-default flags. To proceed, either re-run your command with --reset or
use the command below to explicitly mention the current value of
all non-default settings:
tailscale up --advertise-exit-node --advertise-routes=192.168.1.0/24 --accept-dns=false
Looks like some old flag is still holding you down. I think you need to run that (I)ssue --reset command to see if you can't clear that first. Either that, or accept item #6, let it go through the motions of adding it, and then remove item #6.The downgrade instructions from @jksmurf worked (as expected).
This time I did get an error message in TAILMON when upgrading from 1.66.4 to 1.68.0:
Code:Messages: Executing: tailscale up --advertise-exit-node --advertise-routes=192.168.1.0/24 Error: changing settings via 'tailscale up' requires mentioning all non-default flags. To proceed, either re-run your command with --reset or use the command below to explicitly mention the current value of all non-default settings: tailscale up --advertise-exit-node --advertise-routes=192.168.1.0/24 --accept-dns=false
Great! the instructions can be a placeholder for others.The downgrade instructions from @jksmurf worked (as expected).
This time I did get an error message in TAILMON when upgrading from 1.66.4 to 1.68.0:
Code:Messages: Executing: tailscale up --advertise-exit-node --advertise-routes=192.168.1.0/24 Error: changing settings via 'tailscale up' requires mentioning all non-default flags. To proceed, either re-run your command with --reset or use the command below to explicitly mention the current value of all non-default settings: tailscale up --advertise-exit-node --advertise-routes=192.168.1.0/24 --accept-dns=false
Unfortunately that did not help; I got the same error when updating from 1.68.0 to 1.68.1.However, I don't see it in my current custom values in TAILMON, so I'm going to add it there.
So let me try to duplicate this...Unfortunately that did not help; I got the same error when updating from 1.68.0 to 1.68.1.
Additionally/however, that extra parameter is now gone (again?) from the TAILMON custom parameters...
That’s odd. I swear @Viktor Jaep recently fixed the custom commands not being saved, maybe there’s a rabbit hole where is gets missed. I’m sure he’ll find it if there’s an issue.Additionally/however, that extra parameter is now gone (again?) from the TAILMON custom parameters...
Ah yes, I recall now, you are in the situation where you can’t ignore the overwrite (as suggested earlier in this thread) and you have to use the —accept-dns=false workaround for your use case.I explicitly set accept-dns to false to prevent conflicts with NextDNS:
It's fixed in 1.0.17b1. I believe he's running .14That’s odd. I swear @Viktor Jaep recently fixed the custom commands not being saved, maybe there’s a rabbit hole where is gets missed. I’m sure he’ll find it if there’s an issue.
# Health check:
# - not logged in, last login error=fetch control key: Get "https://controlplane.tailscale.com/key?v=97": context canceled
# Health check:
# - not in map poll
unexpected state: NoState
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!