search

dperson / torproxy

GNU Affero General Public License v3.0
515 stars 144 forks source link

I got stuck at tor bootstraping stage #36

Closed zoonderkins closed 4 years ago

zoonderkins commented 4 years ago

Debian 10 64bit Here is the docker log

Oct 31 10:12:44.686 [notice] Tor 0.3.5.8 running on Linux with Libevent 2.1.10-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A.
Oct 31 10:12:44.686 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Oct 31 10:12:44.686 [notice] Read configuration file "/etc/tor/torrc".
Oct 31 10:12:44.688 [warn] You specified a public address '0.0.0.0:9040' for TransPort. 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.
Oct 31 10:12:44.689 [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.
Oct 31 10:12:44.689 [warn] You specified a public address '0.0.0.0:9040' for TransPort. 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.
Oct 31 10:12:44.689 [notice] Opening Socks listener on 0.0.0.0:9050
Oct 31 10:12:44.689 [notice] Opened Socks listener on 0.0.0.0:9050
Oct 31 10:12:44.689 [notice] Opening DNS listener on 127.0.0.1:5353
Oct 31 10:12:44.689 [notice] Opened DNS listener on 127.0.0.1:5353
Oct 31 10:12:44.689 [notice] Opening Transparent pf/netfilter listener on 0.0.0.0:9040
Oct 31 10:12:44.689 [notice] Opened Transparent pf/netfilter listener on 0.0.0.0:9040
Oct 31 10:12:44.689 [notice] Opening Control listener on 127.0.0.1:9051
Oct 31 10:12:44.689 [notice] Opened Control listener on 127.0.0.1:9051
Oct 31 10:12:44.689 [warn] Fixing permissions on directory /var/lib/tor
Oct 31 10:12:44.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Oct 31 10:12:44.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Oct 31 10:12:44.000 [notice] Bootstrapped 0%: Starting
Oct 31 10:12:44.000 [notice] Starting with guard context "default"
Oct 31 10:12:45.000 [notice] Opening Control listener on /etc/tor/run/control
Oct 31 10:12:45.000 [notice] Opened Control listener on /etc/tor/run/control
Oct 31 10:12:45.000 [notice] Bootstrapped 5%: Connecting to directory server
Oct 31 10:12:47.000 [notice] Bootstrapped 10%: Finishing handshake with directory server
Oct 31 10:12:47.000 [warn] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Host is unreachable; NOROUTE; count 1; recommendation warn; host 587E0A9552E4274B251F29B5B2673D38442EE4BF at 95.130.12.119:443)
Oct 31 10:14:59.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc)
Oct 31 10:15:43.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
dperson commented 4 years ago

Thanks for including the logs, could you also include the command line that you used to launch the container? Thanks.

zoonderkins commented 4 years ago

docker run -it -p 8118:8118 -p 9051:9050 -d dperson/torproxy

dperson commented 4 years ago

Hmm, that shouldn't be happening. Is there any chance that your provider, where you work, your ISP, etc, are blocking tor?

zoonderkins commented 4 years ago

Hmm, now working fine :D, I restart my server

dperson commented 4 years ago

It may have been a SNAFU on the tor host 587E0A9552E4274B251F29B5B2673D38442EE4BF at 95.130.12.119:443 (from your logs) that the container was bootstrapping from, a networking issue, or something on your system.

Regardless, I'm glad it's fixed and that things are working for you once more.

zoonderkins commented 4 years ago

Idk why this still happened once I restart my VPS... I ask my provider, they replied that they do not block and TOR IPs

zoonderkins commented 4 years ago

It took a lot of time to retry... any way to improve?

