dperson / torproxy Goto Github PK

I use the next script for container creating:

#!/bin/sh
DOCKER="sudo docker"

$DOCKER run -d \
	--restart=always \
	--name tor \
	-p 9050:9050 \
	-e PASSWORD="password" \
	-e LOCATION="DE},{US},{CA},{DE},{GB},{FR},{NL},{AT},{AU},{NO},{MX" \
	dperson/torproxy

Then the container restarts sequentially.
So I learned logs and config and discovered that torrc has many garbage strings in it. See the generated config file in attachment.

torrc.gz

Hello and thanks for putting this together.
I am not sure if this is more of a Tor question or not...
I am able to watch videos that are blocked by my ISP when I use the Tor browser, but when I use this proxy and try to watch through Chrome, the video portion of websites does not load (shows "***.refused to connect").

Any idea what is going on and how I could fix that?

Cheers,
Chris

Is it possible to set this option on the docker-compose.yml? I'm trying to do it like this:

tor:
  image: dperson/torproxy
  volumes:
    - ./torrc:/etc/tor/torrc
  expose:
    - 9050
    - 8118
  entrypoint: torproxy.sh
  command:
    - "--net host -p 8118:8118 -p 9050:9050"

But I can't get the container to run, I keep getting this error: Unknown option: --

Why did you put the control.authcookie in /etc/tor/run? Can it go in /var/run/tor instead?

I'm trying to connect another container to torproxy and it wants to look in /var/run/tor for control.authcookie.

Hello! I have a need to install your product on a kubernetes. How easier can I do this?
Thank you in advance!

Hi, it's nice that there's a script to route all traffic through TOR. Before running such a script, I'm wondering, is there a way to undo it if you want restore your prior settings or default settings?

The latest image is complaining about a misconfiguration of the privoxy listen-address:

Error: Ignoring unrecognized directive '[::]:8118' (41319776U) in line 784 in configuration file (/etc/privoxy/config).

Amending line 784 of /etc/privoxy/config from [::]:8118 to listen-address [::]:8118 fixed it.

Setting bandwidth using either command line argument or env is not working. I tested this via speed test website. It doesn't look like it is limit the data transfer speed.

This is a usage question, so feel free to send me to a forum or something. I couldn't find any for this docker container.

I want to refresh my IP more often. I tried making a docker-compose that looks like this:

version: '3'
services:
  tor:
    image: dperson/torproxy
    restart: unless-stopped
    environment:
      - TOR_MaxCircuitDirtiness=1
      - TOR_NewCircuitPeriod=1
      - TOR_EnforceDistinctSubnets=1
      - LOCATION=US
  app:
    build: .
    restart: unless-stopped
    environment:
      - PORT=3000
    ports:
      - 3000:3000

My app is a simple express service, like this:

// get info about running server
app.get('/info', (req, res) => {
  const { name, version } = pkg
  request({url: 'http://jsonip.com/', proxy: 'http://tor:8118'}, (err, response, body) => {
    if (err) {
      return res.status(500).json(err)
    }
    const { ip } = JSON.parse(body)
    res.json({
      name,
      version,
      ip
    })
  })
})

I get an IP that is different from my own, but it doesn't change between requests very often:

Example:

{
  "name": "data-proxy",
  "version": "1.0.0",
  "ip": "104.223.123.98"
}

Hello,

I just tried torproxy in a docker container as your instructions.

when I pointed a browser to "http://localhost:8118" the message I see is:

Maximum number of open connections reached.

Is this correct?

Is it possible to set this option on the docker-compose.yml? I'm trying to do it like this:

tor:
  image: dperson/torproxy
  volumes:
    - ./torrc:/etc/tor/torrc
  expose:
    - 9050
    - 8118
  entrypoint: torproxy.sh
  command:
    - "--net host -p 8118:8118 -p 9050:9050"

/ # torproxy.sh -n
/usr/bin/torproxy.sh: line 66: warning: command substitution: ignored null byte in input
515 Authentication failed: Wrong length on authentication cookie.
Service already running, please restart container to apply changes

Thanks for your help !

Hi,

I am using dockstarter in raspberry pi 3.

I ve added the below config in dockstarter docker-compose.override.yml

  torproxy:
    image: dperson/torproxy:latest
    container_name: torproxy
    ports:
      - "9050:9050"
      - "8118:8118"
    environment:
      - TORUSER=pi
      - TOR_NewCircuitPeriod=400
      - TZ=${TZ}

