What does the email say? Perfect case to have email rate limiting turned on.Apparently Tailscale and/or my router went down (I can’t reach them remotely) and now TAILMON is mailing me about that EVERY minute… (so there is still some connectivity)
I read about rate limiting in previous release notes, but I must have read them wrong, because I thought it got enabled in that release (by default)…failure:%20TAILMON%20has%20detected%20that%20the%20Tailscale%20service%20was%20dead%20and%20not%20connected.%20TAILMON.%20has%20reset%20the%20service,%20and%20reestablished%20a%20connection%20to%20your%20Tailnet.%20Please%20investigate%20if%20this%20behavior%20continues%20to%20persist.
Yeah, sorry... It's off by default... shows as a red "RL" on the operations menu.I read about rate limiting in previous release notes, but I must have read them wrong, because I thought it got enabled in that release (by default)…
That’s a bummer. I was going to ask the same as Viktor. WireGuard on the router saved me a couple of times so I could ssh in and fix Tailscale with Viktors’ special C, I issue —reset option.My router is refusing all SSH connections that usually work:
- on iPhone via Tailscale
- on iPhone via OpenVPN
- on a Pi on the local network provided by the router (via Tailscale or OpenVPN)
Shameless plug for knock.sh. If you had a reboot command set up, you could potentially send a reboot command to the router from the local network (eg. from Pi?).My router is refusing all SSH connections that usually work:
- on iPhone via Tailscale
- on iPhone via OpenVPN
- on a Pi on the local network provided by the router (via Tailscale or OpenVPN)
Had the same thought. A break-glass device in case there's no other option.That’s a bummer. I was going to ask the same as Viktor. WireGuard on the router saved me a couple of times so I could ssh in and fix Tailscale with Viktors’ special C, I issue —reset option.
It did start me wondering whether one of those power plug devices you could operate over a phone connection to reboot it (and the ONT) might eventually be a good investment …
View attachment 70496
Hmm not sure that one has a SIM card option though? … not much chop having a phone App if it only works over WiFi … if the router running the WiFi is not working.
Link?Shameless plug for knock.sh.
Yes, here:Link?
(Maybe to prepare for “next time”…)
Just thinking about this though, if the URL can’t get through to the network as nothing is advertising access to it (see XIII list of devices he’s tried to get through on), will it still work ?Shameless plug for knock.sh. If you had a reboot command set up, you could potentially send a reboot command to the router from the local network (eg. from Pi?).
knock v1.2 - router commands for non-admin users
The router could have a ssh issue only. He mentioned access to the local Pi. I would think the router would really have to be in trouble if the firewall logging is down too (what knock.sh is monitoring). Note the email function and tailmon is still working on the router. One would think knock.sh would be too.Just thinking about this though, if the URL can’t get through to the network as nothing is advertising access to it (see XIII list of devices he’s tried to get through on), will it still work ?
I have doubts about that as well, but it would at least be one other thing to try.Just thinking about this though, if the URL can’t get through to the network as nothing is advertising access to it (see XIII list of devices he’s tried to get through on), will it still work ?
Very true. You'd think if there's a SIM involved, there's probably an ongoing cost as well.Hmm not sure that one has a SIM card option though? … not much chop having a phone App if it only works over WiFi … if the router running the WiFi is not working.
The suggestion I posted above is like an independent plug run off a SIM card (ignore the WiFi capability)… you can make like ET and phone home …
Correct. Knock uses firewall logging to execute pre-planned commands like reboot. No ssh needed.I have doubts about that as well, but it would at least be one other thing to try.
All the things I tried have in common that they require SSH to work on the router.
I haven’t looked at knock.sh yet, but that might not depend on that?
I did turn that on and it looks like my router is again not accessible today, so this might be a "good test"...Perfect case to have email rate limiting turned on.![]()
Ah, looks like reading also fails? That makes more sense...It's super annoying that I can no longer SSH into the router when the SSD switches to read only mode
2026-02-28T17:43:19+01:00 router kernel: sd 1:0:0:0: [sdb] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
2026-02-28T17:43:19+01:00 router kernel: sd 1:0:0:0: [sdb] tag#1 Sense Key : Not Ready [current]
2026-02-28T17:43:19+01:00 router kernel: sd 1:0:0:0: [sdb] tag#1 Add. Sense: Logical unit is in process of becoming ready
2026-02-28T17:43:19+01:00 router kernel: sd 1:0:0:0: [sdb] tag#1 CDB: Read(10) <REDACTED>
2026-02-28T17:43:19+01:00 router kernel: print_req_error: I/O error, dev sdb, sector 264310575
2026-02-28T17:43:19+01:00 router kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:995: inode #8259739: lblock 0: comm sysstate: error -5 reading directory block
In many cases, the enclosure matters. Even with the 'bulletproof' enclosure I've got, I've still had the occasional instance where the SSD doesn't come active until I unplug the USB, and plug it back in. The last few times after it spontaneously rebooted, or forced a reboot on its own through MerlinAU to update the FW, it's had no issues thank goodness.Ah, looks like reading also fails? That makes more sense...
Just got my first TAILMON email. Next one should "wait" 1 hour...Code:2026-02-28T17:43:19+01:00 router kernel: sd 1:0:0:0: [sdb] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE 2026-02-28T17:43:19+01:00 router kernel: sd 1:0:0:0: [sdb] tag#1 Sense Key : Not Ready [current] 2026-02-28T17:43:19+01:00 router kernel: sd 1:0:0:0: [sdb] tag#1 Add. Sense: Logical unit is in process of becoming ready 2026-02-28T17:43:19+01:00 router kernel: sd 1:0:0:0: [sdb] tag#1 CDB: Read(10) <REDACTED> 2026-02-28T17:43:19+01:00 router kernel: print_req_error: I/O error, dev sdb, sector 264310575 2026-02-28T17:43:19+01:00 router kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:995: inode #8259739: lblock 0: comm sysstate: error -5 reading directory block
We use essential cookies to make this site work, and optional cookies to enhance your experience.