What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

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

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.
 
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.
 
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.
 
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:
Code:
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"
 
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:
Code:
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.
 

Attachments

  • Step02a_CURL_then_Step02b_REM_INST_TS.jpg
    Step02a_CURL_then_Step02b_REM_INST_TS.jpg
    59.2 KB · Views: 13
  • Step03a_START_TM_SN.jpg
    Step03a_START_TM_SN.jpg
    87 KB · Views: 11
  • Step03b_FINAL_STATE.jpg
    Step03b_FINAL_STATE.jpg
    67.2 KB · Views: 11
  • Step04_AU_TM.jpg
    Step04_AU_TM.jpg
    79.3 KB · Views: 10
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?
 
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.
 
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.
 
Last edited:
I’m going to jump in here before Viktor wakes up :-).
No worries... I put it on snooze! Thanks for providing that great answer. ;)
 
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.
 
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):
Code:
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.

1752324863863.png


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.

1752324961214.png


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.
 
Last edited:
@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! :)

Code:
curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/TAILMON/master/tailmon.sh" -o "/jffs/scripts/tailmon.sh" && chmod 755 "/jffs/scripts/tailmon.sh"
 
@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! :)

Code:
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.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top