PSA for Umbrel node runners: if your channels are offline, it's probably not your fault. Tor on umbrelOS is broken.

My node lost all Lightning connectivity recently. All channels offline, watchtowers unreachable, .onion services dead. After some digging it turned out to be nothing local:

UmbrelOS (up to and including the current 1.7.3) ships Tor 0.4.7.8, a version that reached end of life in January 2024. After the Tor network's directory authority changes, this old client can no longer validate the network consensus. Every Tor container on the node is stuck forever at "Bootstrapped 30%" with the error "Consensus not signed by sufficient number of requested authorities".

Why this kills Lightning specifically: Umbrel routes ALL of LND's outbound traffic (onion and clearnet peers) through its Tor SOCKS proxy. Dead proxy = zero peers = all channels offline. Your funds are safe (bitcoind and chain watching still work), but you can't route, send or receive, and your watchtower protection is offline.

Quick check on your node: `sudo docker logs tor_proxy` and look for "Stuck at 30%".

I filed a full analysis with a verified workaround (swapping in a current Tor image) here:

https://github.com/getumbrel/umbrel/issues/2189

The workaround has to be re-applied after every reboot, so the real fix has to come from the Umbrel team via an image update. If you run Umbrel, please check your node and add your confirmation to the issue. The more affected nodes report in, the faster this gets fixed. Some of your "inactive" channel peers may be Umbrel nodes with the same problem right now.