2017-01-10 01:17:07 +00:00
tor-socks-proxy
=======
2018-02-12 18:15:01 +00:00
![license ](https://img.shields.io/badge/license-GPLv3.0-brightgreen.svg?style=flat ) [![ ](https://img.shields.io/docker/pulls/peterdavehello/tor-socks-proxy.svg )](https://hub.docker.com/r/peterdavehello/tor-socks-proxy/) [![ ](https://images.microbadger.com/badges/image/peterdavehello/tor-socks-proxy.svg )](https://microbadger.com/images/peterdavehello/tor-socks-proxy/) [![ ](https://images.microbadger.com/badges/version/peterdavehello/tor-socks-proxy.svg )](https://hub.docker.com/r/peterdavehello/tor-socks-proxy/tags/)
2018-02-12 17:46:10 +00:00
2017-01-10 01:17:07 +00:00
The super easy way to setup a tor SOCKS5 proxy server without relay/exit feature.
## How to use?
1. Setup the proxy server at the **first time**
```sh
$ docker run -d --name tor_socks_proxy -p 127.0.0.1:9150:9150 peterdavehello/tor-socks-proxy:latest
```
2017-11-05 21:12:30 +00:00
- 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 valia 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:
2017-01-10 01:17:07 +00:00
```
$ docker start tor_socks_proxy
```
2017-11-05 21:12:30 +00:00
2. Make sure it's running, it'll take a short time to bootstrap
2017-01-10 01:17:07 +00:00
```
$ 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
```
2017-11-05 21:12:30 +00:00
3. Configure your client to use it, target on `127.0.0.1` port `9150` (Or the other port you setup in step 1)
2017-01-10 01:17:07 +00:00
2017-01-10 01:33:41 +00:00
Take `curl` as an example, checkout what's your ip address via tor nextwork:
```sh
$ curl --socks5-hostname 127.0.0.1:9150 ipinfo.io/ip
$ curl --socks5-hostname 127.0.0.1:9150 icanhazip.com
$ curl --socks5-hostname 127.0.0.1:9150 ipecho.net/plain
2017-11-05 21:12:30 +00:00
$ curl --socks5-hostname 127.0.0.1:9150 whatismyip.akamai.com
2017-01-10 01:33:41 +00:00
```
Take `ssh` and `nc` as an example, connect to a host via tor:
```sh
$ ssh -o ProxyCommand='nc -x 127.0.0.1:9150 %h %p' target.hostname.blah
```
2017-01-10 01:17:07 +00:00
4. After using it, you can turn it off
```sh
$ docker stop tor_socks_proxy
```
2017-11-05 21:19:59 +00:00
2017-11-05 21:19:16 +00:00
## How to renew IP?
2018-02-17 17:03:53 +00:00
- To renew the IP that Tor gives you, simply restart your docker container:
2017-11-05 21:19:16 +00:00
```sh
2017-11-05 21:19:59 +00:00
$ docker restart tor_socks_proxy
2017-11-05 21:19:16 +00:00
```
Just note that all the connections will be terminated and need to be reconnected.
2017-11-05 21:19:59 +00:00
## Note
2017-11-05 21:12:30 +00:00
2017-11-05 21:19:59 +00:00
**For the project sustainability I strongly encourge you to help setup Tor bridge/exit and donate money to the Tor project (Not this proxy project) when you have the ability/capacity!**