🐳 Tiny Docker image (🤏 10MB) as 🧅 Tor SOCKS5 proxy 🛡
Go to file
2019-11-24 16:48:51 +08:00
.github Add GitHub FUNDING file 2019-07-13 23:03:59 +08:00
.travis.yml Move Travis CI Linux env to Ubuntu Bionic (18.04) 2019-07-21 22:50:24 +08:00
docker-compose.yml Add docker-compose file 2019-08-31 17:28:58 +08:00
Dockerfile Reduce an image layer by merging commands 2019-08-09 17:30:01 +08:00
README.md Add one another IP inspect service owned by me to README.md 2019-10-28 17:03:46 +08:00
renovate.json Add renovate.json 2019-11-24 08:41:25 +00:00
torrc Set HardwareAccel to 1 2019-08-31 21:46:31 +08:00

Tor-socks-proxy

license Build Status Docker Hub pulls Docker image layers Docker image version

Docker Hub badge

The super easy way to setup a Tor SOCKS5 proxy server inside a Docker container without relay/exit feature.

Usage

  1. Setup the proxy server at the first time

    $ docker run -d --name tor_socks_proxy -p 127.0.0.1:9150:9150 peterdavehello/tor-socks-proxy:latest
    
    • Use 127.0.0.1 to limit the connections from localhost, do not change it unless you know you're going to expose it to a local network or to the Internet.
    • Change to first 9150 to any valid and free port you want, please note that port 9050/9150 may already taken if you are also running other Tor client, like TorBrowser.
    • Do not touch the second 9150 as it's the port inside the docker container unless you're going to change the port in Dockerfile.

    If you already setup the instance before (not the first time), just start it:

    $ docker start tor_socks_proxy
    
  2. Make sure it's running, it'll take a short time to bootstrap

    $ docker logs tor_socks_proxy
    .
    .
    .
    Jan 10 01:06:59.000 [notice] Bootstrapped 85%: Finishing handshake with first hop
    Jan 10 01:07:00.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
    Jan 10 01:07:02.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
    Jan 10 01:07:02.000 [notice] Bootstrapped 100%: Done
    
  3. Configure your client to use it, target on 127.0.0.1 port 9150(Or the other port you setup in step 1)

    Take curl as an example, checkout what's your IP address via Tor network:

    $ curl --socks5-hostname 127.0.0.1:9150 https://ipinfo.tw/ip
    $ curl --socks5-hostname 127.0.0.1:9150 https://ipinfo.io/ip
    $ curl --socks5-hostname 127.0.0.1:9150 https://icanhazip.com
    $ curl --socks5-hostname 127.0.0.1:9150 https://ipecho.net/plain
    

    Take ssh and nc as an example, connect to a host via Tor:

    $ ssh -o ProxyCommand='nc -x 127.0.0.1:9150 %h %p' target.hostname.blah
    
  4. After using it, you can turn it off

    $ docker stop tor_socks_proxy
    

IP renewal

  • Tor changes circuit automatically every 10 minutes by default, which usually bring you the new IP address, it's affected by MaxCircuitDirtiness config, you can override it with your own torrc. See the official manual for more details.

  • To manually renew the IP that Tor gives you, simply restart your docker container to open a new circuit:

    $ docker restart tor_socks_proxy
    

    Just note that all the connections will be terminated and need to be reestablished.

Note

For the Tor project sustainability, I strongly encourage you to help setup Tor bridge/exit nodes(script) and donate money to the Tor project (Not this proxy project) when you have the ability/capacity!