TAILMON TAILMON v1.1.1 -Jul 26, 2025- WireGuard-based Tailscale Installer, Configurator and Monitor (Now available in AMTM!)

[Viktor Jaep]

Thanks this worked!

Just for the record, v1.86.0 seems to work OK for me getting to my router/devices behind my router from remote.

 

[rung]

@rung ... you can also downgrade this way:

tailscale update --version 1.84.0

Unfortunately, this command didn't let you downgrade only upgrade. I successfully used Colin's method.

However, I found the version was not the issue but I did fix it somehow:
1) downgrade by copying the binaries then restarting tailscale in tailmon. Saw a warning about mismatched versions so I restarted twice
2) Found issue still existed
3) Unsuccessfully tried to upgrade in tailmon. An error about some cache directory being readonly
4) Completely shutdown tailmon and then restarted tailmon
5) Upgrade now worked in tailmon with same warning about a mismatch.
6) Can't remember, may have restarted tailscale again here

Now it works again! No idea what was wrong before.

Thanks,
Rung

 

[Viktor Jaep]

Unfortunately, this command didn't let you downgrade only upgrade. I successfully used Colin's method.

However, I found the version was not the issue but I did fix it somehow:
1) downgrade by copying the binaries then restarting tailscale in tailmon. Saw a warning about mismatched versions so I restarted twice
2) Found issue still existed
3) Unsuccessfully tried to upgrade in tailmon. An error about some cache directory being readonly
4) Completely shutdown tailmon and then restarted tailmon
5) Upgrade now worked in tailmon with same warning about a mismatch.
6) Can't remember, may have restarted tailscale again here

Now it works again! No idea what was wrong before.

Thanks,
Rung

Looks like that feature may be broken... but according to the docs, it should be possible:

Glad things are back up and running again!

 

[Viktor Jaep]

Small patch to help with some message rate limitations in the situation of a network outage, as reported by @JGrana. Thank you!

What's new?
v1.1.1 - (July 26, 2025)
- PATCH: Modified a section of code that checks to see if the Tailscale service is dead, and tries to restart the service. @JGrana found that in a case of a network outage, that TAILMON will flood you with messages indicating that it tried restarting the service, only to have it loop until network connectivity is restored. This puts a rate limiter on to only attempt this every 60 seconds. It will also execute a fresh version of the script each time to eliminate any factors around that.

Download Links (or update directly within TAILMON, AMTM or just let it autoupdate itself):

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/TAILMON/master/tailmon.sh" -o "/jffs/scripts/tailmon.sh" && chmod 755 "/jffs/scripts/tailmon.sh"

Significant Screenshots:
None today!

 

[salvo]

I tried Tailscale / Tailmon today, and so far it’s working correctly.

During setup, I was experimenting with CIDR blocks and likely ran into a situation where Tailmon got stuck and began restarting repeatedly. I had mistakenly configured the CIDR as 192.168.1.0/21 instead of the correct 192.168.0.0/21. After restarting Tailmon, it failed to recover and entered a restart loop, without the option to access (C)onfiguration. I had to use the -setup parameter to revert to the correct CIDR (192.168.0.0/21 in my case).

Not a major issue, but just something I observed.

 

[Viktor Jaep]

I tried Tailscale / Tailmon today, and so far it’s working correctly.

During setup, I was experimenting with CIDR blocks and likely ran into a situation where Tailmon got stuck and began restarting repeatedly. I had mistakenly configured the CIDR as 192.168.1.0/21 instead of the correct 192.168.0.0/21. After restarting Tailmon, it failed to recover and entered a restart loop, without the option to access (C)onfiguration. I had to use the -setup parameter to revert to the correct CIDR (192.168.0.0/21 in my case).

Not a major issue, but just something I observed.

View attachment 66950

Thanks for reporting, @salvo... you actually hit that screen that now provides a limiter, and runs every 60 seconds instead of continuously. Configuration errors are easy to make with Tailscale, especially when you start adding custom switches. Glad you were able to get it resolved and back to stable again.

 

[Stephen Harrington]

@Viktor Jaep looks like Tailscale has pulled the 1.86.0 update...

Tailscale Changelog

Tailscale v1.86.0
Update instructions
Note: Tailscale halted the rollout of version 1.86.0
for macOS on July 25, 2025,and for all other platforms
on July 28, 2025, due to multiple regressions.

Resulting in an amusing/confusing tailmon message for me overnight after the daily update check:

SUCCESS: Tailscale was successfully updated via autoupdate from v1.86.0 to v1.84.0

Date/Time: Jul 29 2025 05:10:14

SUCCESS: TAILMON has successfully autoupdated Tailscale to the latest version.

Sent by the "tailmon.sh" script.
From the "AsusRouter" router.

2025-Jul-29 Tue 05:10:14 AM UTC

It wasn't - I rebooted just to be sure and then I'm still on 1.86.0 if I run "tailscale version" manually.

Probably an edge case you hadn't quite foreseen?
I'm thinking I'll get the "upgrade" emails again when it tries again tomorrow morning perhaps?
Plus with the command line downgrade not working...

Not sure if we should all be downgrading to 1.84.0 or not pending them squashing all the "multiple regressions"...

 

[Stephen Harrington]

@Viktor Jaep And just because I've actually been catching up with AMTM add-on emails...

