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.0.20 -Jul 27, 2024- WireGuard-based Tailscale Installer, Configurator and Monitor (Now available in AMTM!)

Worked for me! The maintenance mode command worked and tailscale was updated to the latest version automagically. Great job!

Note I did get two "SUCCESS: TAILMON was successfully updated via autoupdate" emails. The first one may have been during initial installation, not sure.
 
Worked for me! The maintenance mode command worked and tailscale was updated to the latest version automagically. Great job!

Note I did get two "SUCCESS: TAILMON was successfully updated via autoupdate" emails. The first one may have been during initial installation, not sure.
Thank you @rung! Let me look into that. I may have accidentally duplicated that message. ;)

EDIT: Could it have been just similar messaging that threw you off, or were they identical? You probably would have seen both of these if it updated both the script and Tailscale:

1 x TAILMON has successfully autoupdated Tailscale to the latest version
1 x TAILMON was successfully updated to the latest version via autoupdate
 
Cron job scheduler has been added to the latest beta... Please let me know if any of the wording in any of the added items is confusing or needs to be changed.

1751823323115.png
 
EDIT: Could it have been just similar messaging that threw you off, or were they identical? You probably would have seen both of these if it updated both the script and Tailscale:
That was it! Sorry about that.
 
Cron job scheduler has been added to the latest beta... Please let me know if any of the wording in any of the added items is confusing or needs to be changed.

View attachment 66531
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
 
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
Really appreciate your incredibly fast feedback, @rung! :)
 
@jksmurf ... I know how eager you are to try this out. ;) Here are some early beta testing instructions... please see how this goes for you.
Thank you @Viktor Jaep, good to your word, as always; and thanks to @rung for testing too, great stuff.
5. Expected behavior seen:
- TAILMON v1.1.1 will get downloaded through the autoupdate function
- Tailscale will get autoupdated to v1.84 through the autoupdate function
- TAILMON will refresh and update itself in your original window the next time its internal counter refreshes itself.

Success and failure emails are configured.

If this looks good from your end, I'll get a CRON job menu item worked in so we can automate the autoupdate check on a daily basis.

I don't use screen so wasn't 100% sure what to stop exactly, so I stopped the TS service and ran through the steps above.
Any odd messages that you see may be as a result of that; but feedback all the same, in case of others doing these out-of-whack installs :-).

I did not initially see item 7 in the menu above but probably not on the "latest latest" beta; restarting it gave me the menu (v1.1.1).

Minor comment for Custom item 7:
  • I would suggest that rather than just state a time there (01:00 in grey), that if it is DISABLED (being the default), that you just print (state) "Disabled".
  • It was not immediately apparent (albeit not green) that 01:00 in grey meant disabled, until you enter the menu.
I received a "FAILURE: Tailscale Service Restarted" email; not 100% sure if that was due to me stopping the service (rather than screen).

Again, thank you Viktor, this is awesome.

k.
 

Attachments

  • 1.jpg
    1.jpg
    35.6 KB · Views: 13
  • 2.jpg
    2.jpg
    63.6 KB · Views: 12
  • 3.jpg
    3.jpg
    70.8 KB · Views: 12
  • 4.jpg
    4.jpg
    101.7 KB · Views: 10
  • 5.jpg
    5.jpg
    38 KB · Views: 11
Last edited:
Thank you @Viktor Jaep, good to your word, as always; and thanks to @rung for testing too, great stuff.


I don't use screen so wasn't 100% sure what to stop exactly, so I stopped the TS service and ran through the steps above.
Any odd messages that you see may be as a result of that; but feedback all the same, in case of others doing these out-of-whack installs :-).

I did not initially see item 7 in the menu above but probably not on the "latest latest" beta; restarting it gave me the menu (v1.1.1).

Minor comment for Custom item 7:
  • I would suggest that rather than just state a time there (01:00 in grey), that if it is DISABLED (being the default), that you just print (state) "Disabled".
  • It was not immediately apparent (albeit not green) that 01:00 in grey meant disabled, until you enter the menu.
I received a "FAILURE: Tailscale Service Restarted" email; not 100% sure if that was due to me stopping the service (rather than screen).

Again, thank you Viktor, this is awesome.

k.
Lookin' good, @jksmurf! Yeah, that's a normal message when you stop the service while the script is still running. It's trying to recover. ;)

Screen is definitely a great little tool... I always had issues where my laptop would lose its SSH connection, so my script(s) would bomb. I wanted something that would survive outages, so Screen was a great solution so that SSH connection would continue running on the router itself. You can then just pop in and out of those sessions to check up on things whenever you please. Ever since that, I've always built in the option to use screen with any of my tools. ;)
 
