Cannot connect via tor until I firstly log via local

Hello!

tor | Jul 10 09:30:03.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $EDEDB8797873D340328B5FEDBD7744A7D1DF151F~CalyxInstitute18 [IeNSpgCom9o3NI3jd7uO8A/tEQB4B6bnfckjLJujnQ8] at 185.220.103.6. Retrying on a new circuit.
tor | Jul 10 09:30:03.000 [notice] Tried for 125 seconds to get a connection to [scrubbed]:8333. Giving up.
tor | Jul 10 09:34:58.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Jul 10 09:38:06.743 [notice] Tor 0.4.5.7 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma N/A, Libzstd N/A and Glibc 2.28 as libc.
tor | Jul 10 09:38:06.744 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at Tor Project | Download
tor | Jul 10 09:38:06.758 [notice] Read configuration file “/etc/tor/torrc”.
tor | Jul 10 09:38:06.786 [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.
tor | Jul 10 09:38:07.021 [notice] You configured a non-loopback address ‘10.21.XX.11:9050’ for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
tor | Jul 10 09:38:07.021 [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.
tor | Jul 10 09:38:07.024 [notice] Opening Socks listener on 10.21.XX.11:9050
tor | Jul 10 09:38:07.024 [notice] Opened Socks listener connection (ready) on 10.21.XX.11:9050
tor | Jul 10 09:38:07.024 [notice] Opening Control listener on 10.21.XX.11:29051
tor | Jul 10 09:38:07.025 [notice] Opened Control listener connection (ready) on 10.21.XX.11:29051
tor | Jul 10 09:38:07.000 [notice] Bootstrapped 0% (starting): Starting
tor | Jul 10 09:38:08.000 [notice] Starting with guard context “default”
tor | Jul 10 09:38:09.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
tor | Jul 10 09:38:09.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
tor | Jul 10 09:38:09.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
tor | Jul 10 09:38:09.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
tor | Jul 10 09:38:09.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor | Jul 10 09:38:09.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor | Jul 10 09:38:09.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor | Jul 10 09:38:10.000 [notice] Bootstrapped 100% (done): Done
tor | Jul 10 09:38:19.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 1000 buildtimes.
tor | Jul 10 09:38:20.000 [notice] Guard windeck ($320DB7BEA72C058BA2EEF098BF1AEFBA29371BE0) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 132/188. Use counts are 91/91. 132 circuits completed, 0 were unusable, 0 collapsed, and 1 timed out. For reference, your timeout cutoff is 60 seconds.
tor | Jul 10 09:38:20.000 [warn] Guard windeck ($320DB7BEA72C058BA2EEF098BF1AEFBA29371BE0) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 132/264. Use counts are 91/91. 132 circuits completed, 0 were unusable, 0 collapsed, and 1 timed out. For reference, your timeout cutoff is 60 seconds.
tor | Jul 10 09:38:20.000 [warn] Guard windeck ($320DB7BEA72C058BA2EEF098BF1AEFBA29371BE0) is failing an extremely large amount of circuits. This could indicate a route manipulation attack, extreme network overload, or a bug. Success counts are 66/236. Use counts are 91/91. 66 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
tor | Jul 10 09:38:35.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 269 buildtimes.
tor | Jul 10 09:38:37.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 213 buildtimes.
tor | Jul 10 09:39:04.000 [notice] New control connection opened from 10.21.21.9.
tor | Jul 10 09:39:10.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $D315FDE4F81387BC07839BCBBBD20719389A7E02~Ganthet [zeAI/stnuGlCuwL+903LnLpj6Tv3rSa62h76lXxaM6o] at 45.153.160.2. Retrying on a new circuit.
tor | Jul 10 09:39:26.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $BDA5CDA556481CCE7DE03D59C51ECBD08D464E1A~ifteam11 [C3QtgxePtJP5bH3bi/Ns0ie7MlwipMu671KmPhzDe6A] at 142.44.246.156. Retrying on a new circuit.
tor | Jul 10 09:39:42.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $721E494B0E06554D8F9A169BDBF17282C07B2588~desync [wWlbnFHcdXExytFdI5cCNXFErLzZS527T8x8k2b5bvA] at 66.230.230.230. Retrying on a new circuit.
tor | Jul 10 09:39:58.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $98F793C7320CE3C15A45353AFCC165747A40366D~F3Netze [sSWyZJ/Ab5YjRO5R7Hh0v3/27BvIn4FXHsHgfMP8s0Q] at 185.220.100.255. Retrying on a new circuit.
tor | Jul 10 09:40:13.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $E8AD8C4FDC3FE152150C005BB2EAA6A0990B74DF~F3Netze [5lbkUyBKLAk+1zunDhv/Z2rGUXouCNh2fTZgQvHAcfs] at 185.220.100.243. Retrying on a new circuit.
tor | Jul 10 09:40:40.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $AF7094B62864DE941DCD88A2F0DBAFECF3997E47~artikel5ev10 [vPOjBBt0RIblDQjOCgxRDBCC+WaVhGGgRI4kvPc58aw] at 185.170.114.25. Retrying on a new circuit.
tor | Jul 10 09:40:40.000 [notice] Tried for 126 seconds to get a connection to [scrubbed]:8333. Giving up.
tor | Jul 10 09:43:41.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Jul 10 09:48:10.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Jul 10 09:54:53.000 [notice] Giving up on marked_for_close conn that’s been flushing for 15s (fd 24, type Socks, state open).
tor | Jul 10 10:26:24.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Jul 10 10:27:32.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Jul 10 10:31:10.000 [notice] Our directory information is no longer up-to-date enough to build circuits: We’re missing descriptors for 1/2 of our primary entry guards (total microdescriptors: 6695/6711). That’s ok. We will try to fetch missing descriptors soon.
tor | Jul 10 10:31:10.000 [notice] I learned some more directory information, but not enough to build a circuit: We’re missing descriptors for 1/2 of our primary entry guards (total microdescriptors: 6695/6711). That’s ok. We will try to fetch missing descriptors soon.

I come here to ask help being recommended from Telegram group @lukechilds childs and @mayank

I have a problem with me umbrel node. I use 2 differents internet conections sometimes, and I have the problem that when I power on my umbrel node, I cannot connect via tor until I firstly connect via local conection (umbrel.local or IP) and I put the password of my node.

Then I can connect via tor from any computer/smartphone via tor.

¿How can I configure the umbrel node to not be necessary to connect firstly by local conection?

I put there the logs (I have hidden some part of the IP with XX) that shows my node using “sudo docker-compose logs tor”.

pd. The onion direction is always the same.

Thanksfuly.

1 Like

@mayank @lukechilds what do you think about this case?