dperson / torproxy

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

Failed to connect to 0.0.0.0 port 8118: Connection timed out #47

Closed brouillette closed 4 years ago

brouillette commented 4 years ago

Hello!

I'm trying to run this on a Raspberry Pi 4 running Raspbian,

$ lsb_release -a No LSB modules are available. Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster

and I'm getting a 'Connection time out'.

$ docker run -it -p 8118:8118 -d --restart=always --name tor-proxy-1 dperson/torproxy 46083e9757be4db10a2f8c2f1471c221ab343bfe582ff72951ac809015fd5812

$ docker logs tor-proxy-1 May 24 19:58:25.178 [notice] Tor 0.4.1.9 running on Linux with Libevent 2.1.11-stable, OpenSSL 1.1.1g, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A. May 24 19:58:25.178 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning May 24 19:58:25.178 [notice] Read configuration file "/etc/tor/torrc". May 24 19:58:25.187 [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. May 24 19:58:25.188 [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. May 24 19:58:25.188 [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. May 24 19:58:25.188 [notice] Opening Socks listener on 0.0.0.0:9050 May 24 19:58:25.188 [notice] Opened Socks listener on 0.0.0.0:9050 May 24 19:58:25.188 [notice] Opening DNS listener on 127.0.0.1:5353 May 24 19:58:25.188 [notice] Opened DNS listener on 127.0.0.1:5353 May 24 19:58:25.188 [notice] Opening Transparent pf/netfilter listener on 0.0.0.0:9040 May 24 19:58:25.188 [notice] Opened Transparent pf/netfilter listener on 0.0.0.0:9040 May 24 19:58:25.188 [notice] Opening Control listener on 127.0.0.1:9051 May 24 19:58:25.189 [notice] Opened Control listener on 127.0.0.1:9051 May 24 19:58:25.189 [warn] Fixing permissions on directory /var/lib/tor May 24 19:58:25.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip. May 24 19:58:26.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6. May 24 19:58:26.000 [notice] Bootstrapped 0% (starting): Starting May 24 19:58:26.000 [notice] Starting with guard context "default" May 24 19:58:27.000 [notice] Opening Control listener on /etc/tor/run/control May 24 19:58:27.000 [notice] Opened Control listener on /etc/tor/run/control May 24 19:58:27.000 [notice] Bootstrapped 5% (conn): Connecting to a relay May 24 19:58:27.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay May 24 19:58:28.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay May 24 19:58:28.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done May 24 19:58:28.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection May 24 19:58:28.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus May 24 19:58:28.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus May 24 19:58:29.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus. May 24 19:58:29.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs May 24 19:58:30.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services. May 24 19:58:30.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors May 24 19:58:30.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/6016, 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.) May 24 19:58:30.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors May 24 19:58:30.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths. May 24 19:58:32.000 [notice] Bootstrapped 57% (loading_descriptors): Loading relay descriptors May 24 19:58:33.000 [notice] Bootstrapped 62% (loading_descriptors): Loading relay descriptors May 24 19:58:33.000 [notice] Bootstrapped 67% (loading_descriptors): Loading relay descriptors May 24 19:58:33.000 [notice] Bootstrapped 73% (loading_descriptors): Loading relay descriptors May 24 19:58:33.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits May 24 19:58:34.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits May 24 19:58:34.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits May 24 19:58:34.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits May 24 19:58:34.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits May 24 19:58:34.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit May 24 19:58:35.000 [notice] Bootstrapped 100% (done): Done

$ curl --proxy 0.0.0.0:8118 https://check.torproject.org Failed to connect to 0.0.0.0 port 8118: Connection timed out

However, from inside the container itself, it works fine :

$ docker exec -it tor-proxy-1 /bin/bash bash-5.0# curl --proxy 0.0.0.0:8118 https://check.torproject.org

<!doctype html> ... Congratulations. This browser is configured to use Tor. ...

Any ideas? Thanks in advance!

brouillette commented 4 years ago

False alarm!