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

[Viktor Jaep]

No the one for diversion/amtm. when you first install it it ask you to select one of 3 sources. Sorry I just realise while answering you that maybe I should ask it somewhere else

This might be best directed in the AMTM thread(s)? You mean the format of your external USB drive and/or creation of the swap file?

 

[Dr.Rom]

Yes I will do sorry. No. I don’t remember exactly when you first run amtm it ask you for the colour theme and then after words maybe it ask you which repository you would want to use (so you could pick which is best according to your location). Or maybe when you install entware? Not sure.

 

[Viktor Jaep]

Yes I will do sorry. No. I don’t remember exactly when you first run amtm it ask you for the colour theme and then after words maybe it ask you which repository you would want to use (so you could pick which is best according to your location). Or maybe when you install entware? Not sure.

Yep, I believe it involves formatting, picking your swap file size and location where it and entware may get placed. Definitely post over in the AMTM thread for the experts on this to chime in there.

 

[rung]

Updated to latest beta and found new option. Enabled and cron job and services-start script were both updated correctly. Now we wait for the next update... lol

Success! Tailmon automatically updated tailscale last night:
"SUCCESS: Tailscale was successfully updated via autoupdate from v1.84.0 to v1.86.0"

Thanks for the handy new feature.

 

[Viktor Jaep]

Success! Tailmon automatically updated tailscale last night:
"SUCCESS: Tailscale was successfully updated via autoupdate from v1.84.0 to v1.86.0"

Thanks for the handy new feature.

Lol! Yeah I woke up to that message as well this morning! Glad it's working as advertised!

 

[XIII]

Did anything change regarding default flags in TAILMON?

I manually updated Tailscale 1.84.0 to 1.86.0 (using TAILMON) and now TAILMON is endlessly looping with this:

Executing: tailscale down

Tailscale was already stopped.
Messages:

 Checking tailscaled...              alive.
 Shutting down tailscaled...              done.

Messages:

 Starting tailscaled...              done.

Messages:

Executing: tailscale up --advertise-exit-node --advertise-routes=192.168.1.0/24 --accept-dns=false

Error: changing settings via 'tailscale up' requires mentioning all
non-default flags. To proceed, either re-run your command with --reset or
use the command below to explicitly mention the current value of
all non-default settings:

    tailscale up --accept-dns=false --advertise-exit-node --advertise-routes=192.168.1.0/24 --accept-routes

Which resulted in 30+ mails about a failing Tailscale service restart...

 

[JGrana]

I had a similar thing occur yesterday. The first restart done by Tailmon was at 8:09 AM

I didn’t notice the restart

I was traveling later in the day and got a call from my security company that the connection to my house was lost. I stopped to check it out - and saw a number of emails from Tailmon starting around 2:40PM (I believe 40+ about every 30-40 seconds or so). I also received a few other emails from cloud services that my house network was down.

Finally around 3:21 PM another email from Tailmon stating

WARNING: Router Has Unexpectedly Restarted​

After that every thing seems stable. Ironic - last night at 2AM Tailmon updates the tailscale binary.

I wonder if there was an issue on the Tailscale network side. I also noticed a number of wan-events beginning around noon.

BTW, @XIII do you use Starlink as your WAN provider?

 

[Viktor Jaep]

Did anything change regarding default flags in TAILMON?

I manually updated Tailscale 1.84.0 to 1.86.0 (using TAILMON) and now TAILMON is endlessly looping with this:

Executing: tailscale down

Tailscale was already stopped.
Messages:

 Checking tailscaled...              alive.
 Shutting down tailscaled...              done.

Messages:

 Starting tailscaled...              done.

Messages:

Executing: tailscale up --advertise-exit-node --advertise-routes=192.168.1.0/24 --accept-dns=false

Error: changing settings via 'tailscale up' requires mentioning all
non-default flags. To proceed, either re-run your command with --reset or
use the command below to explicitly mention the current value of
all non-default settings:

    tailscale up --accept-dns=false --advertise-exit-node --advertise-routes=192.168.1.0/24 --accept-routes

Which resulted in 30+ mails about a failing Tailscale service restart...

Mine updated without incident, all within the span of about 30 seconds. I wonder in your case if tailscale made a change on what needs to be reported on the "tailscale up" commandline? It does seem to show that "--accept-routes" was being expected. Guess I need to dive into their release notes. So yeah, this is one of the downsides of autoupdate. You never know what changes tailscale is going to pull that might affect the operation of your install.

 

[Viktor Jaep]

I had a similar thing occur yesterday. The first restart done by Tailmon was at 8:09 AM

Tailmon doesn't reset the router. Do you mean the tailscale service?

I didn’t notice the restart

I was traveling later in the day and got a call from my security company that the connection to my house was lost. I stopped to check it out - and saw a number of emails from Tailmon starting around 2:40PM (I believe 40+ about every 30-40 seconds or so). I also received a few other emails from cloud services that my house network was down.

