TAILMON TAILMON v1.2.0 -Aug 11, 2025- WireGuard-based Tailscale Installer, Configurator and Monitor (Now available in AMTM!)

[Viktor Jaep]

Yeah, but considering the auto update downgrading I thought sticking to the beta path could be worth mentioning.

I'm still not sure how it can auto downgrade... here's the steps it takes:

1. It checks the local version: tailscale version
2. It checks the upstream version: echo $(tailscale version --upstream | grep "upstream" | cut -d ':' -f 2)
3. If they don't equal each other, it runs: tailscale update -yes

I would assume that if you're on stable it will update to the next stable version, and if you're on the beta, it goes to the next beta.

What are you seeing when you run these commands individually vs. what you would get if you ran tailmon -autoupdate?

 

[swejuggalo]

I'm still not sure how it can auto downgrade... here's the steps it takes:

1. It checks the local version: tailscale version
2. It checks the upstream version: echo $(tailscale version --upstream | grep "upstream" | cut -d ':' -f 2)
3. If they don't equal each other, it runs: tailscale update -yes
v
I would assume that if you're on stable it will update to the next stable version, and if you're on the beta, it goes to the next beta.

What are you seeing when you run these commands individually vs. what you would get if you ran tailmon -autoupdate?

ailscale version
1.87.33
track: unstable (dev); frequent updates and bugs are likely
tailscale commit: 908f20e0a506f9fe0c3f6479bc6b7c017cab27a1
long version: 1.87.33-t908f20e0a-g8c7df8d92
other commit: 8c7df8d92929db24d210a6e658d1394e568e6e05
go version: go1.24.4

