Setup Tor on your system

Guides
1

Setup Tor on your system

image

Official website: https://www.torproject.org/

Tor is used to access your Umbrel services and apps from outside your local network, without exposing your device to the internet.

macOS

  1. Open the Terminal app on your Mac and install the Homebrew package manager by running:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
  1. Install Tor by running:
brew update && brew install tor

Linux

  1. Open Terminal and install Tor:
sudo apt-get install tor

Windows

  1. Download Tor Windows Expert Bundle from here.
  2. Unzip the file and extract the Tor folder inside to your system (e.g. to “C:\\”)
  3. Open CMD.exe as administrator, navigate to the Tor folder and run:
tor.exe –-service install

Android

  1. Download Orbot on your phone.

  2. Open Orbot and tap the big onion icon to start the Tor proxy.

    running
    running1080×2340 156 KB

  3. It is also possible to select apps which will automatically use Tor.
    a. Tap the gear icon under Tor-Enabled apps and add apps (here Electrum).
    b. Enable VPN Mode.

    select_app
    select_app1080×2340 309 KB
    running_vpn
    running_vpn1080×2340 163 KB

1 Like
2

Maybe add a step 3 for macOS “3. brew services start tor”

2 Likes
3

how do I know if it is running on my windows 10, everything I can find just deals with the tor browser. is that all I need? this is all that I can get it to do

image
image1366×768 65.7 KB

4

is my problem related to this?

umbrel@umbrel:~$ docker logs bitcoin_tor_1 --tail 50

