umbrelOS (verified up to 1.7.3 and currentmaster) pinsgetumbrel/tor:0.4.7.8for every Tor daemon it runs. Tor 0.4.7.x reached end-of-life in January 2024, and after the Tor Project's directory-authority changes this client version can no longer validate the network consensus. It gets permanently stuck atBootstrapped 30%.
The impact on an affected node is total loss of Tor connectivity:
- LND has zero peer connectivity — Umbrel routes all LND outbound traffic (onion and clearnet) through the Tor SOCKS proxy at
10.21.21.11:9050, so all channels show offline and watchtower sessions fail.- Bitcoin Core loses onion peers and its
.onionservice.- All app hidden services (
<app>-tor_server-1containers) are dead.- Umbrel's backup-over-Tor fails (
[backup-monitor] Error: Proxy connection timed out).- Remote dashboard access via Tor Browser is dead.
No amount of restarting, reinstalling apps, or updating umbrelOS fixes it, because the same broken image is pinned everywhere (see "Affected components"). Users also cannot patch it persistently themselves, because /opt/umbreld is reset on every boot.Suggested fixSuggested fix
Update the pinned Tor image (all three locations above, plusapp.ts) to a currently supported Tor release (0.4.8.x+ / current stable 0.4.9.x), either by publishing a rebuiltgetumbrel/toror by adopting a maintained upstream image. Given that Tor bootstrap has been broken network-wide for this version, this affects every umbrelOS node running Bitcoin/Lightning or any Tor-dependent app, and silently disables watchtower protection for Lightning nodes.
umbrelOS 1.7.4 is now out which includes the latest Tor version, just login and update to fix the issue.
So trying to understand what this means, is this an issue for all Umbrel nodes? I am having trouble accessing my umbrel node via Zeus, but it sometimes it is a bit temperamental. Not sure if related or not.
Why do you use Tor for connecting to your OWN node? You are not trusting yourself ?
Use LNC with Lightning Terminal or Tailscale or a VPN tunnel over clearnet to connect Zeus and manage your node from a mobile device.
Is really dumb to use Tor just for that.
Man, I didn't know that was an option. Got it working with tailscale, thanks. I always found TOR to be fucking slow to connect.
It's not useful to update to tor 0.4.8.x - update to 0.4.9.x only.
As I said many times before: Is stupid to run LN nodes over Tor, especially PUBLIC ones #944885
If you do not want to reveal your home IP, there are many ways to do it, but not Tor.
Good news : Update is done !
Thanks!
Lived this. Start9, not Umbrel, but same Tor-or-nothing setup — remote access died on me enough times that I ripped it out and put Tailscale in front of everything. Tor-only access is a single point of failure, and this outage just proved it at NETWORK scale. A second path in isn't optional anymore.