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

[jksmurf]

That is weird. Mine will actually stop and start the service when I encounter that error. Does that error message never resolve and just stays? Like you never see your device list?

Yup pretty much. Although when I exit then return it shows the device list just fine.

This is the Dev branch. I will get you back on the main

Thx

Check the Tailmon logs. I don't write anything to the syslogs. The messaging functionality does somewhat.

k.

 

[Viktor Jaep]

Yup pretty much. Although when I exit then return it shows the device list just fine.

Thanks for letting me know. I'll see if I can trap that bad behavior and force a service reset.

 

[jksmurf]

Thanks for letting me know. I'll see if I can trap that bad behavior and force a service reset.

Thanks Viktor . Let me know if there’s anything I can do or provide to reproduce it and help debug, if I can.

 

[Viktor Jaep]

Thanks Viktor . Let me know if there’s anything I can do or provide to reproduce it and help debug, if I can.

I've made some changes to catch that weird status error you've been seeing, @jksmurf ... please give this version a shot, and see if that helps resolve things? Now, when TAILMON determines that the status is giving an error, it will restart services. Let's see if it recovers after that?

Here's the updated script:

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

 

[jksmurf]

I've made some changes to catch that weird status error you've been seeing, @jksmurf ... please give this version a shot, and see if that helps resolve things? Now, when TAILMON determines that the status is giving an error, it will restart services. Let's see if it recovers after that?

Here's the updated script:

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

Hi Viktor! Thank you

OK so I followed your steps here again, for consistency.