I ve tired without TORUSER as well as TORUSER=root as env variables.

The container stops as soon it starts.

command: sudo docker run -it -p 9050:9050 -d dperson/torproxy -p *** -l "NL}, {FR}, {GB}, {CY"

output:

...
Oct 04 16:35:16.000 [notice] Bootstrapped 100%: Done
Oct 04 16:35:17.000 [warn] Socks version 67 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 04 16:35:18.000 [warn] Socks version 71 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 04 16:35:18.000 [warn] Socks version 67 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)

Is there a way to set NewCircuitPeriod when running the container?

Hi, thank you for your image, but it doesn't work on mac. Today I tried 20 images and no one works on mac, so I tried yours on Ubuntu and it works.

Doesn't work means, that command curl -x http://172.17.0.2:8118 http://jsonip.com/ get curl: (7) Failed to connect to 172.17.0.2 port 8118: Operation timed out

I have found that part sed -i 's|\(127.0.0.1\|localhost\):8118|0.0.0.0:8118|' /etc/privoxy/config in Dockerfile is not working out of box.
Have changed it to: sed -i 's|\(127.0.0.1\):8118|0.0.0.0:8118|' /etc/privoxy/config

Hi, the container always exits even if I set to TOR user manually.
I'm using Raspberry Pi.

Thanks!

Is it possible to setup authentication so that not just any joe shmoe can access/use the proxy? what does that look like?

Good day, can you update tor to last stable version 4.1.x
Thank you.

I'm running with the simple docker run -it -p 8118:8118 -p 9050:9050 -d dperson/torproxy command and using it at port 9050 for browser proxy.
But I noticed each time I start it it seems to run the same circuit resulting in the same IP (exit node).

Is there a way to tell it to generate new one?

Thanks

using this config:

torproxy:
image: dperson/torproxy
ports:
- '8128:8118'

produces an error on privoxy:

his is Privoxy 3.0.28 on 4e27f69d9367 (172.26.0.3), port 8118, enabled

Connect failedYour request for http://localhost:8128/ could not be fulfilled, because the connection to localhost (127.0.0.1) could not be established.This is often a temporary failure, so you might just try again.

Hey, I'd try to run up an EC2 with your docker image.

When I did the curl test at my localhost and I got this:

What I'd run:
sudo docker run -it -p 8118:8118 -p 9050:9050 -d dperson/torproxy -l US

Did I make anything wrong?

hello i am in china and i need to change what bridge it uses in the docker , i downloaded your docker and installed it already but i do not know how to configure it to use a different bridge then default. default bridges can not be reached in china, so is there a way to set it to use maybe the obfs4 and built-in bridge. because i am in a censored country.

If I use links between torproxy and another service it will expose env variables of linked service into torproxy container. It is not problem unless compose project name starts with "tor", because then there will be env variables TOR_* and this variables will be copied into /etc/tor/torrc.

Then tor will fail on broken config:

21. 5. 2017 1:35:36May 21 01:35:36.957 [notice] Tor 0.2.9.10 (git-e28303bcf90b842d) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.1.0e and Zlib 1.2.8.
21. 5. 2017 1:35:36May 21 01:35:36.960 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
21. 5. 2017 1:35:36May 21 01:35:36.961 [notice] Read configuration file "/etc/tor/torrc".
21. 5. 2017 1:35:36May 21 01:35:36.974 [warn] Failed to parse/validate config: Unknown option '_DOWNLOADER_DB_1_ENV_GOSU_VERSION'.  Failing.
21. 5. 2017 1:35:36May 21 01:35:36.975 [err] Reading config failed--see warnings above.

Can't connect to the others ports control with nyx when running multiple instences :

podman run -it -p 8118:8118 -p 9050:9050 -p 9051:9051 -d dperson/torproxy -p "test"
podman run -it -p 9150:9150 -p 9151:9151 -v /some/torrc:/etc/tor/torrc:ro -d dperson/torproxy -p "test"

Torrc config of the second instence :

ControlSocket /etc/tor/run/control
ControlSocketsGroupWritable 1
ControlPort 9151
CookieAuthentication 1
CookieAuthFileGroupReadable 1
CookieAuthFile /etc/tor/run/control.authcookie
DataDirectory /var/lib/tor
RunAsDaemon 0
User tor
AutomapHostsOnResolve 1
ExitPolicy reject :
VirtualAddrNetworkIPv4 10.192.0.0/10
DNSPort 5353
SocksPort 0.0.0.0:9150 IsolateDestAddr
TransPort 0.0.0.0:9040

