So - confirming.- if I run the script on the Comet, I should ignore the warning messages and it will complete the Tailscale update. I simply need to reboot the Comet after the update is completed and it will be on the current Tailscale version?
@admon, first of all, thank you so much for taking the time to create this script and share it with the community. 
I truly appreciate it.
Iām having issues with using the update script & Iām not sure what went wrong.
I have a Slate AX and I followed the instructions exactly to SSH into the unit. I ran the script and it successfully updated. Didnāt realize at first it required a router reboot. After rebooting, I noticed that there was a yellow/gold banner that appeared (but without any of the usual text) in the Tailscale section. Also, Tailscale doesnāt seem to connect (the status dot stays yellow instead of turning blue). I also get an occasional red banner with a timeout message. Oddly, the Tailscale web dashboard shows that the Slate AX has been successfully updated (showing version 1.82) & that itās connected to my Tailnet but nothing working right on the router - but the router clearly shows that itās not connected.
I went back in via SSH and deployed the script again with the ārestore flag. It successfully rolled back Tailscale to version 1.66 or so. Upon router reboot, Tailscale immediately showed as connected (blue dot), everything seems to be working correctly, and all the yellow and red banners are gone.
Iād still love to update to a newer version as 1.66 is quite old now. Do you know of any reasons why this might have failed? Does anything that I described sound like I did something wrong or missed something out? If you have any suggestions, I would really value hearing them. Thanks so much, once again.
Unfortunately, I can't really help with that. It still seems to be some hardcoded issue inside the UI.
@admon thanks so much for responding. So, are you saying that thereās an issue with the GLinet UI thatās causing the issue and at this point, thereās no resolution (but keeping the lower version of Tailscale)?
Yup, exactly. Seems like that.
It might be worth stating the FW you are using and what mode; presumably router, that youāre running in.
Not really my field but Iād suggest that many users, including myself, have no problem running the script on a regular basis. Iām on 1.82.5 on a Beryl AX MT-3000. So if itās possible to narrow down any setup or mode or settings you have, that might isolate why youāre seeing the problem?
Hello everyone, just updated to the new Tailscale version on Flint 2, i don't know if it can be a problem at some point but everything went smooth with a simple "tailscale update" and a reboot.
On Flint 2 this isn't an issue, but other devices don't have sufficient storage for that.
2 Likes
@admon
Sorry if this is not the correct place to post - but after updating my GL-MT2500 with the latest firmware, all appeared to update fine, and I'm able to access the router (10.0.1.1) however, i seemed to have lost access to a file server on my LAN - I AM able to get a ping response from the device, located at 10.0.1.111 - I've approved the subnet routes, as I have always done... but I can't seem to reach it...
is there any code I can run to verify the firewall settings are correct? my assumption is that something went wrong during the update... but I could be wrong... any ideas how to troubleshoot this?
ps - I should say this is on a remote network, so i don't want to do anything to really mess things up / It's set up as the main router - so if it goes down - so does the whole network over there... at least now the network is ok - I just can't reach the server, if that makes sense...
OK, I ran the this Tailscale update on my Comet about a week ago, upgrading from 1.82.0 (the supported version on the Comet) to 1.84.0 .As @Marcinoo97 stated, I was able to update using the script and once the Comet was restarted, the tailscale version updated. However, today I ran the recent Comet firmware update (1.2.3) and it reset my TS version back to the 1.82.0.
That's normal. Every firmware update will undo the upgrade. You need to run the script again if you chose to not make it permanent.
I think that I set the firmware update to permanent. I will have to observe again if the Comet firmware update undoes the TS update.
I can confirm that the Comet firmware update resets the Tailscale version. My Comet firmware update 1.3.0 reset Tailscale version back 1.82.0 (the currently supported version by GL.iNet).
I ran the script on the Flint 2 router. It worked perfectly. The current version is also displayed in the Tailscale admin console. I've enabled automatic script updates. Thanks, good work.
1 Like
This is what my interface looks like at the moment
you my friend are a hero without cape!
1 Like
Hello! I have been using this script on all of my gl-inet devices. Perhaps I am doing something wrong, but it does not appear to work as expected on my gl-inet Comet...
Could you give me some advice on might be happening?
Will this script work on the new GL-MT6000 Wi-Fi 6 AX6000 Home Router?
I'm looking to upgrade my network - any helpful advice would be appreciated - looking for a more robust, stable, router, that i can continue remote management. TY
MT6000 is Flint 2, which isn't "new". Works perfectly there.
@Baldwin_RL Can't help with that, don't have a Comet right now.
would sending the capture of the error help you on determine what might be causing the error? 