The update was not available yesterday, but it was successful today.
1 Like
Sorry Iām not sure which revision you refer to and what was not available.
For clarity, did you use the āno-tiny switch? because that will always find the latest update.
If you just ran the standard script, then as @admon notes above his binaries are updated once a day so you may have tried with the standard sh line without the switch, sometime before he did the daily update.
I only use n not N and it seems to work (although there may be a default no in any case) but itās a good question, some script writers purposely require the correct case to ensure desired input.
Fixed, thanks for asking! @Revolutrix
2 Likes
I'm using the standard script.
1 Like
I had a couple questions about Updating and Restoring.
IF I wanted to restore would I SSH in and only run:
sh update-tailscale.sh --restore
or would I run the whole script like this:
wget -O update-tailscale.sh https://raw.githubusercontent.com/Admonstrator/glinet-tailscale-updater/main/update-tailscale.sh \ && sh update-tailscale.sh --restore
Next Question:
During the update, it created a backup. Is that a backup of the previous version of TailScale that was installed by the script?
AND
If so, is the backup of the āORIGINALā version that came with the the firmware still available to be restored using the --restore flag?
That depends.
You can run sh update-tailscale.sh --restore if the script is still available on your device. If not, try the full path including the download.
No, it's just a backup of the tailscale config files. You should be able to revert to a previous version and use those configs again.
That's what happens by using --restore. The original version of the firmware is located in /rom - you can't delete it, no matter what you try.
Is there a way to disable the Tailscale SSH on these routers? It gets in the way of the methods I usually connect to them
You can just say "No" while the script asks you about Tailscale SSH.
But it should not affect any of your methods anyway.
When I force-upgrade and say No to āenable Tailscale SSHā, it still does not deactivate. Iād have to rebuild the entire router and never activate it.
And yes having Tailscale SSH activated doesnāt allow me to log in with the preset password, instead rerouting to Tailscaleās webpage-based authentication.
Next time, just ask.
First of all āārestoreā would help and second you could just run ātailscale set --ssh=falseā to disable it.
Normal Tailscale commands donāt seem to work (forgot to mention that earlier), but the restore and re-upgrade through your script did. Thank you!
Ah, forgot about the modified gl_tailscale script. You would need to remove the SSH part there. But I will try to improve this process, thanks for your feedback! 
1 Like
I apologize if this has been discussed before, but Iāve had Glinet routers for a while and have always just sshāed into the router and ran something like ātailscale updateā and never had any issues. Heck, on my X3000, I ran that tailscale set āauto-update and it gets pushed the newest tailscale firmware automatically. Should it not be done this way?
You can do it this way as long as it works.
It might break sometimes - so better keep an eye on it.
Hello, did you already try it on Comet Pro KVM (GL-RM10) ?
Unfortunately, I don't own a RM10 - so I can't test nor adjust the script.
It should not work so far.
Ok. Any info i can share with you from the device that can help ?
Not really. Without testing on the device in vitro, it would be too much effort, tbh.
Ok, i understand. If you change your mind, don't hesitate to ask, I'll be happy to help
1 Like
@admon quick update about tailscale update for the Comet Pro: Comet pro tailscale update . No need to worry about your script, it can be update using tailscale command.