Nov 07 09:31:40.403 [notice] Tor 0.3.5.8 running on Linux with Libevent 2.1.10-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A.
Nov 07 09:31:40.403 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Nov 07 09:31:40.403 [notice] Read configuration file "/etc/tor/torrc".
Nov 07 09:31:40.406 [warn] You specified a public address '0.0.0.0:9040' for TransPort. 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.
Nov 07 09:31:40.408 [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.
Nov 07 09:31:40.408 [warn] You specified a public address '0.0.0.0:9040' for TransPort. 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.
Nov 07 09:31:40.408 [notice] Opening Socks listener on 0.0.0.0:9050
Nov 07 09:31:40.408 [notice] Opened Socks listener on 0.0.0.0:9050
Nov 07 09:31:40.408 [notice] Opening DNS listener on 127.0.0.1:5353
Nov 07 09:31:40.408 [notice] Opened DNS listener on 127.0.0.1:5353
Nov 07 09:31:40.408 [notice] Opening Transparent pf/netfilter listener on 0.0.0.0:9040
Nov 07 09:31:40.408 [notice] Opened Transparent pf/netfilter listener on 0.0.0.0:9040
Nov 07 09:31:40.408 [notice] Opening Control listener on 127.0.0.1:9051
Nov 07 09:31:40.408 [notice] Opened Control listener on 127.0.0.1:9051
Nov 07 09:31:40.409 [warn] Fixing permissions on directory /var/lib/tor
Nov 07 09:31:40.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Nov 07 09:31:40.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Nov 07 09:31:40.000 [notice] Bootstrapped 0%: Starting
Nov 07 09:31:40.000 [notice] Starting with guard context "default"
Nov 07 09:31:41.000 [notice] Opening Control listener on /etc/tor/run/control
Nov 07 09:31:41.000 [notice] Opened Control listener on /etc/tor/run/control
Nov 07 09:31:41.000 [notice] Bootstrapped 5%: Connecting to directory server
Nov 07 09:31:42.000 [notice] Bootstrapped 10%: Finishing handshake with directory server
Nov 07 09:33:52.000 [notice] Bootstrapped 15%: Establishing an encrypted directory connection
Nov 07 09:33:52.000 [notice] Bootstrapped 20%: Asking for networkstatus consensus
Nov 07 09:33:52.000 [notice] Bootstrapped 25%: Loading networkstatus consensus
Nov 07 09:33:57.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Nov 07 09:33:57.000 [notice] Bootstrapped 40%: Loading authority key certs
Nov 07 09:33:58.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.
Nov 07 09:33:58.000 [notice] Bootstrapped 45%: Asking for relay descriptors for internal paths
Nov 07 09:33:58.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/5929, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
Nov 07 09:34:39.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Nov 07 09:35:54.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Nov 07 09:36:03.000 [notice] Bootstrapped 50%: Loading relay descriptors for internal paths
Nov 07 09:36:04.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.
Nov 07 09:37:09.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Nov 07 09:38:04.000 [notice] Bootstrapped 56%: Loading relay descriptors
Nov 07 09:38:05.000 [notice] Bootstrapped 64%: Loading relay descriptors
Nov 07 09:38:05.000 [notice] Bootstrapped 70%: Loading relay descriptors
Nov 07 09:38:05.000 [notice] Bootstrapped 78%: Loading relay descriptors
Nov 07 09:38:24.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Nov 07 09:39:39.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Nov 07 09:40:54.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Nov 07 09:41:02.000 [warn] Problem bootstrapping. Stuck at 78%: Loading relay descriptors. (DONE; DONE; count 10; recommendation warn; host AEF6C1FBA0FC16F4931638BF065085B974D3E90F at 51.77.251.192:443)
Nov 07 09:41:02.000 [warn] 14 connections have failed:
Nov 07 09:41:02.000 [warn]  12 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN
Nov 07 09:41:02.000 [warn]  2 connections died in state connect()ing with SSL state (No SSL object)
Nov 07 09:41:02.000 [warn] Problem bootstrapping. Stuck at 78%: Loading relay descriptors. (DONE; DONE; count 11; recommendation warn; host 98A1D0BCCC5D45C7E096D7634C8ED3FFBF1908C6 at 185.61.148.80:8443)
Nov 07 09:41:02.000 [warn] 15 connections have failed:
Nov 07 09:41:02.000 [warn]  13 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN
Nov 07 09:41:02.000 [warn]  2 connections died in state connect()ing with SSL state (No SSL object)
Nov 07 09:41:02.000 [warn] Problem bootstrapping. Stuck at 78%: Loading relay descriptors. (DONE; DONE; count 12; recommendation warn; host AE95BDA37A5BB4685FEBB7F06649D6CE949B5316 at 176.31.229.76:9001)
Nov 07 09:41:02.000 [warn] 16 connections have failed:
Nov 07 09:41:02.000 [warn]  14 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN
Nov 07 09:41:02.000 [warn]  2 connections died in state connect()ing with SSL state (No SSL object)
Nov 07 09:41:02.000 [warn] Problem bootstrapping. Stuck at 78%: Loading relay descriptors. (DONE; DONE; count 13; recommendation warn; host 7185B69E3267E71D0E4CBE30209677205DEA5E67 at 144.76.236.14:9001)
Nov 07 09:41:02.000 [warn] 17 connections have failed:
Nov 07 09:41:02.000 [warn]  15 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN
Nov 07 09:41:02.000 [warn]  2 connections died in state connect()ing with SSL state (No SSL object)
Nov 07 09:41:14.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Nov 07 09:41:14.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Nov 07 09:41:15.000 [notice] Bootstrapped 100%: Done
dperson commented 4 years ago

I'm not seeing that behavior personally, and really haven't had any other reports of the container doing this. I think it's network conditions where your host is running. The below support thread for tor has different ideas for getting connected even with such issues (I'm not a tor developer, I just created this container because I wanted it to exist).

https://tor.stackexchange.com/questions/4727/cant-connect-tor-network-failed-to-establish-network