Forum Thread: How to Get Proxychains to Work?

I installed kali linux last week and started a new tutorial on Ethical hacking, Everytime I try to get proxychains to work it timesout I tried different Wi-Fi but just the same. Thats what it type for me.

proxychains firefox www.google.co.uk
ProxyChains-3.1 (http://proxychains.sf.net)
|DNS-request| detectportal.firefox.com
|D-chain|-<>-127.0.0.1:9050-<>-127.0.0.1:9050-<--denied
|D-chain|-<>-127.0.0.1:9050-<><>-4.2.2.2:53-|DNS-request| www.google.co.uk
|D-chain|-<>-127.0.0.1:9050-<>-127.0.0.1:9050-<--denied
|D-chain|-<>-127.0.0.1:9050-<><>-4.2.2.2:53-|DNS-request| self-repair.mozilla.org
|D-chain|-<>-127.0.0.1:9050-<>-127.0.0.1:9050-<--denied
|D-chain|-<>-127.0.0.1:9050-<><>-4.2.2.2:53-<--timeout
|D-chain|-<>-127.0.0.1:9050-<><>-4.2.2.2:53-<--timeout
|D-chain|-<>-127.0.0.1:9050-<><>-4.2.2.2:53-<--timeout
|D-chain|-<>-127.0.0.1:9050-<><>-4.2.2.2:53-<--timeout
|D-chain|-<>-127.0.0.1:9050-<><>-4.2.2.2:53-<--timeout
|D-chain|-<>-127.0.0.1:9050-<><>-4.2.2.2:53-<--timeout
|D-chain|-<>-127.0.0.1:9050-<><>-4.2.2.2:53-<--timeout
|DNS-response|: detectportal.firefox.com does not exist
|DNS-request| detectportal.firefox.com
|D-chain|-<>-127.0.0.1:9050-<>-127.0.0.1:9050-<--denied
|D-chain|-<>-127.0.0.1:9050-<><>-4.2.2.2:53-<--timeout
|DNS-response|: www.google.co.uk does not exist
|DNS-request| www.google.co.uk
|D-chain|-<>-127.0.0.1:9050-<>-127.0.0.1:9050-<--denied
|D-chain|-<>-127.0.0.1:9050-<><>-4.2.2.2:53-<--timeout
|DNS-response|: self-repair.mozilla.org does not exist
|DNS-request| self-repair.mozilla.org
|D-chain|-<>-127.0.0.1:9050-<>-127.0.0.1:9050-<--denied
|D-chain|-<>-127.0.0.1:9050-<><>-4.2.2.2:53-<--timeout
|D-chain|-<>-127.0.0.1:9050-<><>-4.2.2.2:53-<--timeout
|D-chain|-<>-127.0.0.1:9050-<><>-4.2.2.2:53-<--timeout
|D-chain|-<>-127.0.0.1:9050-<><>-4.2.2.2:53-<--timeout
|D-chain|-<>-127.0.0.1:9050-<><>-4.2.2.2:53-<--timeout
|D-chain|-<>-127.0.0.1:9050-<><>-4.2.2.2:53-<--timeout
|D-chain|-<>-127.0.0.1:9050-<><>-4.2.2.2:53-^A<--timeout
|DNS-response|: detectportal.firefox.com does not exist
<--timeout
|DNS-response|: www.google.co.uk does not exist
|DNS-request| support.mozilla.org
|D-chain|-<>-127.0.0.1:9050-<>-127.0.0.1:9050-<--denied
|D-chain|-<>-127.0.0.1:9050-<><>-4.2.2.2:53-|DNS-request| www.google.co.uk
|D-chain|-<>-127.0.0.1:9050-<>-127.0.0.1:9050-<--denied
|D-chain|-<>-127.0.0.1:9050-<><>-4.2.2.2:53-<--timeout
|DNS-response|: self-repair.mozilla.org does not exist

Thats The Proxychains.conf file:

# proxychains.conf VER 3.1
#
# HTTP, SOCKS4, SOCKS5 tunneling proxifier with DNS.
#

# The option below identifies how the ProxyList is treated.
# only one option should be uncommented at time,
# otherwise the last appearing option will be accepted
#
dynamic_chain
#
# Dynamic - Each connection will be done via chained proxies
# all proxies chained in the order as they appear in the list
# at least one proxy must be online to play in chain
# (dead proxies are skipped)
# otherwise EINTR is returned to the app
#
#strict_chain
#
# Strict - Each connection will be done via chained proxies
# all proxies chained in the order as they appear in the list
# all proxies must be online to play in chain
# otherwise EINTR is returned to the app
#
#random_chain
#
# Random - Each connection will be done via random proxy
# (or proxy chain, see chain_len) from the list.
# this option is good to test your IDS :)

# Make sense only if random_chain
#chain_len = 2

# Quiet mode (no output from library)
#quiet_mode

# Proxy DNS requests - no leak for DNS data
proxy_dns

# Some timeouts in milliseconds
tcpreadtime_out 15000
tcpconnecttime_out 8000

# ProxyList format
# type host port user pass
# (values separated by 'tab' or 'blank')
#
#
# Examples:
#
# socks5 192.168.67.78 1080 lamer secret
# http 192.168.89.3 8080 justu hidden
# socks4 192.168.1.49 1080
# http 192.168.39.93 8080
#
#
# proxy types: http, socks4, socks5
# ( auth types supported: "basic"-http "user/pass"-socks )
#
ProxyList
# add proxy here ...
# meanwile
# defaults set to "tor"
socks4 127.0.0.1 9050
socks5 127.0.0.1 9050

PLEASE HELP

2 Responses

# defaults set to "tor"
socks4 127.0.0.1 9050
#socks5 127.0.0.1 9050

try start tor service

apt install tor
service tor start

# I personaly prefer to run the tor program itself, as i have had issues with
# the service, if it's your case, just type "tor" in a terminal window.
------------------------------------------------------------------------------------------

Oh, and you also don't need to use "socks4", only "socks5". Leaving it that way will only make your traffic go through TOR in socks4, then go back to your machine (127.0.0.1) and use yourself as another proxy, this time through socks5, in other words, slow as fuck.

Share Your Thoughts

  • Hot
  • Active