• On step 3 after starting TM (before I get to the second SSH Window for the Update), I see two error messages (see picture 03a attached). The first 'failed to connect to local tailscaled' is the one I saw before; the second (error fetching current status:') I might not have noticed before. No idea about these, maybe a daemon startup timing mismatch or something?
• Also in step 3, AFTER it restarts TS (and says it sent a FAILURE email) it then shows (see 3b, v1.1.0) a running 'alive' TS service.
• After the second SSH window (step 4) is run, it correctly udpates TM v1.1.0 to v1.1.1, then correctly updates TS v1.82 to v1.84, but in the process, gives (the same) 'error fetching current status:' message shown in the scond part of 3a, then restarts TS, which seems to be OK, and says AU was completed successfully.

So again, it all seems to work OK, just gives those 3 errors (2 the same, at different stages of the update).

HTH

k.

 

[Viktor Jaep]

Hi Viktor! Thank you

OK so I followed your steps here again, for consistency.

• On step 3 after starting TM (before I get to the second SSH Window for the Update), I see two error messages (see picture 03a attached). The first 'failed to connect to local tailscaled' is the one I saw before; the second (error fetching current status:') I might not have noticed before. No idea about these, maybe a daemon startup timing mismatch or something?
• Also in step 3, AFTER it restarts TS (and says it sent a FAILURE email) it then shows (see 3b, v1.1.0) a running 'alive' TS service.
• After the second SSH window (step 4) is run, it correctly udpates TM v1.1.0 to v1.1.1, then correctly updates TS v1.82 to v1.84, but in the process, gives (the same) 'error fetching current status:' message shown in the scond part of 3a, then restarts TS, which seems to be OK, and says AU was completed successfully.

So again, it all seems to work OK, just gives those 3 errors (2 the same, at different stages of the update).

HTH

k.

Thanks for validating, @jksmurf! Those errors are normal. They're induced from stopping services and connections, and I'm not suppressing any messages so we can see everything that's happening. It's exactly what I'm seeing as well. I'm going to run this a few more days and will probably issue a release this weekend if things are working good for you from the autoupdate perspective?

 

[jksmurf]

things are working good for you from the autoupdate perspective?

Roger that. Seems all good to go

 

[swejuggalo]

Set this up again, mostly for fun.
Updated it too. Seems to work fine with router as the exit node.
I assume that the need of updating it manually despite just having installed it is due to entware don't have the latest one?

Haven't found any issues on iPad. But the Android client sometimes needs to be force stopped.
But all that is unrelated to the script.

 

[jksmurf]

I assume that the need of updating it manually despite just having installed it is due to entware don't have the latest one?

I’m going to jump in here before Viktor wakes up .

TLDR;
Yes.

Background:
The latest version of Tailscale included in entware, for most of the more modern router architecture_kernel configurations is 1 82.5-1. An example (for my RT-AX88U Pro) is as shown in screenshot 02xxx above. I believe you can check architecture plus kernel using opkg print-architecture. Issuing uname -m will give you (CPU) architecture only. IIRC Tailmon covers, as noted by @ColinTaylor in the testing phase, for practical purposes, three possible Entware repositories, aarch64-k3.10, armv7sf-k3.2 and armv7sf-k2.6.

Exact details of which version vs router arch_kernel is shown in the entware repo at https://bin.entware.net or @lonelycoder mirror of the same, here https://entware.diversion.ch. Tailscale (stable track) is currently on v 1.84.x depending on oS of device.

See Tailscale stable track binaries for the latest version of Tailscale as updated by Tailmon. If you want bleeding edge TS binaries, you will have to install those by yourself by extracting the binaries and copying the files across to the router. It’s definitely possible and I’ve done it on my Asus router and also a GLiNET MT-3000 but you’d have to want a really specific reason to do so.

If you’re on an older armv7sf-k2.6 based device such as the RT-AC68U, the latest version installed on initial install is (now) 1.84.2, see @garycnew repo here https://garycnew.github.io/Entware/armv7sf-k2.6/, which he has very kindly kept updated following maurer no longer doing so.

If you install entware on such a device then per the instructions in amtm you must install entware from the (now) garycnew backports mirror, (previously the maurer one).

As an aside, @Viktor Jaep may need to amend the instructions in the intro post for older devices referring to maurer. I’m not 100% sure what it’s now called.

 

[Viktor Jaep]

I’m going to jump in here before Viktor wakes up .

No worries... I put it on snooze! Thanks for providing that great answer.

 

[Viktor Jaep]

As an aside, @Viktor Jaep may need to amend the instructions in the intro post for older devices referring to maurer. I’m not 100% sure what it’s now called.

I'm not very sure either. There seemed to be some discussion going under the AMTM thread about this... I definitely need to sort out what's going on.

 

[jksmurf]

I'm not very sure either. There seemed to be some discussion going under the AMTM thread about this... I definitely need to sort out what's going on.

No biggie, I’m sure @thelonelycoder will let us know in good time.

 

[Viktor Jaep]

No biggie, I’m sure @thelonelycoder will let us know in good time.

Fixed the documentation.

 

[jksmurf]

Fixed the documentation.

 

[Viktor Jaep]

After almost an entire YEAR, a great new feature has been added to TAILMON. Huge thanks to @jksmurf for the suggestion, and to both him and @rung for the awesome testing that went into this release!

What's new?
v1.1.0 - (July 12, 2025)
- MINOR: Thanks to a great suggestion from @jksmurf, autoupdate functionality has been added to TAILMON. Autoupdate can be scheduled via CRON job within the script under the Custom Configuration Menu, item #7. When autoupdate runs, it will check for both TAILMON script updates as well as Tailscale binary updates, and attempt to install them accordingly. While autoupdates are running, the main TAILMON script may enter "Maintenance Mode" as to not interfere or overstep actions that the main script may take to keep Tailscale running. Appropriate on-screen, logging and email messaging has been added to keep you in the loop when either the script or Tailscale binaries are autoupdated.

Download link (Or update directly within TAILMON or AMTM):

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:

Autoupdate functionality can be enabled under the "Custom Configuration Options for TAILMON", allowing you to pick a time when it will check for updates. Enabling this functionality will add a "tailmon -autoupdate" command to your scheduled CRON jobs.

When the autoupdate command runs, it will check for both script and Tailscale binary updates, and install them accordingly without requiring any input. Appropriate log entries and optional emails will get fired off anytime there is something that gets updated.

ENJOY!

DISCLAIMER: The "Autoupdate" feature within the TAILMON script is in no way, shape, or form related to, inspired by, or a secret admirer of the legendary "MerlinAU" autoupdate mechanism. Any copyrights or trademarks owned hereinso by @ExtremeFiretop and/or @Martinski shall thusly not be stepped on or harmed. Any similarities in functionality, purpose, or the sheer magic of things updating themselves are purely coincidental and the result of a rogue developer who probably also rips the 'Do Not Remove' tags off mattresses.

 

[Viktor Jaep]

@jksmurf... to get back onto the main branch, just install the latest version using this link, and you should be good to go! Thanks for your tremendous help!

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

 

[jksmurf]

@jksmurf... to get back onto the main branch, just install the latest version using this link, and you should be good to go! Thanks for your tremendous help!

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

Thank you Viktor , awesome stuff. Just keeps getting better.

 

[frazor77]

Since updating it seems to be regularly restarting the service (and picks up speed) throwing the following:

fatal error: runtime: out of memory

runtime stack:
runtime.throw({0x77bbb8?, 0x28298?})
runtime/panic.go:1101 +0x38 fp=0x7fcc7ac4d0 sp=0x7fcc7ac4a0 pc=0x84808
runtime.sysMapOS(0x4000000000, 0x400000)
runtime/mem_linux.go:168 +0x104 fp=0x7fcc7ac510 sp=0x7fcc7ac4d0 pc=0x28854
runtime.sysMap(0x4000000000, 0x400000, 0xd5af28?)
runtime/mem.go:155 +0x34 fp=0x7fcc7ac530 sp=0x7fcc7ac510 pc=0x282a4
runtime.(*mheap).grow(0xd4ace0, 0x3b038?)
runtime/mheap.go:1547 +0x274 fp=0x7fcc7ac5b0 sp=0x7fcc7ac530 pc=0x3c034
runtime.(*mheap).allocSpan(0xd4ace0, 0x1, 0x0, 0x26)
runtime/mheap.go:1252 +0x164 fp=0x7fcc7ac650 sp=0x7fcc7ac5b0 pc=0x3b544
runtime.(*mheap).alloc.func1()
runtime/mheap.go:970 +0x6c fp=0x7fcc7ac6a0 sp=0x7fcc7ac650 pc=0x3b04c
runtime.(*mheap).alloc(0x7fcc7ac728?, 0x27a40?, 0x0?)
runtime/mheap.go:964 +0x54 fp=0x7fcc7ac6f0 sp=0x7fcc7ac6a0 pc=0x3afb4
runtime.(*mcentral).grow(0x7fcc7ac778?)
runtime/mcentral.go:254 +0x5c fp=0x7fcc7ac730 sp=0x7fcc7ac6f0 pc=0x27d1c
runtime.(*mcentral).cacheSpan(0xd5d5a8)
runtime/mcentral.go:170 +0x4ec fp=0x7fcc7ac7b0 sp=0x7fcc7ac730 pc=0x27b8c
runtime.(*mcache).refill(0x7fa668d108, 0x20?)
runtime/mcache.go:183 +0x1ac fp=0x7fcc7ac800 sp=0x7fcc7ac7b0 pc=0x2704c
runtime.(*mcache).nextFree(0x7fa668d108, 0x26)
runtime/malloc.go:964 +0x84 fp=0x7fcc7ac850 sp=0x7fcc7ac800 pc=0x23554
runtime.mallocgcSmallScanNoHeader(0x120, 0x660500, 0x1)

Eventually it gets stuck in a loop where the service goes down and it tries to bring it up again (KeepAlive is enabled) and I can't stop it manually and have to reboot the router

 

[Viktor Jaep]

Since updating it seems to be regularly restarting the service (and picks up speed) throwing the following:

Eventually it gets stuck in a loop where the service goes down and it tries to bring it up again (KeepAlive is enabled) and I can't stop it manually and have to reboot the router

Can you please share some of your Tailmon logs? Perhaps we can get some more clarity from that to see what's going on?

 

[frazor77]

Not sure this is helpful but...:

1820 Jul 14 2025 18:13:42 RT-AX88U-5B60 TAILMON[15514] - ERROR: Tailscale Status producing errors. Restarting services.
1821 Jul 14 2025 18:13:44 RT-AX88U-5B60 TAILMON[15514] - INFO: Tailscale Connection stopped.
1822 Jul 14 2025 18:13:46 RT-AX88U-5B60 TAILMON[15514] - INFO: Tailscale Service stopped.
1823 Jul 14 2025 18:13:47 RT-AX88U-5B60 TAILMON[15514] - INFO: Tailscale Service started.
1824 Jul 14 2025 18:13:48 RT-AX88U-5B60 TAILMON[15514] - INFO: Tailscale Connection started.
1825 Jul 14 2025 18:13:51 RT-AX88U-5B60 TAILMON[15514] - INFO: Email notification was sent successfully [FAILURE: Tailscale Service Restarted]
1826 Jul 14 2025 18:15:36 RT-AX88U-5B60 TAILMON[53848] - INFO: Tailscale Service stopped.
1827 Jul 14 2025 18:16:00 RT-AX88U-5B60 TAILMON[15514] - ERROR: Tailscale Status producing errors. Restarting services.
1828 Jul 14 2025 18:16:04 RT-AX88U-5B60 TAILMON[15514] - INFO: Tailscale Connection stopped.
1829 Jul 14 2025 18:16:05 RT-AX88U-5B60 TAILMON[15514] - INFO: Tailscale Service stopped.
1830 Jul 14 2025 18:16:06 RT-AX88U-5B60 TAILMON[15514] - INFO: Tailscale Service started.
1831 Jul 14 2025 18:16:06 RT-AX88U-5B60 TAILMON[53848] - ERROR: Tailscale Status producing errors. Restarting services.
1832 Jul 14 2025 18:16:07 RT-AX88U-5B60 TAILMON[15514] - INFO: Tailscale Connection started.
1833 Jul 14 2025 18:16:08 RT-AX88U-5B60 TAILMON[53848] - INFO: Tailscale Connection stopped.
1834 Jul 14 2025 18:16:10 RT-AX88U-5B60 TAILMON[15514] - INFO: Email notification was sent successfully [FAILURE: Tailscale Service Restarted]
1835 Jul 14 2025 18:16:10 RT-AX88U-5B60 TAILMON[53848] - INFO: Tailscale Service stopped.
1836 Jul 14 2025 18:16:11 RT-AX88U-5B60 TAILMON[53848] - INFO: Tailscale Service started.
1837 Jul 14 2025 18:16:13 RT-AX88U-5B60 TAILMON[53848] - INFO: Tailscale Connection started.
1838 Jul 14 2025 18:16:16 RT-AX88U-5B60 TAILMON[53848] - INFO: Email notification was sent successfully [FAILURE: Tailscale Service Restarted]
1839 Jul 14 2025 18:19:00 RT-AX88U-5B60 TAILMON[130495] - ERROR: Tailscale Status producing errors. Restarting services.
1840 Jul 14 2025 18:19:02 RT-AX88U-5B60 TAILMON[130495] - INFO: Tailscale Connection stopped.
1841 Jul 14 2025 18:19:04 RT-AX88U-5B60 TAILMON[130495] - INFO: Tailscale Service stopped.
1842 Jul 14 2025 18:19:05 RT-AX88U-5B60 TAILMON[130495] - INFO: Tailscale Service started.
1843 Jul 14 2025 18:19:06 RT-AX88U-5B60 TAILMON[130495] - INFO: Tailscale Connection started.
1844 Jul 14 2025 18:19:09 RT-AX88U-5B60 TAILMON[130495] - INFO: Email notification was sent successfully [FAILURE: Tailscale Service Restarted]