TAILMON TAILMON v1.3.0 -Aug 24, 2025- WireGuard-based Tailscale Installer, Configurator and Monitor (Available in AMTM!)

[Viktor Jaep]

Something I haven't mentioned is that the whole system is incredibly slow.
E.g.
in amtm, I type "tm"
nothing happens for 30 secs, then the screen goes blank
again, nothing happens for 30 secs, then the TAILMON screen appears

from the config screen, I type '9'
nothing happens for 30 secs, then it says "You are on the latest STABLE version!"

I'm guessing there's a couple of 30 second timeouts in there somewhere.

I'd have to agree with @swejuggalo ... you may want to check that nothing is being blocked on Skynet or Pihole? Definitely sounds like something is timing out. That is definitely not normal. On my end, hitting 'tm' is instantaneous coming from AMTM. Same goes for hitting '9' while within TAILMON.

 

[alan6854321]

you may want to check that nothing is being blocked on Skynet or Pihole?

I don't have skynet installed and I don't see anything getting blocked by pihole.
Actually - I'm not sure requests from the router inself go through pihole
Not sure what else to check.

 

[Viktor Jaep]

I don't have skynet installed and I don't see anything getting blocked by pihole.
Actually - I'm not sure requests from the router inself go through pihole
Not sure what else to check.

Perhaps run htop in another window while you try to start TAILMON? See what top services are consuming resources?

Anything else in syslog? Any other delays getting DNS responses? Any other scripts, tools or machines experiencing these issues?

 

[alan6854321]

Perhaps run htop in another window while you try to start TAILMON? See what top services are consuming resources?

No, nothing obvious in htop.
nothing in syslog and the router works fine apart from this.

But, it's not just Tailmon, just doing 'u' from amtm takes ages for each script installed.
(scMerlin, spdMerlin, YazDHCP, TAILOMN)

(We did go though a similar problem on the amtm thread recently with TheLonelyCoded, but I thought that was fixed somehow).

 

[alan6854321]

That thread was here.....

amtm - amtm 6.1.5 - the Asuswrt-Merlin Terminal Menu, August 06, 2025

amtm 6.1 is now available Adds support for wx WXMON - Localized Weather Monitoring, extended forecasts, including aviation METARs and TAFs! (US/Global!) by @Viktor Jaep. This is Viktor's sixth script that makes it into amtm. Congratulations Mr. Jaep, you are the best! Added option in sc Scripts...

www.snbforums.com

 

[Viktor Jaep]

No, nothing obvious in htop.
nothing in syslog and the router works fine apart from this.

But, it's not just Tailmon, just doing 'u' from amtm takes ages for each script installed.
(scMerlin, spdMerlin, YazDHCP, TAILOMN)

(We did go though a similar problem on the amtm thread recently with TheLonelyCoded, but I thought that was fixed somehow).

Sounds like resolution issues? What happens if you bypass running it from AMTM? Just run "tailmon" from the prompt?

 

[alan6854321]

Sounds like resolution issues? What happens if you bypass running it from AMTM? Just run "tailmon" from the prompt?

Same delays - 30 secs + 30 secs

 

[Viktor Jaep]

Same delays - 30 secs + 30 secs

How long does it take to run this?

curl --retry 3 --connect-timeout 3 --max-time 6 --retry-delay 1 --retry-all-errors --fail "https://raw.githubusercontent.com/ViktorJp/TAILMON/main/version.txt"

 

[alan6854321]

I timed-out three times then failed.

curl --retry 3 --connect-timeout 3 --max-time 6 --retry-delay 1 --retry-all-error
s --fail "https://raw.githubusercontent.com/ViktorJp/TAILMON/main/version.txt"
curl: (6) name lookup timed out
Warning: Problem : timeout. Will retry in 1 seconds. 3 retries left.
curl: (6) name lookup timed out
Warning: Problem : timeout. Will retry in 1 seconds. 2 retries left.
curl: (6) name lookup timed out
Warning: Problem : timeout. Will retry in 1 seconds. 1 retries left.
curl: (6) name lookup timed out

 

[alan6854321]

If I go to https://raw.githubusercontent.com/ViktorJp/TAILMON/main/version.txt from a browser, it returns 1.3.0 straight away.

 

[Viktor Jaep]

I timed-out three times then failed.

curl --retry 3 --connect-timeout 3 --max-time 6 --retry-delay 1 --retry-all-error
s --fail "https://raw.githubusercontent.com/ViktorJp/TAILMON/main/version.txt"
curl: (6) name lookup timed out
Warning: Problem : timeout. Will retry in 1 seconds. 3 retries left.
curl: (6) name lookup timed out
Warning: Problem : timeout. Will retry in 1 seconds. 2 retries left.
curl: (6) name lookup timed out
Warning: Problem : timeout. Will retry in 1 seconds. 1 retries left.
curl: (6) name lookup timed out

