I’ve had my umbrel node for about 2 weeks now and it’s never moved passed syncing 0.24%. I’m not sure where to start with trying to fix it so haven’t tried anything specific yet.
You should go into the settings section on the dashboard and click on the troubleshoot section. That will generate logs and copy and paste that into some like pastebin and then post that link here. Without them nobody can really help you.
Sorry, I meant to add it but forgot. Here’s the pastebin
Thanks for sharing your debug-log.
Somehow Tor can’t establish a successful connection. It’s either (1) stuck from the software part or (2) from your ISP.
For the former (1), you could try mitigate with a soft reboot. Did you do a restart via UI > Settings already?
For the latter (2), it’s getting quite complex. Are you living in a country where the ISPs are blocking Tor? Let’s not dive into this yet, trying for test (1) before going about (2).
I’ve tried rebooting in the settings a couple times hoping something as simple as that could fix it but that hasn’t worked.
I’ve used Tor a few times before and never had issues with it being blocked so I’m not sure why it would block it now. On the UI it says its connected to Tor as well
I’m also not sure what could be causing this, but the logs are pointing at Tor not being able to successfully establish a connection to a bridge relay.
I’d wait until someone more knowledgable for Tor chiming in here. What I would do is deleting the Tor docker images and reinstalling it. Given that you barely started, I guess there isn’t much at risk to just start over. You might just consider reflashing your SD card and see if that changes the Tor section of the debug and sync picks up again.
See below where you’d need to keep an eye on whether it improves
Tor logs
--------
Attaching to tor, umbrel_app_tor_1, umbrel_app_2_tor_1, umbrel_app_3_tor_1
app_2_tor_1 | Jan 11 06:05:23.000 [warn] 117 connections died in state handshaking (TLS) with SSL state SSLv3/TLS write client hello in HANDSHAKE
app_2_tor_1 | Jan 11 06:05:23.000 [warn] 5 connections died in state handshaking (TLS) with SSL state error in HANDSHAKE
app_2_tor_1 | Jan 11 10:33:04.000 [notice] Heartbeat: Tor's uptime is 17:59 hours, with 0 circuits open. I've sent 0 kB and received 0 kB. I've received 0 connections on IPv4 and 0 on IPv6. I've made 122 connections with IPv4 and 0 with IPv6.
app_2_tor_1 | Jan 11 16:33:04.000 [notice] Heartbeat: Tor's uptime is 23:59 hours, with 0 circuits open. I've sent 0 kB and received 0 kB. I've received 0 connections on IPv4 and 0 on IPv6. I've made 122 connections with IPv4 and 0 with IPv6.
app_2_tor_1 | Jan 11 17:12:50.000 [warn] Problem bootstrapping. Stuck at 10% (conn_done): Connected to a relay. (CONNECTRESET; CONNECTRESET; count 123; recommendation warn; host 7262B9D2EDE0B6A266C4B43D6202209BF6BBA888 at 78.156.110.135:9092)
app_2_tor_1 | Jan 11 17:12:50.000 [warn] 123 connections have failed:
app_2_tor_1 | Jan 11 17:12:50.000 [warn] 118 connections died in state handshaking (TLS) with SSL state SSLv3/TLS write client hello in HANDSHAKE
app_2_tor_1 | Jan 11 17:12:50.000 [warn] 5 connections died in state handshaking (TLS) with SSL state error in HANDSHAKE
tor | Jan 11 18:05:26.000 [notice] Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.
tor | Jan 11 18:05:26.000 [notice] Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.
tor | Jan 11 18:05:26.000 [notice] Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.
tor | Jan 11 18:05:26.000 [notice] Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.
tor | Jan 11 18:05:27.000 [warn] Problem bootstrapping. Stuck at 10% (conn_done): Connected to a relay. (CONNECTRESET; CONNECTRESET; count 19348; recommendation warn; host 4F0DB7E687FC7C0AE55C8F243DA8B0EB27FBF1F2 at 108.53.208.157:443)
tor | Jan 11 18:05:27.000 [warn] 19348 connections have failed:
tor | Jan 11 18:05:27.000 [warn] 18573 connections died in state handshaking (TLS) with SSL state SSLv3/TLS write client hello in HANDSHAKE
tor | Jan 11 18:05:27.000 [warn] 775 connections died in state handshaking (TLS) with SSL state error in HANDSHAKE
tor | Jan 11 18:05:47.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:8333. Giving up. (waiting for circuit)
tor | Jan 11 18:05:48.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:8333. Giving up. (waiting for circuit)
app_3_tor_1 | Jan 11 14:15:24.000 [warn] Problem bootstrapping. Stuck at 10% (conn_done): Connected to a relay. (wrong version number; TLS_ERROR; count 106; recommendation warn; host BD6A829255CB08E66FBE7D3748363586E46B3810 at 171.25.193.9:80)
app_3_tor_1 | Jan 11 14:15:24.000 [warn] 106 connections have failed:
app_3_tor_1 | Jan 11 14:15:24.000 [warn] 99 connections died in state handshaking (TLS) with SSL state SSLv3/TLS write client hello in HANDSHAKE
app_3_tor_1 | Jan 11 14:15:24.000 [warn] 7 connections died in state handshaking (TLS) with SSL state error in HANDSHAKE
app_3_tor_1 | Jan 11 16:33:04.000 [notice] Heartbeat: Tor's uptime is 23:59 hours, with 0 circuits open. I've sent 0 kB and received 0 kB. I've received 0 connections on IPv4 and 0 on IPv6. I've made 106 connections with IPv4 and 0 with IPv6.
app_3_tor_1 | Jan 11 17:28:42.000 [warn] Problem bootstrapping. Stuck at 10% (conn_done): Connected to a relay. (CONNECTRESET; CONNECTRESET; count 107; recommendation warn; host 24E2F139121D4394C54B5BCC368B3B411857C413 at 204.13.164.118:443)
app_3_tor_1 | Jan 11 17:28:42.000 [warn] 107 connections have failed:
app_3_tor_1 | Jan 11 17:28:42.000 [warn] 100 connections died in state handshaking (TLS) with SSL state SSLv3/TLS write client hello in HANDSHAKE
app_3_tor_1 | Jan 11 17:28:42.000 [warn] 7 connections died in state handshaking (TLS) with SSL state error in HANDSHAKE
app_tor_1 | Jan 11 12:41:46.000 [warn] Problem bootstrapping. Stuck at 10% (conn_done): Connected to a relay. (CONNECTRESET; CONNECTRESET; count 89; recommendation warn; host 74A910646BCEEFBCD2E874FC1DC997430F968145 at 199.58.81.140:443)
app_tor_1 | Jan 11 12:41:46.000 [warn] 89 connections have failed:
app_tor_1 | Jan 11 12:41:46.000 [warn] 85 connections died in state handshaking (TLS) with SSL state SSLv3/TLS write client hello in HANDSHAKE
app_tor_1 | Jan 11 12:41:46.000 [warn] 4 connections died in state handshaking (TLS) with SSL state error in HANDSHAKE
app_tor_1 | Jan 11 16:33:04.000 [notice] Heartbeat: Tor's uptime is 23:59 hours, with 0 circuits open. I've sent 0 kB and received 0 kB. I've received 0 connections on IPv4 and 0 on IPv6. I've made 89 connections with IPv4 and 0 with IPv6.
app_tor_1 | Jan 11 17:40:39.000 [warn] Problem bootstrapping. Stuck at 10% (conn_done): Connected to a relay. (CONNECTRESET; CONNECTRESET; count 90; recommendation warn; host 90A5D1355C4B5840E950EB61E673863A6AE3ACA1 at 54.37.139.118:9001)
app_tor_1 | Jan 11 17:40:39.000 [warn] 90 connections have failed:
app_tor_1 | Jan 11 17:40:39.000 [warn] 86 connections died in state handshaking (TLS) with SSL state SSLv3/TLS write client hello in HANDSHAKE
app_tor_1 | Jan 11 17:40:39.000 [warn] 4 connections died in state handshaking (TLS) with SSL state error in HANDSHAKENot a problem, I’ve reflashed the SD card before and it didn’t fix it so I’m not sure why its constantly an issue. I’ll try again and see how it goes. Thank you for you help
1 Like
Any news? I have the “Problem bootstrapping” too on my recently installed Umbrel over a new Raspberry Pi 4.
I cant find any info about this problem anywhere.
I don’t know TOR well at all, but VPNs are very sensitive to time/timing and will not work if time is out of sync by very much. Your log showing 1/11 makes me wonder if the date being so far out (presuming your post is recent) of sync isn’t part of the issue you are having. Perhaps set the Pi clock somehow and try again?
Just a guess