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.