Looks like every time tailmon manages a successful Tailscale binary update (including this morning's supposed downgrade to 1.84.0 - NOT) I also get the following email sent at the same time, even though my setup has always been Custom and has never changed - I probably don't need to be reminded if the "Mode" stays the same, even though the Senior Moments are starting to creep in occasionally!

SUCCESS: Tailscale Operating Mode changed to Custom Mode

Date/Time: Jul 29 2025 05:10:26

SUCCESS: TAILMON has changed Tailscale Operating Mode to Custom mode

Sent by the "tailmon.sh" script.
From the "AsusRouter" router.

2025-Jul-29 Tue 05:10:26 AM UTC

 

[Viktor Jaep]

@Viktor Jaep looks like Tailscale has pulled the 1.86.0 update...

Tailscale Changelog

Tailscale v1.86.0
Update instructions
Note: Tailscale halted the rollout of version 1.86.0
for macOS on July 25, 2025,and for all other platforms
on July 28, 2025, due to multiple regressions.

Resulting in an amusing/confusing tailmon message for me overnight after the daily update check:

SUCCESS: Tailscale was successfully updated via autoupdate from v1.86.0 to v1.84.0

Date/Time: Jul 29 2025 05:10:14

SUCCESS: TAILMON has successfully autoupdated Tailscale to the latest version.

Sent by the "tailmon.sh" script.
From the "AsusRouter" router.

2025-Jul-29 Tue 05:10:14 AM UTC

It wasn't - I rebooted just to be sure and then I'm still on 1.86.0 if I run "tailscale version" manually.

Probably an edge case you hadn't quite foreseen?
I'm thinking I'll get the "upgrade" emails again when it tries again tomorrow morning perhaps?
Plus with the command line downgrade not working...

Not sure if we should all be downgrading to 1.84.0 or not pending them squashing all the "multiple regressions"...

That is indeed a unique edge case I wasn't prepared for. I would have always assumed that the version you're about to download would be newer/higher than the one on your system. As you can see during the autoupdate below, it even complains that no update is needed, but TAILMON is dumb, and proceeds to think that the upgrade was successful afterall. If you want to avoid this, then yeah, you would need to uninstall tailscale, and upgrade to v1.84. Or you can just turn off autoupdate for the time being.

 

[Viktor Jaep]

@Viktor Jaep And just because I've actually been catching up with AMTM add-on emails...

Looks like every time tailmon manages a successful Tailscale binary update (including this morning's supposed downgrade to 1.84.0 - NOT) I also get the following email sent at the same time, even though my setup has always been Custom and has never changed - I probably don't need to be reminded if the "Mode" stays the same, even though the Senior Moments are starting to creep in occasionally!

SUCCESS: Tailscale Operating Mode changed to Custom Mode

Date/Time: Jul 29 2025 05:10:26

SUCCESS: TAILMON has changed Tailscale Operating Mode to Custom mode

Sent by the "tailmon.sh" script.
From the "AsusRouter" router.

2025-Jul-29 Tue 05:10:26 AM UTC

That certainly is an annoyance. I get those too, and am annoyed as well. I'll take care of this!

 

[Stephen Harrington]

If you want to avoid this, then yeah, you would need to uninstall tailscale, and upgrade to v1.84. Or you can just turn off autoupdate for the time being.

Well you know @Viktor Jaep, OCD and all so - managed to downgrade to 1.84.0 manually using my own (probably ham-fisted) variation on the @ColinTaylor instructions ...

Download https://pkgs.tailscale.com/stable/tailscale_1.84.0_arm64.tgz and extract tailscale and tailscaled. Copy them both to /opt/bin. Restart Tailscale.

1. Downloaded https://pkgs.tailscale.com/stable/tailscale_1.84.0_arm64.tgz and extracted the "new" (older) tailscale and tailscaled binaries to a temp location.
2. Deleted old files /opt/bin/tailscale and /opt/bin/tailscaled.
3. Moved the two new files to /opt/bin
4. Made them both executable chmod 755
5. Rebooted router, seems happy.
(I'm sure there are cleverer ways of doing it without rebooting but tailmon was complaining after a tailscale restart from tailmon so I just went Nuclear to save time)

 

[Viktor Jaep]

Well you know @Viktor Jaep, OCD and all so - managed to downgrade to 1.84.0 manually using my own (probably ham-fisted) variation on the @ColinTaylor instructions ...

1. Downloaded https://pkgs.tailscale.com/stable/tailscale_1.84.0_arm64.tgz and extracted the "new" (older) tailscale and tailscaled binaries to a temp location.
2. Deleted old files /opt/bin/tailscale and /opt/bin/tailscaled.
3. Moved the two new files to /opt/bin
4. Made them both executable chmod 755
5. Rebooted router, seems happy.
(I'm sure there are cleverer ways of doing it without rebooting but tailmon was complaining after a tailscale restart from tailmon so I just went Nuclear to save time)

Maybe a good feature to add in the near future would be to build an actual downgrade option into TAILMON, allowing you to specify which version you want it to be running.

 

[swejuggalo]

Since we discuss downgrading possibilities. Any possibility to enable beta path for Tailscale?
Depending on OS your clients have it's basically just a toggle or application away to enable it. Found it everywhere but for Windows so far.