Socks proxy 9050 & 9150 work well

nyx -i 9051 # works
nyx -i 9151 # return --> Unable to authenticate: socket connection failed (Received empty socket content.)

Hi!
I had bad configuration error on start when trying to set some TOR variables like

AccountingMax 100 GB
AccountingStart month 1 00:00

for example, env variable:

TOR_AccountingStart=month 1 00:00

processed incorrectly inside torproxy.sh bash script, becomes in broken torrc file content:

...
AccountingStart "month"
 1
0 "00:00"
...

Hi @dperson

Can you pls tag images which you push to docker hub. Just don't want to use :latest image on my environment.

Thanks!

I do not understand everything inside the startup script, but "TOR_" prefixed environment variables dot not get written to /etc/tor/torrc file.

Problem seems to be coming from this line:

After execution, on TOR_MaxCircuitDirtiness=60, name variable equals "_MaxCircuitDirtiness", which is, I think, not the expected behaviour, as the script then gets to the "continue" command, ignoring this environment variable

When In Node.js using built-in http library and GET with headers

{
	headers: {
		Host: 'api.ipify.org'
	},
	host: '127.0.0.1',
	path: 'https://api.ipify.org/?format=json',
	timeout: 30000,
	method: 'GET',
	port: 8118
}

I get a Error: request timed out, while if using global-tunnel configured as

var globalTunnel = require('global-tunnel-ng');

    globalTunnel.initialize({
        host: 'localhost',
        port: 8118
    });

it works ok.

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!

Hi

Thank you for providing this container. Perfect for my use case.
One thing though. how can i instruct the controller to change IP address?
I know the NEWNYM signal is used for that, but I can't reach the controller.
Tried using Python's stem package, but there I'm already stuck with the authorisation

with Controller.from_port(port=9051) as controller:
controller.authenticate(password='1234')
controller.signal(Signal.NEWNYM)
controller.close()

stem.connection.AuthenticationFailure: socket connection failed (Received empty socket content.)

connecting with telnet 127.0.0.1 9075 also did not succeed.

I tried providing a password like so:

sudo docker run -p 8119:8118 -p 9070:9050 -p 9075:9051 -e PASSWORD=1234 -d dperson/torproxy

but no luck. Any ideas how to get there?

Thank you

When starting the container with the following command:

sudo docker run --restart=always -p 8118:8118 -p 9050:9050 --name upbeat_galileo -e TORUSER=root -d dperson/torproxy -b 150 -l "DE"

after some time (10 minutes - some hours) its docker STATUS turns "unhealty" and starts behaving a little crazy. Sometimes it still works, sometimes it complains like this:

$ curl -Lx http://localhost:8118 https://jsonip.com/
curl: (56) Received HTTP code 503 from proxy after CONNECT

The output of docker logs upbeat_galileo:

Oct 29 20:14:52.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $6CADB707B2E0170B5F13557E42DB7E5C151CC0BC~niftyhutia at 185.220.101.50. Retrying on a new circuit.
Oct 29 20:14:52.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $6CADB707B2E0170B5F13557E42DB7E5C151CC0BC~niftyhutia at 185.220.101.50. Retrying on a new circuit.
Oct 29 20:14:53.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:7779. Giving up.
Oct 29 20:14:53.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:7779. Giving up.
Oct 29 20:14:53.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:7779. Giving up.
Oct 29 20:14:53.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:7779. Giving up.
Oct 29 20:14:53.000 [notice] Tried for 134 seconds to get a connection to [scrubbed]:443. Giving up.
Oct 29 20:14:53.000 [notice] Tried for 130 seconds to get a connection to [scrubbed]:443. Giving up.
Oct 29 20:14:53.000 [notice] Tried for 131 seconds to get a connection to [scrubbed]:443. Giving up.
Oct 29 20:14:53.000 [notice] Tried for 124 seconds to get a connection to [scrubbed]:443. Giving up.
Oct 29 20:14:53.000 [warn] Socks version 71 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 29 20:14:53.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:43. Giving up. (waiting for circuit)
Oct 29 20:14:55.000 [warn] Socks version 80 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 29 20:14:55.000 [warn] Socks version 67 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 29 20:15:01.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:7779. Giving up.
Oct 29 20:15:01.000 [warn] Socks version 71 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 29 20:15:06.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:7779. Giving up.
Oct 29 20:15:09.000 [warn] Socks version 80 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 29 20:15:09.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:7779. Giving up.
Oct 29 20:15:11.000 [warn] Application request to port 110: this port is commonly used for unencrypted protocols. Please make sure you don't send anything you would mind the rest of the Internet reading!
Oct 29 20:15:11.000 [warn] Socks version 80 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 29 20:15:12.000 [warn] Socks version 80 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 29 20:15:12.000 [warn] Socks version 67 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 29 20:15:14.000 [warn] Socks version 67 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 29 20:15:14.000 [warn] Socks version 71 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 29 20:15:14.000 [warn] Socks version 71 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 29 20:15:14.000 [warn] Socks version 67 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 29 20:15:15.000 [warn] Socks version 80 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 29 20:15:16.000 [warn] Socks version 71 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 29 20:15:19.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 172 buildtimes.
Oct 29 20:15:21.000 [warn] Socks version 71 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 29 20:15:21.000 [warn] Socks version 71 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 29 20:15:22.000 [warn] Socks version 67 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 29 20:15:22.000 [warn] Socks version 80 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 29 20:15:23.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:7779. Giving up.
Oct 29 20:15:23.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for socks info)
Oct 29 20:15:23.000 [warn] Socks version 71 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 29 20:15:23.000 [warn] Socks version 71 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 29 20:15:23.000 [warn] Socks version 71 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 29 20:15:24.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:7779. Giving up.
Oct 29 20:15:26.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Oct 29 20:15:26.000 [notice] Tried for 121 seconds to get a connection to [scrubbed]:7779. Giving up.
Oct 29 20:15:26.000 [notice] Tried for 121 seconds to get a connection to [scrubbed]:7779. Giving up.
Oct 29 20:15:26.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for socks info)
Oct 29 20:15:26.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for socks info)
Oct 29 20:15:26.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for socks info)
Oct 29 20:15:27.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:7779. Giving up.
Oct 29 20:15:27.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:7779. Giving up.
Oct 29 20:15:28.000 [warn] Socks version 71 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Oct 29 20:15:29.000 [notice] Tried for 121 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for socks info)

Ports 9050 and 9051 are openend at the firewall.

Any idea/suggestion what might be wrong?

It looks like you've set up a control port in the dockerfile at 9051. It would be great if you could add a hashedpassword environment variable so that we can trigger a new tor circuit through that port using a python command such as:

from stem import Signal
from stem.control import Controller
with Controller.from_port(port = 9051) as controller:
    controller.autenticate()
    controller.signal(Signal.NEWNYM)

I started docker container you provide to setup proxy:

docker run -it -p 8118:8118 -p 9050:9050 -d dperson/proxy

And then run the script tor-route-all-traffic.sh on the host (not container). Problems which I have is

1. DNS resolution doesn't work
2. Even if I disable entries in iptables which route DNS traffic through the proxy, still curl cannot connect to websites via proxy.

Is there some extra tuning needed to the script/docker run command to make it work?

We were built to run on a 64-bit CPU, with OpenSSL 1.0.1 or later, but with a version of OpenSSL that apparently lacks accelerated support for the NIST P-224 and P-256 groups. Building openssl with such support (using the enable-ec_nistp_64_gcc_128 option when configuring it) would make ECDH much faster.

updated to the latest armhf image but it keeps on restarting in an endless loop.
using TORUSER=root doesn't make any difference.
was working fine before update.
Can't rollback cause for the life of me I deleted the old image before the update. I am so smart, right? we live and learn.

Today I found out that the tor proxy was stuck, after running for 3 weeks. It was as simple as restarting the docker container but does this happen normally? Is there a recommended period for auto restarts?

Cant get this running on Unraid. This is what my run commnd looks like:

docker run -d --name="Torproxy" --net="bridge" -e TZ="Europe/London" -e HOST_OS="unRAID" -e "USERID"="99" -e "GROUPID"="100" -e "TORUSER"="root" -p 8118:8118/tcp -p 9050:9050/tcp -p 9051:9051/tcp -it dperson/torproxy

And this is the resulting log:

3:18:08.840 [notice] Tor v0.2.8.9 (git-cabd4ef300c6b3d6) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.2j and Zlib 1.2.8. 3:18:08.840 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning 3:18:08.840 [notice] Read configuration file "/etc/tor/torrc". 3:18:08.849 [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. 3:18:08.851 [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. 3:18:08.851 [notice] Opening Socks listener on 0.0.0.0:9050 3:18:08.851 [notice] Opening DNS listener on 127.0.0.1:5353 3:18:08.851 [notice] Opening Transparent pf/netfilter listener on 127.0.0.1:9040 3:18:08.851 [notice] Opening Control listener on 127.0.0.1:9051 3:18:08.000 [warn] Couldn't open "/etc/tor/run/control.authcookie.tmp" (/etc/tor/run/control.authcookie) for writing: Permission denied 3:18:08.000 [warn] Error writing auth cookie to "/etc/tor/run/control.authcookie". 3:18:08.000 [warn] Error creating control cookie authentication file. 3:18:08.000 [err] set_options(): Bug: Acting on config options left us in a broken state. Dying. (on Tor 0.2.8.9 )

It is stated here that I should be able to use this script to route all traffic through Tor. Where is this script and how would I change the command to start this on container creation?

I've already set --net=host.

I'm using this line to execute the torproxy:

docker run --name tor -it -p 8118:8118 -p 9050:9050 -d -v /var/local/tor/etc:/etc -v /var/local/tor/var/lib/tor:/var/lib/tor -e TORUSER=root dperson/torproxy -b 100

And this is the output from docker logs tor

May 14 01:07:44.342 [notice] Tor 0.3.1.9 (git-727d3f1b5e6eeda7) running on Linux with Libevent 2.1.8-stable, OpenSSL LibreSSL 2.6.3, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A.
May 14 01:07:44.342 [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 14 01:07:44.342 [notice] Read configuration file "/etc/tor/torrc".
May 14 01:07:44.348 [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 14 01:07:44.348 [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 14 01:07:44.349 [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 14 01:07:44.349 [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 14 01:07:44.350 [notice] Opening Socks listener on 0.0.0.0:9050
May 14 01:07:44.350 [notice] Opening DNS listener on 127.0.0.1:5353
May 14 01:07:44.350 [notice] Opening Transparent pf/netfilter listener on 0.0.0.0:9040
May 14 01:07:44.351 [notice] Opening Control listener on 127.0.0.1:9051
May 14 01:07:44.351 [warn] Error setting configured user: tor not found
May 14 01:07:44.351 [warn] Failed to parse/validate config: Problem with User value. See logs for details.
May 14 01:07:44.351 [err] Reading config failed--see warnings above.

Any thoughts?

Do it have one identity (circuit, IP) for a whole time it is started or it switch identity for each request? How to request new identity or handle multiple identities?

Hi, I've tried to start the privoxy. It did not work (tested with curl example).

When tried to run it manually, the following error message appeared:

2017-03-21 10:25:54.982 7f204f467300 Fatal error: can't bind to :::8118: There may be another Privoxy or some other proxy running on port 8118

Of course, this was not true, nothing was running on the port (checked with netstat). This was related to IPV6, simple fix was to delete this line from /etc/privoxy/config and let it use only IPV4.

The netconfig is:

# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
274: eth0: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:ac:11:00:87 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.135/16 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:acff:fe11:87/64 scope link 
       valid_lft forever preferred_lft forever

I'm using debian-jessie (current) with docker.

thanx for fixing

m.

When i start the container i get the warnings

Apr 26 15:57:11.260 [notice] Read configuration file "/etc/tor/torrc".
Apr 26 15:57:11.267 [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.
Apr 26 15:57:11.268 [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.
Apr 26 15:57:11.268 [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.

is that a problem in a local network?
Additionall info:
I dont have any kind of port forwarding enabled in my router.
I use macvlan network to assign the docker container to an ip address in the local network.

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)

A bug was found. When executing the command "tor --hash-password '$ passwd'") ">> $ file the warning is written to torrc

Jun 24 05:56:10.612 [notice] Tor 0.4.3.5 running on Linux with Libevent 2.1.11-stable, OpenSSL 1.1.1g, Zlib 1.2.11, Liblzma 5.2.5, and Libzstd 1.4.5.
Jun 24 05:56:10.612 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Jun 24 05:56:10.612 [warn] Tor was compiled with zstd 1.4.4, but is running with zstd 1.4.5. For safety, we'll avoid using advanced zstd functionality.
Jun 24 05:56:10.612 [notice] Read configuration file "/etc/tor/torrc".
Jun 24 05:56:10.616 [warn] Failed to parse/validate config: Unknown option '16:78A34DBD9752DA0860BB12BFEC701E573471E808149BC4F9A48E635301'. Failing.
Jun 24 05:56:10.616 [err] Reading config failed--see warnings above.
Jun 24 05:56:26.180 [notice] Tor 0.4.3.5 running on Linux with Libevent 2.1.11-stable, OpenSSL 1.1.1g, Zlib 1.2.11, Liblzma 5.2.5, and Libzstd 1.4.5.
Jun 24 05:56:26.180 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Jun 24 05:56:26.180 [warn] Tor was compiled with zstd 1.4.4, but is running with zstd 1.4.5. For safety, we'll avoid using advanced zstd functionality.
Jun 24 05:56:26.180 [notice] Read configuration file "/etc/tor/torrc".
Jun 24 05:56:26.185 [warn] Failed to parse/validate config: Unknown option '16:78A34DBD9752DA0860BB12BFEC701E573471E808149BC4F9A48E635301'. Failing.
Jun 24 05:56:26.185 [err] Reading config failed--see warnings above.
Service exited 'tor sha256:44b9128d05bc5a9cb35fd69237798b30b6d25a05e66be26ecff3a522bb627179'
Killing service 'tor sha256:44b9128d05bc5a9cb35fd69237798b30b6d25a05e66be26ecff3a522bb627179'
Killed service 'tor sha256:44b9128d05bc5a9cb35fd69237798b30b6d25a05e66be26ecff3a522bb627179'

/etc/tor/torrc

ControlSocket /etc/tor/run/control
ControlSocketsGroupWritable 1
ControlPort 0.0.0.0:9051
CookieAuthentication 1
CookieAuthFileGroupReadable 1
CookieAuthFile /etc/tor/run/control.authcookie
DataDirectory /var/lib/tor
RunAsDaemon 0
User tor
AutomapHostsOnResolve 1
ExitPolicy reject *:*
VirtualAddrNetworkIPv4 10.192.0.0/10
DNSPort 5353
SocksPort 0.0.0.0:9050 IsolateDestAddr
TransPort 0.0.0.0:9040
16:2CC93A3B5764D36C6001BF884CD278AFF4336326042AA58E1D8470F031
16:319987E84BC502E6601EA96885CBFF6AAD141A39478E263D63861D4CC4
16:EE6354F29D5D98A26048E257EF357272E8526EF7C45B11DCEE8F59813A
16:BA6B90FE5F36C24860CB31B665E4DA91582BA768151C49523A2433996E
16:A875BDE9A7849A6E6054762054252C971F5270B50FE8D9FFEF6901B52B
16:1E2E6317C73B0DE86092654F923467F46CBF8730B1C98525D231A7BF2E
16:5864150FFF9EEE0160110538AD434B66B2B948E81A4334F0203D27E9D1
StrictNodes 1
ExitNodes {NL}, {FR}, {GB}, {DE}, {LU}, {IT}, {CZ}, {IE}, {CH}, {SE}, {PL}, {ES}, {DK}, {MD}, {LV}, {UA}, {BG}, {EE}, {RO}, {TR}, {IL}, {US}, {CA}, {CY}
HashedControlPassword Jun 30 05:29:21.666 [warn] Tor was compiled with zstd 1.4.4, but is running with zstd 1.4.5. For safety, we'll avoid using advanced zstd functionality.
16:EEFFE1FB5254BA26607230ECAF2F645A9F77BD41E8DEA376E76487C48B

bash-5.0# su - tor -s/bin/bash -c "tor --hash-password Tor"
Jun 30 05:51:52.365 [warn] Tor was compiled with zstd 1.4.4, but is running with zstd 1.4.5. For safety, we'll avoid using advanced zstd functionality.
16:DF569BE55A4D6BB560F58A8DD8F203C94B4418E5FFB550D0CA0EBB6044

Does this image have a killswitch? In case Tor Connection fails will the Client use the real ip of the Host?

Hi,

when I try this command "curl -x http://localhost:8118 http://jsonip.com/" for testing it,
here raise a error message

curl: (56) Recv failure: Connection reset by peer

the image can't support http proxy?

I use TorIpChanger in Celery tasks, which is packaged in a Docker container together with torproxy, which is also packaged in a container and sometimes get an exception [2020-04-27 16: 41: 33,189: ERROR / ForkPoolWorker-2] Task api.resources.main.initialize [5c2122a8-0d73-4db4-b461-1ffd533064ca] raised unexpected: TorIpError ('Failed to obtain a new usable Tor IP')

[2020-04-27 16:41:25,476: DEBUG/ForkPoolWorker-2] GETCONF __owningcontrollerprocess (runtime: 0.0007)
[2020-04-27 16:41:25,478: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "read of closed file"
[2020-04-27 16:41:26,303: DEBUG/ForkPoolWorker-2] GETCONF __owningcontrollerprocess (runtime: 0.0006)
[2020-04-27 16:41:26,304: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "read of closed file"
[2020-04-27 16:41:27,146: DEBUG/ForkPoolWorker-2] GETCONF __owningcontrollerprocess (runtime: 0.0007)
[2020-04-27 16:41:27,148: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "read of closed file"
[2020-04-27 16:41:27,932: DEBUG/ForkPoolWorker-2] GETCONF __owningcontrollerprocess (runtime: 0.0008)
[2020-04-27 16:41:27,934: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "read of closed file"
[2020-04-27 16:41:28,708: DEBUG/ForkPoolWorker-2] GETCONF __owningcontrollerprocess (runtime: 0.0012)
[2020-04-27 16:41:28,742: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "read of closed file"
[2020-04-27 16:41:29,563: DEBUG/ForkPoolWorker-2] GETCONF __owningcontrollerprocess (runtime: 0.0007)
[2020-04-27 16:41:29,565: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "read of closed file"
[2020-04-27 16:41:30,354: DEBUG/ForkPoolWorker-2] GETCONF __owningcontrollerprocess (runtime: 0.0009)
[2020-04-27 16:41:30,356: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "read of closed file"
[2020-04-27 16:41:30,356: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "peek of closed file"
[2020-04-27 16:41:30,357: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "peek of closed file"
[2020-04-27 16:41:30,357: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "peek of closed file"
[2020-04-27 16:41:30,357: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "peek of closed file"
[2020-04-27 16:41:30,357: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "peek of closed file"
[2020-04-27 16:41:30,357: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "peek of closed file"
[2020-04-27 16:41:30,358: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "peek of closed file"
[2020-04-27 16:41:30,358: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "peek of closed file"
[2020-04-27 16:41:30,358: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "peek of closed file"
[2020-04-27 16:41:30,358: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "peek of closed file"
[2020-04-27 16:41:30,359: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "peek of closed file"
[2020-04-27 16:41:30,359: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "peek of closed file"
[2020-04-27 16:41:30,359: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "peek of closed file"
[2020-04-27 16:41:30,359: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "peek of closed file"
[2020-04-27 16:41:30,359: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "peek of closed file"
[2020-04-27 16:41:30,360: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "peek of closed file"
[2020-04-27 16:41:30,360: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "peek of closed file"
[2020-04-27 16:41:30,360: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "peek of closed file"
[2020-04-27 16:41:31,150: DEBUG/ForkPoolWorker-2] GETCONF __owningcontrollerprocess (runtime: 0.0006)
[2020-04-27 16:41:31,151: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "read of closed file"
[2020-04-27 16:41:31,913: DEBUG/ForkPoolWorker-2] GETCONF __owningcontrollerprocess (runtime: 0.0007)
[2020-04-27 16:41:31,914: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "read of closed file"
[2020-04-27 16:41:32,680: DEBUG/ForkPoolWorker-2] GETCONF __owningcontrollerprocess (runtime: 0.0008)
[2020-04-27 16:41:32,682: INFO/ForkPoolWorker-2] Error while receiving a control message (SocketClosed): received exception "read of closed file"

Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/celery/app/trace.py", line 385, in trace_task
    R = retval = fun(*args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/celery/app/trace.py", line 650, in __protected_call__
    return self.run(*args, **kwargs)
  File "/app/api/errors.py", line 131, in wrapped
    current_ip = tor_ip_changer.get_new_ip()
  File "/usr/local/lib/python3.7/site-packages/toripchanger/changer.py", line 113, in get_new_ip
    raise TorIpError("Failed to obtain a new usable Tor IP")
toripchanger.exceptions.TorIpError: Failed to obtain a new usable Tor IP

python -V
Python 3.7.6

uname -a
Linux 93a9f4b2cd04 4.19.75 #1 SMP PREEMPT Mon Mar 23 11:23:28 UTC 2020 aarch64 GNU/Linux

toripchanger==1.1.3