Ever since that, I've always built in the option to use screen with any of my tools. ;)
Bingo.. oooh … ideas…. how much work would it be to toggle it to run in “screen” mode on access, by default …? :-)
 
Last edited:
Bingo.. oooh … ideas…. how much work would it be to toggle it to run in “screen” mode on access, by default …? :-)
What do you mean with "on access, by default"? Do you mean as soon as you type the command "tailmon"?

By default I've left TAILMON be so you can use it in any way you want. By simply appending "-screen" to it, or "-screen -now" (which bypasses the reminder message), you can active its Screen mode.
 
What do you mean with "on access, by default"? Do you mean as soon as you type the command "tailmon"?

By default I've left TAILMON be so you can use it in any way you want. By simply appending "-screen" to it, or "-screen -now" (which bypasses the reminder message), you can active its Screen mode.
Oh I see!

I’ve only ever run it from the Tailmon menu selections, so the suggestion was simply that when you select TM from amtm it opens it in screen (because you selected that).

But Viktor this was just pie in the sky TIC comment :-), not a request 🙏
 
Oh I see!

I’ve only ever run it from the Tailmon menu selections, so the suggestion was simply that when you select TM from amtm it opens it in screen (because you selected that).

But Viktor this was just pie in the sky TIC comment :-), not a request 🙏
Gotcha. Yeah, I don't use AMTM to run programs typically. I go right to the command line. Perhaps I'll add the command verbiage to those menu items to help see what might be possible!

Also, for command help, you can always try:

Code:
tailmon -help (or -h)
 
Last edited:
Got an update email last night during the cron check - not sure if there really was one. Would it be possible to add the old and new revisions to the email?
 
Got an update email last night during the cron check - not sure if there really was one. Would it be possible to add the old and new revisions to the email?
Yep will do. Also planning on adding an event log item to show that the autoupdate ran.
 
Last edited:
Gotcha. Yeah, I don't use AMTM to run programs typically
No worries Viktor, but yep, I think this is where we differ; I primarily use amtm to launch the menu.
 
Got an update email last night during the cron check - not sure if there really was one. Would it be possible to add the old and new revisions to the email?
@jksmurf @rung ... Please update to the latest beta. Added the versions TAILMON and Tailscale updated from/to in the success emails and the logs. Also, added an event log item showing that the autoupdate ran successfully.

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"

If you want, please go through the testing steps to make sure everything looks good on your end! :)

 
@jksmurf @rung ... Please update to the latest beta. Added the versions TAILMON and Tailscale updated from/to in the success emails and the logs. Also, added an event log item showing that the autoupdate ran successfully.

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"

If you want, please go through the testing steps to make sure everything looks good on your end! :)

@jksmurf @rung ... Please update to the latest beta. Added the versions TAILMON and Tailscale updated from/to in the success emails and the logs. Also, added an event log item showing that the autoupdate ran successfully.

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"

If you want, please go through the testing steps to make sure everything looks good on your end! :)

Awesome. I'm on the road and updated through tailscale so I can't do all the testing. Will see what happens tonight when the cron hits...
 
@jksmurf @rung ... Please update to the latest beta. Added the versions TAILMON and Tailscale updated from/to in the success emails and the logs. Also, added an event log item showing that the autoupdate ran successfully.
Works perfectly, thanks Viktor! Oddly though, this time, did not get an email.
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"
Done. Still shows that odd error on 1st SSH screen but has no adverse effect.
If you want, please go through the testing steps to make sure everything looks good on your end! :)

Followed the steps including that this time I started it with "tailmon -screen -now" :-)

HTH, k.

[EDIT] Quick Q, presumably I have to revert to the master install later? This is the dev branch?
 

Attachments

  • 01.jpg
    01.jpg
    73.4 KB · Views: 7
  • 02.jpg
    02.jpg
    71.3 KB · Views: 6
  • 03.jpg
    03.jpg
    48.8 KB · Views: 6
  • 03a.jpg
    03a.jpg
    23.1 KB · Views: 6
  • 04.jpg
    04.jpg
    48.3 KB · Views: 6
Last edited:

Awesome. I'm on the road and updated through tailscale so I can't do all the testing. Will see what happens tonight when the cron hits...

Results:

Email: "SUCCESS: TAILMON was successfully updated via autoupdate from v1.1.0 to v1.1.1"

Syslog only mentioned that an email was sent but not that an upgrade happened.
 
Done. Still shows that odd error on 1st SSH screen but has no adverse effect.
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?
[EDIT] Quick Q, presumably I have to revert to the master install later? This is the dev branch?
This is the Dev branch. I will get you back on the main ;)
Syslog only mentioned that an email was sent but not that an upgrade happened.
Check the Tailmon logs. I don't write anything to the syslogs. The messaging functionality does somewhat.
 

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