echo $(tailscale version --upstream | grep "upstream" | cut -d ':' -f

I get stuck there. No response.

tailscale update -yes
Updating Tailscale from 1.87.33 to 1.87.40; --yes given, continuing without prompts.
Downloading "https://pkgs.tailscale.com/unstable/tailscale_1.87.40_arm64.tgz"
Download size: 33098076
Downloaded 512/33098076 (0.0%)
Downloaded 33098076/33098076 (100.0%)
Downloading "https://pkgs.tailscale.com/unstable/tailscale_1.87.40_arm64.tgz.sig"
Signature OK
Extracting "/root/.cache/tailscale-update/tailscale_1.87.40_arm64.tgz"
Updated /tmp/mnt/disk/entware/bin/tailscale
Updated /tmp/mnt/disk/entware/bin/tailscaled
Tailscale binaries updated successfully.
Please restart tailscaled to finish the update.

Just to be clear, I haven't actually seen it downgrade. Purely based on a comment someone else wrote. BUT, it was Tailscale that got downgraded, not the script, right?
If it's just a problem for the script that is one thing, and Tailscale a other. But, however, I have re-enabled auto update of Tailscale now. Lets see how it goes.

 

[rung]

That may have been my words and I was referring to the script. The beta had an auto update function that worked so well that it updated to the non beta version that didn't have the autoupdate capability anymore lol.

 

[swejuggalo]

That may have been my words and I was referring to the script. The beta had an auto update function that worked so well that it updated to the non beta version that didn't have the autoupdate capability anymore lol.

So a misunderstanding then

 

[Viktor Jaep]

ailscale version
1.87.33
track: unstable (dev); frequent updates and bugs are likely
tailscale commit: 908f20e0a506f9fe0c3f6479bc6b7c017cab27a1
long version: 1.87.33-t908f20e0a-g8c7df8d92
other commit: 8c7df8d92929db24d210a6e658d1394e568e6e05
go version: go1.24.4

Looks normal

echo $(tailscale version --upstream | grep "upstream" | cut -d ':' -f

I get stuck there. No response.

Looks like you forgot the closing ) parenthesis

tailscale update -yes
Updating Tailscale from 1.87.33 to 1.87.40; --yes given, continuing without prompts.
Downloading "https://pkgs.tailscale.com/unstable/tailscale_1.87.40_arm64.tgz"
Download size: 33098076
Downloaded 512/33098076 (0.0%)
Downloaded 33098076/33098076 (100.0%)
Downloading "https://pkgs.tailscale.com/unstable/tailscale_1.87.40_arm64.tgz.sig"
Signature OK
Extracting "/root/.cache/tailscale-update/tailscale_1.87.40_arm64.tgz"
Updated /tmp/mnt/disk/entware/bin/tailscale
Updated /tmp/mnt/disk/entware/bin/tailscaled
Tailscale binaries updated successfully.
Please restart tailscaled to finish the update.

Looks normal

Just to be clear, I haven't actually seen it downgrade. Purely based on a comment someone else wrote. BUT, it was Tailscale that got downgraded, not the script, right?
If it's just a problem for the script that is one thing, and Tailscale a other. But, however, I have re-enabled auto update of Tailscale now. Lets see how it goes.

Gotcha. Yes, if you have autoupdate enabled for the script, it will basically downgrade it by updating to the latest stable version. You want to turn the autoupdate feature off for scripts only under the AMTM Email settings in the configuration, so that it only will autoupdate Tailscale.

That may have been my words and I was referring to the script. The beta had an auto update function that worked so well that it updated to the non beta version that didn't have the autoupdate capability anymore lol.

That's exactly it.

 

[Viktor Jaep]

I'll probably add something that provides a separate autoupdate track for those on stable, and those on beta... so that a beta of TAILMON will autoupdate to the next available beta. Thanks for the suggestions!

 

[swejuggalo]

# Health check:
# - This is an unstable version of Tailscale meant for testing and development purposes. Please report any issues to Tailscale.
# - Tailscale failed to fetch the DNS configuration of your device: getting OS base config is not supported
# - getting OS base config is not supported
# - Some peers are advertising routes but --accept-routes is false

Is all expected?
DNS?
OS base config?

The main problem, regardless of what I set up in a router, admin console status on router always says routes and exit is advertised. The way a Tailscale runs on a router might be pointless without this on... But still, the options to have it or not have it exists. And when Tailmon says it's off I expect it to be seen as off by the admin console.

If I use a router as exit point it doesn't see my DoT configuration. But if I use my Home Assistant as exit it does. Probably expected and totally unrelated to Tailmon though.

 

[Viktor Jaep]

# Health check:
# - This is an unstable version of Tailscale meant for testing and development purposes. Please report any issues to Tailscale.
# - Tailscale failed to fetch the DNS configuration of your device: getting OS base config is not supported
# - getting OS base config is not supported
# - Some peers are advertising routes but --accept-routes is false

Is all expected?
DNS?
OS base config?

I get the same messages. You can eliminate that last item by enabling item #6 "Enable site-to-site functionality on router" in the TAILMON config. That will force the "--accept-routes" flag and merges that into your tailscale command line.

I always figured that Tailscale just isn't running on a compatible enough version of linux to get past those "DNS config" and "OS base config" errors... but I've never seen it cause any major issues. Others may disagree.

The main problem, regardless of what I set up in a router, admin console status on router always says routes and exit is advertised. The way a Tailscale runs on a router might be pointless without this on... But still, the options to have it or not have it exists. And when Tailmon says it's off I expect it to be seen as off by the admin console.

Not quite sure what the communication is between the client running on the router vs. what you see on the web interface. Might again just be compatibility issues we're dealing with here.

If I use a router as exit point it doesn't see my DoT configuration. But if I use my Home Assistant as exit it does. Probably expected and totally unrelated to Tailmon though.

TAILMON is just a fancy script that runs tailscale, and shows some info about what its doing.. it doesn't have any ability to alter the way tailscale physically functions or interacts with the actual router. That's all in tailscale's court along with the command line you're feeding it. In your case, it may come down to needing to go beyond the out-of-box modes that TAILMON provides, and needing to use custom mode with command line switches that may help your particular situation? It would require some research on the capabilities of tailscale and how they can be used to possibly help your issue.

 

[swejuggalo]

It would require some research on the capabilities of tailscale and how they can be used to possibly help your issue.

Yepp. The DoT part would be nice if the script could have as an optional option. If even supported by Tailscale.
There might not be that many configuration option that Tailmon could control that is helpful for routers.

I have barely scratched the surface on what Tailscale has to offer and what it can help me with.
Currently trying to discuss with support why I can end up with a broken Android app, super easy, but impossible to break in similar ways on iPad's.
They mostly talk communication issues... But if everything is is OK on iPad with the same steps it's hard to claim it's only a communication issue when only the OS is different
Have to force kill the app to reconnect. And I can also get in a stage that the GUI say I'm not connected, but the OS says I am.

Anyways, only playing around to see what is happening in various situations.

 

[Viktor Jaep]

Here's another TAILMON beta with a few more features requested, noted below! Enjoy!

What's new??
v1.2.0b4 - (TBA)
- PATCH: Based on a recommendation from @JGrana, the RL (Email Rate Limiting) indicators will no longer show up on the main UI (or in the config display) when AMTM email functionality is turned off.
- PATCH: Expanding further on the separation of scripts/binary updates, if the TAILMON script that is currently running is a beta, you can now update (or autoupdate) to the next available beta. Thanks @swejuggalo!

BETA Download link:

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

Significant Screenshots:
None today!

 

[rung]

Latest beta works great. Updated settings to update script. Entered "tailmon -autoupdate" from the command line and the script said I was at the latest beta and did not move back to stable. Thanks!

 

[jksmurf]

Latest beta works great. Updated settings to update script. Entered "tailmon -autoupdate" from the command line and the script said I was at the latest beta and did not move back to stable. Thanks!

Great work Viktor!

@rung just OOO what are you seeing in the latest Tailscale beta that makes that beta worth updating to (and now maintaining via TM)?

 

[swejuggalo]

Great work Viktor!

@rung just OOO what are you seeing in the latest Tailscale beta that makes that beta worth updating to (and now maintaining via TM)?

Stuff being stable and not breaking every now and then is boring?
Or better me than someone else?
Completely normal reasons if you ask me...

But seriously, if it's not extremely critical, I rather live with a few issues and spend some time reporting the problems I get.

 

[jksmurf]

Stuff being stable and not breaking every now and then is boring?

yeah all good, I am ok with betas on my local system, my remote set 9.5k km’s away, not so much!

Was just curious I guess, as in what am I missing out on, is there a cool all singing all dancing new feature, does this beta finally fix that irksome health warning message e.g, that sort of thing.

 

[swejuggalo]

yeah all good, I am ok with betas on my local system, my remote set 9.5k km’s away, not so much!

Was just curious I guess, as in what am I missing out on, is there a cool all singing all dancing new feature, does this beta finally fix that irksome health warning message e.g, that sort of thing.

Yeah. If it's too much of a risk it's a bad idea. But if some failures don't hurt, why not help out. That is the way I think.

Getting early access to something new or just general improvements is just a perk on the way.

I avoid betas on my server though

 

[rung]

@rung just OOO what are you seeing in the latest Tailscale beta that makes that beta worth updating to (and now maintaining via TM)?

I am on Beta Tailmon but stable Tailscale.

 

[Viktor Jaep]

I think we're ready to rock... TAILMON v1.2.0 -- Enjoy!!

What's new!?
v1.2.0 - (August 11, 2025)
- MINOR: Added the ability to DOWNGRADE your Tailscale version to a previous version (even a Beta if you so wish). This certainly is needed functionality, as the Tailscale installer does not have this capability built-in. This procedure was formalized, based on the step-by-step guidance from @colin Taylor, @rung and @Stephen Harrington.
- MINOR: Implemented an email rate limiter as recently introduced in VPNMON-R3. @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 function creates a more formal rate limit on your emails, configured under the Configuration Menu #4, AMTM Email Notifications, and lets you specify how many emails you can receive per hour. An indicator is visible on the top right hand side of the screen, indicating "RL" (in red) as Rate Limiting being disabled, while "RL:10/h" (in green) showing Rate Limiting enabled, with 10 emails/hr set as the rate limit.
- PATCH: Based on a recommendation from @JGrana, the RL (Rate Limit) indicators will no longer show up on the main UI (or in the config display) when AMTM email functionality is turned off.
- PATCH: Added functionality under the Main Setup & Configuration Menu that allows you to upgrade to the latest Tailscale (B)ETA version. Use at your own risk. You can thank @swejuggalo for this addition!
- PATCH: Decided to remove the email notifications for when Operating Modes switch from userspace, to kernel, to custom. Each time the service resets, it applies the settings for these modes, and would shoot off an annoying email about this.
- PATCH: Going with recommendations from @Stephen Harrington, the ability to split out to check for updates between the script itself and the tailscale binaries has been completed. These options are set within the same "schedule autoupdate" item under the configuration menu.
- PATCH: Expanding further on the separation of scripts/binary updates, if the TAILMON script that is currently running is a beta, you can now update (or autoupdate) to the next available beta. Thanks @swejuggalo!

Download links:

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:

Nothing too significant, other than now showing Rate Limiting on the top right of the screen... most changes are operational configuration menu changes.