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.