If I go to https://raw.githubusercontent.com/ViktorJp/TAILMON/main/version.txt from a browser, it returns 1.3.0 straight away.

For me, it's instantaneous, even from the router end.

So then it sounds like your router is possibly blocking "githubusercontent.com"... which is why it had trouble getting an updated version, and why it takes multiple tries to update TAILMON. Sounds like you have some rabbit holes to dive into on your end!

 

[alan6854321]

Hmm, I can ping it from the router ....

ping raw.githubusercontent.com
PING raw.githubusercontent.com (185.199.111.133): 56 data bytes
64 bytes from 185.199.111.133: seq=0 ttl=57 time=35.557 ms
64 bytes from 185.199.111.133: seq=1 ttl=57 time=27.463 ms
64 bytes from 185.199.111.133: seq=2 ttl=57 time=19.425 ms
64 bytes from 185.199.111.133: seq=3 ttl=57 time=19.265 ms
64 bytes from 185.199.111.133: seq=4 ttl=57 time=75.790 ms
64 bytes from 185.199.111.133: seq=5 ttl=57 time=17.661 ms
64 bytes from 185.199.111.133: seq=6 ttl=57 time=22.074 ms
64 bytes from 185.199.111.133: seq=7 ttl=57 time=23.954 ms
64 bytes from 185.199.111.133: seq=8 ttl=57 time=20.870 ms

 

[alan6854321]

it's intermittent (Oh great!)

I tried curl again and it returned 1.3.0 instantly.
Tried it again and now it's timing out

 

[Viktor Jaep]

it's intermittent (Oh great!)

I tried curl again and it returned 1.3.0 instantly.
Tried it again and now it's timing out

Welcome to the rabbit hole!

Sure it's not Pihole? (No pun intended) Lol

 

[alan6854321]

Does this nslookup out give any clues,
it seems that it's not using PiHole at all but going to OpenDNS

AsusAdmin@RT-AX88U_Pro-0998:/tmp/home/root# nslookup raw.githubusercontent.com
Server:    208.67.222.222
Address 1: 208.67.222.222 dns.sse.cisco.com

Name:      raw.githubusercontent.com
Address 1: 185.199.110.133 cdn-185-199-110-133.github.com
Address 2: 185.199.111.133 cdn-185-199-111-133.github.com
Address 3: 185.199.108.133 cdn-185-199-108-133.github.com
Address 4: 185.199.109.133 cdn-185-199-109-133.github.com
Address 5: 2606:50c0:8000::154
Address 6: 2606:50c0:8001::154
Address 7: 2606:50c0:8002::154
Address 8: 2606:50c0:8003::154

 

[Viktor Jaep]

Does this nslookup out give any clues,
it seems that it's not using PiHole at all but going to OpenDNS

AsusAdmin@RT-AX88U_Pro-0998:/tmp/home/root# nslookup raw.githubusercontent.com
Server:    208.67.222.222
Address 1: 208.67.222.222 dns.sse.cisco.com

Name:      raw.githubusercontent.com
Address 1: 185.199.110.133 cdn-185-199-110-133.github.com
Address 2: 185.199.111.133 cdn-185-199-111-133.github.com
Address 3: 185.199.108.133 cdn-185-199-108-133.github.com
Address 4: 185.199.109.133 cdn-185-199-109-133.github.com
Address 5: 2606:50c0:8000::154
Address 6: 2606:50c0:8001::154
Address 7: 2606:50c0:8002::154
Address 8: 2606:50c0:8003::154

Looks correct from my end.

 

[swejuggalo]

Interesting. Every time I start Tailmon with TM the latest beta of Tailscale the watchdog restarts it, even though it is properly running.

Can anyone confirm?

Interesting, open Tailmon with TM in AMTM is fine on AX88U, but it restarts Tailmon on BE88U. Identically set up.

Update: Ah, scratch that. Whatever that happened, it's fine on BE88U now too.

 

[alan6854321]

Looks correct from my end.

Could it be as simple as a too-short timeout?

In the curl command you asked me to try, I replaced --connect-timeout 3 with --connect-timeout 10 and it works every time.

 

[Viktor Jaep]

Could it be as simple as a too-short timeout?

In the curl command you asked me to try, I replaced --connect-timeout 3 with --connect-timeout 10 and it works every time.

--connect-timeout only governs the time spent setting up the connection. Once the connection is established, this option no longer applies.

In other words, this phase should be almost instantaneous. If your router takes longer than 3 seconds to establish a connection, there is something seriously wrong. ;(