What emails duplicated about 40x? Could you please send a few sample of the emails you received, then I might be able to narrow down where this looping was happening, and see if I can shore anything up?

Finally around 3:21 PM another email from Tailmon stating

WARNING: Router Has Unexpectedly Restarted​

After that every thing seems stable. Ironic - last night at 2AM Tailmon update the tailscale binary.

I wonder if there was an issue on the Tailscale network side.

So did this looping happen before Tailmon updated the binary? If that's the case, then yeah, I would agree with you about it probably having some kind of connectivity issue?

On my end, I haven't seen any connectivity issues. And this morning I was greeted with a message that the binary successfully upgraded. I checked my logs, and there was no issue. Everything finished within about 30 seconds before returning to normal operation. This is on both of my routers.

 

[JGrana]

Sorry I wasn’t more clear (early, not enough coffee yet ;-)
Yes, Tailmon was restarting the service - not the router.
It appears something did indeed restart the router around 3:20PM. I looked at the logs as best I could - seems there was lots of wan-restart services, tons of dnsmasq reloading and of course a handful of amas_lib faults.
Here is an example of the email that was repeating:

FAILURE: Tailscale Service Restarted

Date/Time: Jul 24 2025 15:19:06

FAILURE: TAILMON has detected that the Tailscale service was dead and not connected. TAILMON.
has reset the service, and reestablished a connection to your Tailnet. Please investigate if this
behavior continues to persist.

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

2025-Jul-24 Thu 03:19:06 PM PDT

As a side, I need to look into why it’s taking ntp_ready to go true after a reboot. It’s seems to take many minutes. I might have something configured wrong. I run chrony using ntpMerlin and might try adding a line in services start to manually start chronyd since ntpMerlin waits (for some reason) for ntp_ready.

 

[JGrana]

I think I found the culprit at least in my case:

https://downdetector.com/status/starlink/

Starlink had lots of issues globally during the period.

@Viktor Jaep about the only thing to think about is maybe adding a “rate limiter” to Tailmon for restarts on a wobbly wan network.

Edge case at best ;-)

 

[XIII]

BTW, @XIII do you use Starlink as your WAN provider?

No, I don’t.

this is one of the downsides of autoupdate.

Luckily I was doing a manual update (and noticed the issue, after a few minutes…)

 

[Viktor Jaep]

@Viktor Jaep about the only thing to think about is maybe adding a “rate limiter” to Tailmon for restarts on a wobbly wan network.

Edge case at best ;-)

That is definitely something to look into. When you got those 40x emails... were they all like 1 min apart from each other? What was the message exactly in those emails? That will help me narrow down where to implement rate limiting.

Nevermind... I think you included that email in your message above. My bad!

 

[Viktor Jaep]

Did anything change regarding default flags in TAILMON?

I manually updated Tailscale 1.84.0 to 1.86.0 (using TAILMON) and now TAILMON is endlessly looping with this:

Executing: tailscale down

Tailscale was already stopped.
Messages:

 Checking tailscaled...              alive.
 Shutting down tailscaled...              done.

Messages:

 Starting tailscaled...              done.

Messages:

Executing: tailscale up --advertise-exit-node --advertise-routes=192.168.1.0/24 --accept-dns=false

Error: changing settings via 'tailscale up' requires mentioning all
non-default flags. To proceed, either re-run your command with --reset or
use the command below to explicitly mention the current value of
all non-default settings:

    tailscale up --accept-dns=false --advertise-exit-node --advertise-routes=192.168.1.0/24 --accept-routes

Which resulted in 30+ mails about a failing Tailscale service restart...

I found this entry in the 1.86 release notes, but it doesn't make sense to me... doesn't seem like this should have caused what you were seeing.

CHANGED: Warn in tailscale status health and tailscale up if there are nodes advertising routes but --accept-routes=false

Tailscale

View changes to the Tailscale client and service.

tailscale.com

 

[rung]

Any idea of the easiest way to revert to the last version of tailscale? Tailmon reports everything running fine but I can't connect to the router or my clients via the tailscale network anymore.

 

[ColinTaylor]

I found this entry in the 1.86 release notes, but it doesn't make sense to me... doesn't seem like this should have caused what you were seeing.

CHANGED: Warn in tailscale status health and tailscale up if there are nodes advertising routes but --accept-routes=false

Tailscale

View changes to the Tailscale client and service.

tailscale.com

That's a note from 2022 for release v1.34.

 

[ColinTaylor]

Any idea of the easiest way to revert to the last version of tailscale? Tailmon reports everything running fine but I can't connect to the router or my clients via the tailscale network anymore.

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.

 

[Viktor Jaep]

That's a note from 2022 for release v1.34.

Whoops. Guess I didn't scroll back up far enough to see the version it was referring to. I blame not having my morning coffee yet.

 

[Viktor Jaep]

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.

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

tailscale update --version 1.84.0

 

[rung]

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.

Thanks this worked!