Docker Container
-------------------------------------
(Optional) <-> Tor Proxy 1
Client <----> Privoxy <-> HAproxy <-> Tor Proxy 2
<-> Tor Proxy n
Why: Lots of IP addresses. One single endpoint for your client. Load-balancing by HAproxy.
Optionaly adds support for Privoxy using -e privoxy=1, useful for http (default 8118, changable via -e privoxy_port=<port>) proxy forward and ad removal.
tors- Integer, number of tor instances to run.new_circuit_period- Integer, NewCircuitPeriod parameter value.privoxy- Boolean, whatever to run insance of privoxy in front of haproxy.privoxy_port- Integer, port for privoxy.haproxy_port- Integer, port for haproxy.haproxy_stats- Integer, port for haproxy monitor.haproxy_loginandhaproxy_pass- BasicAuth config for haproxy monitor.
# build docker container
docker build -t zeta0/alpine-tor:latest .
# ... or pull docker container
docker pull zeta0/alpine-tor:latest
# start docker container
docker run -d -p 5566:5566 -p 2090:2090 -e tors=25 zeta0/alpine-tor
# start docker with privoxy enabled and exposed
docker run -d -p 8118:8118 -p 2090:2090 -e tors=25 -e privoxy=1 zeta0/alpine-tor
# test with ...
curl --socks5 localhost:5566 http://echoip.com
# or if privoxy enabled ...
curl --proxy localhost:8118 http://echoip.com
# or to run chromium with your new found proxy
chromium --proxy-server="http://localhost:8118" --host-resolver-rules="MAP * 0.0.0.0 , EXCLUDE localhost"
# monitor
# auth login:admin
# auth pass:admin
http://localhost:2090 or http://admin:admin@localhost:2090
# start docket container with new auth
docker run -d -p 5566:5566 -p 2090:2090 -e haproxy_login=MySecureLogin -e haproxy_pass=MySecurePassword zeta0/alpine-tor