Feb 01 11:52:39.000 [notice] Catching signal TERM, exiting cleanly.
Feb 01 11:52:40.214 [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.
Feb 01 11:52:40.214 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Feb 01 11:52:40.214 [notice] Read configuration file "/etc/tor/torrc".
Feb 01 11:52:40.215 [warn] You have a ControlPort set to accept connections from a non-local address.  This means that programs not running on your computer can reconfigure your Tor.  That's pretty bad, since the controller protocol isn't encrypted!  Maybe you should just listen on 127.0.0.1 and use a tool like stunnel or ssh to encrypt remote connections to your control port.
Feb 01 11:52:40.215 [warn] CookieAuthFileGroupReadable is set, but will have no effect: you must specify an explicit CookieAuthFile to have it group-readable.
Feb 01 11:52:40.217 [warn] You have a ControlPort set to accept connections from a non-local address.  This means that programs not running on your computer can reconfigure your Tor.  That's pretty bad, since the controller protocol isn't encrypted!  Maybe you should just listen on 127.0.0.1 and use a tool like stunnel or ssh to encrypt remote connections to your control port.
Feb 01 11:52:40.218 [notice] Opening Socks listener on 127.0.0.1:9050
Feb 01 11:52:40.218 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
Feb 01 11:52:40.218 [notice] Opening Control listener on 0.0.0.0:9051
Feb 01 11:52:40.218 [notice] Opened Control listener connection (ready) on 0.0.0.0:9051
Feb 01 11:52:40.000 [notice] Bootstrapped 0% (starting): Starting
Feb 01 11:52:40.000 [notice] Starting with guard context "default"
Feb 01 11:52:40.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Feb 01 11:52:40.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Feb 01 11:52:41.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
Feb 01 11:52:41.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
Feb 01 11:52:41.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Feb 01 11:52:41.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
Feb 01 11:52:41.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
Feb 01 11:52:41.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
Feb 01 11:52:41.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Feb 01 11:52:41.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Feb 01 11:52:41.000 [warn] Received http status code 404 ("Not found") from server 185.230.162.217:443 while fetching "/tor/keys/fp/D586xxxxxxxxFC5C6F93646BE72FA1401C02A8DF2E8B4+EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97".
Feb 01 11:52:42.000 [notice] Bootstrapped 100% (done): Done
Feb 01 11:53:28.000 [notice] Catching signal TERM, exiting cleanly.
Feb 01 11:53:29.031 [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.
Feb 01 11:53:29.031 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Feb 01 11:53:29.031 [notice] Read configuration file "/etc/tor/torrc".
Feb 01 11:53:29.032 [warn] You have a ControlPort set to accept connections from a non-local address.  This means that programs not running on your computer can reconfigure your Tor.  That's pretty bad, since the controller protocol isn't encrypted!  Maybe you should just listen on 127.0.0.1 and use a tool like stunnel or ssh to encrypt remote connections to your control port.
Feb 01 11:53:29.032 [warn] CookieAuthFileGroupReadable is set, but will have no effect: you must specify an explicit CookieAuthFile to have it group-readable.
Feb 01 11:53:29.033 [warn] You specified a public address '0.0.0.0:9050' for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
Feb 01 11:53:29.033 [warn] You have a ControlPort set to accept connections from a non-local address.  This means that programs not running on your computer can reconfigure your Tor.  That's pretty bad, since the controller protocol isn't encrypted!  Maybe you should just listen on 127.0.0.1 and use a tool like stunnel or ssh to encrypt remote connections to your control port.
Feb 01 11:53:29.033 [notice] Opening Socks listener on 0.0.0.0:9050
Feb 01 11:53:29.033 [notice] Opened Socks listener connection (ready) on 0.0.0.0:9050
Feb 01 11:53:29.033 [notice] Opening Control listener on 0.0.0.0:9051
Feb 01 11:53:29.033 [notice] Opened Control listener connection (ready) on 0.0.0.0:9051
Feb 01 11:53:29.000 [notice] Bootstrapped 0% (starting): Starting
Feb 01 11:53:29.000 [notice] Starting with guard context "default"
Feb 01 11:53:29.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Feb 01 11:53:29.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Feb 01 11:53:29.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
Feb 01 11:53:29.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
Feb 01 11:53:29.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Feb 01 11:53:30.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
Feb 01 11:53:30.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
Feb 01 11:53:30.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
Feb 01 11:53:30.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Feb 01 11:53:30.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Feb 01 11:53:30.000 [notice] Bootstrapped 100% (done): Done

umbrel@umbrel:~$ docker exec -it bitcoin_tor_1 tor

Feb 01 11:57:45.078 [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.
Feb 01 11:57:45.078 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Feb 01 11:57:45.078 [notice] Read configuration file "/etc/tor/torrc".
Feb 01 11:57:45.079 [warn] You have a ControlPort set to accept connections from a non-local address.  This means that programs not running on your computer can reconfigure your Tor.  That's pretty bad, since the controller protocol isn't encrypted!  Maybe you should just listen on 127.0.0.1 and use a tool like stunnel or ssh to encrypt remote connections to your control port.
Feb 01 11:57:45.079 [warn] CookieAuthFileGroupReadable is set, but will have no effect: you must specify an explicit CookieAuthFile to have it group-readable.
Feb 01 11:57:45.081 [warn] You specified a public address '0.0.0.0:9050' for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
Feb 01 11:57:45.081 [warn] You have a ControlPort set to accept connections from a non-local address.  This means that programs not running on your computer can reconfigure your Tor.  That's pretty bad, since the controller protocol isn't encrypted!  Maybe you should just listen on 127.0.0.1 and use a tool like stunnel or ssh to encrypt remote connections to your control port.
Feb 01 11:57:45.081 [notice] Opening Socks listener on 0.0.0.0:9050
Feb 01 11:57:45.081 [warn] Could not bind to 0.0.0.0:9050: Address already in use. Is Tor already running?
Feb 01 11:57:45.081 [notice] Opening Control listener on 0.0.0.0:9051
Feb 01 11:57:45.081 [warn] Could not bind to 0.0.0.0:9051: Address already in use. Is Tor already running?
Feb 01 11:57:45.081 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.
Feb 01 11:57:45.081 [err] Reading config failed--see warnings above.