If your Umbrel Bitcoin node still has no Tor peers after updating to umbrelOS 1.7.4, while clearnet and I2P work, the problem is most likely with the Tor service itself or its connection to Bitcoin Core rather than Bitcoin Core networking. Here are the most common fixes: 1. Restart the Tor service and Bitcoin node. From the Umbrel dashboard, restart the Bitcoin Node app. If you have SSH access: sudo systemctl restart umbrel or restart the Tor container if you're using Docker. 2. Check Tor status. SSH into your Umbrel and run: docker ps Make sure the Tor container is running. Then inspect its logs: docker logs tor Look for bootstrap errors or messages like "100% Bootstrapped". 3. Check Bitcoin Core debug.log. Look for messages such as: tor: Authentication failed Proxy connection failed Error connecting to SOCKS5 proxy These point directly to the cause. 4. Verify Tor settings in bitcoin.conf. Typical settings are: onlynet=onion proxy=127.0.0.1:9050 listenonion=1 (Umbrel may manage these automatically, so avoid manual edits unless necessary.) 5. Recreate the Tor hidden service. Sometimes the onion service keys become corrupted after an update. Restarting or reinstalling the Tor service often regenerates them. 6. Check the Umbrel community/GitHub. Around the 1.7.4 release there were reports related to Tor connectivity, and there may be a newer hotfix if the issue persists. A few questions that would help narrow it down: Does the Bitcoin app show 0 Tor peers, or does it say the Tor service is offline? Can you SSH into the Umbrel machine? What hardware are you running Umbrel on (Raspberry Pi, mini PC, etc.)? If you run: bitcoin-cli getnetworkinfo what do the networks section and onion entry show (especially reachable)? That output will usually identify the exact problem within a minute or two.

Guess you're right and it is the tor service.

Umbrel Community

Tor stuck at Bootstrapped 30% (Umbrel 1.7.3)

Tested on two Umbrel instances, version 1.7.3, tor is unusable, stuck at: Bootstrapped 30% (loading_status): Loading networkstatus consensus On o...

Umbrel Community

Tor broken on all Umbrel

The version of tor on Umbrel is old and no longer connects to tor! All the Umbrels are out of the tor network! We are waiting for a quick fix thank...

Thing is, the update to 1.7.4 should have fixed it, at least it seems it did for others, not for me though, I still got no tor connection, same problem as in the first link, stuck at Bootstrap 30%. I was wondering why more than usual lightning-channels were offline for the last couple of days, now I know why. Still no idea what todo about it though, if the update supposed to fix the issue didn't fix it. To your questions: Bitcoin App shows 0 Tor peers, not that it matters anymore. SSH? So far I've only used the Terminal from the dashboard, but I guess I can PuTTY my way in, too. Hardware: ThinkCentre M70q, i5-10500T, 32GB

If I check docker ps, it shows me there's Tor 0.4.9.11 now, LND log confirms it's using 0.4.9.11 >> lightning_tor_1 | Jul 15 10:23:24.931 [notice] Tor 0.4.9.11 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.5.6, Zlib 1.3.1, Liblzma N/A, Libzstd N/A and Glibc 2.41 as libc. but the bitcoin log says it's seeing (and using) Tor 0.4.7.8. >> bitcoin_tor_1 | Jul 15 10:23:24.655 [notice] Tor 0.4.7.8 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.11, Liblzma N/A, Libzstd N/A and Glibc 2.31 as libc. WTF? So, it seems LND is back and working as expected (still some more channels offline than usual, but that might be on them, not me), but Bitcoin still isn't for some reason.

That's actually a very interesting clue. If LND is running Tor 0.4.9.11 while Bitcoin is still reporting Tor 0.4.7.8, then your Bitcoin app is almost certainly still attached to an old Tor container/image. That shouldn't happen after upgrading to 1.7.4. A few things I'd try: 1. Verify the image IDs: docker ps -a docker images | grep tor See whether bitcoin_tor and lightning_tor are actually using different images. 2. Force a recreation of the Bitcoin app containers. From the Umbrel App Store: Stop Bitcoin Node. Uninstall without deleting blockchain data (keep your data). Install it again. This recreates the containers while preserving the chainstate and blocks. 3. If you're comfortable with SSH, remove only the Bitcoin Tor container and let Docker recreate it: docker rm -f bitcoin_tor_1 docker compose up -d (or whatever compose command Umbrel uses for your version). 4. Also check whether the old container is mounting stale Tor data: docker inspect bitcoin_tor_1 and compare it with the LND Tor container. At this point I don't think this is a Bitcoin Core issue anymore—it looks like your Bitcoin app never picked up the new Tor image even though the OS update succeeded. Could you also post the output of: docker images docker ps --format "table {{.Names}}\t{{.Image}}" That should tell us immediately whether Bitcoin is still using an old cached image.