Help with Proxychains4: Unable to Connect to Burp Suite (Port 8080)

2025-03-16T02:39:17.091000Z

Hello, Proxychains4 developers. I need your assistance.

I'm trying to use Proxychains4 to anonymize the requests made by my tool, TurboSearch, since SOCKS5 allows me to mask DNS resolutions. I'm also using Burp Suite, a tool to intercept and analyze HTTP/S traffic, aiming to send TurboSearch's findings directly to it.

For context, TurboSearch is an automated URL discovery tool widely used in security testing to identify possible API endpoints or vulnerable paths on a server. It sends HTTP(S) requests to a specified target using a wordlist (e.g., /api/login, /admin, etc.). My goal is to execute TurboSearch with Proxychains4, ensuring that requests are routed through the Tor network for anonymity, while the findings are sent to Burp Suite.

Here is my current Proxychains4 configuration (with comments and blank lines removed for simplicity):

strict_chain
proxy_dns
remote_dns_subnet 224
tcp_read_time_out 15000
tcp_connect_time_out 8000
[ProxyList]
socks5 127.0.0.1 9050
I confirmed that both Tor and Burp Suite are active and listening on their respective ports (9050 and 8080) using the following command:

netstat -platun | grep -E "8080|9050"
Command output:

(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 127.0.0.1:9050 0.0.0.0: LISTEN -
tcp6 0 0 127.0.0.1:8080 ::: LISTEN 3323/java
With this setup, I successfully executed TurboSearch using Proxychains4. Here’s the command and its corresponding output:

proxychains4 turbosearch -I -t https://api.client.com -w /usr/share/seclists/Discovery/Web-Content/api/api-endpoints.txt --method get,post,put,patch -D --random-agent
Explanation of TurboSearch options:

-I: Enables interactive mode, displaying detailed information about the requests and responses during execution.
-t https://api.client.com: Sets the target URL where TurboSearch will send requests.
-w /usr/share/seclists/Discovery/Web-Content/api/api-endpoints.txt: Specifies the path to the wordlist containing possible endpoints (e.g., /login, /admin).
--method get,post,put,patch: Defines the HTTP methods to use (GET, POST, PUT, PATCH).
-D: Activates "Double Path" mode, where TurboSearch tests concatenated paths like /api/api/login for possible vulnerabilities.
--random-agent: Makes TurboSearch use randomized User-Agents in requests to make traffic harder to identify.
--report-to http://127.0.0.1:8080 (when added): Sends the findings to Burp Suite, configured to listen on port 8080.
Partial output without --report-to:

[proxychains] config file found: /etc/proxychains4.conf
[proxychains] Strict chain ... 127.0.0.1:9050 ... api.client.com:443 ... OK
[+] Connectivity checker
[+] Connection test against https://api.client.com OK! (CODE:403|SIZE:335)
At this stage, everything works perfectly. Proxychains4 routes TurboSearch's requests through the Tor network, and scans run without any issues.

The problem:

When I include the --report-to http://127.0.0.1:8080 option in the TurboSearch command to send the findings to Burp Suite, Proxychains4 fails the connectivity check. Here's the updated command:

[proxychains] Strict chain ... 127.0.0.1:9050 ... 127.0.0.1:8080 <--socket error or timeout!
[!] Error connecting to url https://api.client.com using report to proxy http://127.0.0.1:8080
[!] Error: HTTPSConnectionPool(host='api.client.com', port=443): Max retries exceeded with url: / (Caused by ProxyError('Unable to connect to proxy', NewConnectionError('<urllib3.connection.httpsconnection object="" at="" 0x7fe1f6f9cb90="">: Failed to establish a new connection: [Errno 111] Connection refused')))
My interpretation of the issue:</urllib3.connection.httpsconnection>

I suspect the problem lies in the Proxychains4 configuration, as it seems unable to connect to Burp Suite on port 8080. Here are my thoughts:

strict_chain is enabled, which forces all connections to go through the configured proxy chain in the specified order. This includes routing local traffic (127.0.0.1:8080) through the Tor network (127.0.0.1:9050). This behavior doesn't make sense for localhost connections like those to Burp Suite.

dynamic_chain, another Proxychains4 option, allows connections to bypass non-responsive proxies and proceed with the remaining proxies in the chain. If enabled, the configuration would look like this:

dynamic_chain
proxy_dns
remote_dns_subnet 224
tcp_read_time_out 15000
tcp_connect_time_out 8000
[ProxyList]
socks5 127.0.0.1 9050
Although strict_chain seems like the likely cause, I don’t fully understand how dynamic_chain would resolve the issue, as the problem appears specific to Proxychains4 failing to reach Burp Suite on localhost.

Specific questions:

Is this behavior expected when using strict_chain?
Is there a way to ensure that local connections (e.g., to Burp Suite) are not routed through the Tor network unnecessarily?
Can Proxychains4 be configured differently to handle this situation?
If I’m overlooking something crucial, it might be because I’ve been struggling with this all day. Any guidance or suggestions would be greatly appreciated. Thank you so much!

New requirement: Need all purpose ACL in configuration

2024-06-26T07:29:17.800000Z

I posted the topic here at project proxychains-ng:
https://github.com/rofl0r/proxychains-ng/issues/571

Thanks!

Is a version for Raspbian expected?

2024-02-03T02:52:07.583000Z

Is a version for Raspberry Pi Bookworm expected?

Configuration not working

2022-10-24T04:26:33.660000Z

I am using Proxychains on Debian (QubesOS) and am attempting to use socks5 servers. It's hard to determine what I should ask in this post because pretty much everything I've tried has failed - typically what happens is it says "does not exist" next to website names in the terminal when I run $ proxychains firefox www. (website name ) .com

In granular detail, what is the proper formatting for entering authorized socks5 servers in the lower part of the proxychains.conf file? (tabs, spaces, etc). Should I leave an empty line after the - #defaults set to "tor" - line?
Tell me any fine details about formatting or anything I may be missing that may be throwing me off.

I've been doing it this way:

Socks Type (TAB) IP Address (TAB) Port (TAB) username (TAB) password

Haking

2022-09-19T03:23:32.858000Z

Proxified program uses direct connection

2022-03-12T19:30:21.190000Z

The proxified program uses direct connection

$ proxychains -f /etc/proxychains.conf '/home/m/Desktop/StatusIm-Desktop-v0.3.0-beta-a8c37d.AppImage' 
[proxychains] config file found: /etc/proxychains.conf
[proxychains] preloading /usr/lib/libproxychains4.so
[proxychains] DLL init: proxychains-ng 4.16
[proxychains] DLL init: proxychains-ng 4.16
[proxychains] DLL init: proxychains-ng 4.16
[proxychains] DLL init: proxychains-ng 4.16
[proxychains] DLL init: proxychains-ng 4.16
INFO [03-12|22:57:40.476] Status backend initialized               backend=geth version=0.85.0 commit=192ca6e3
Network Cache Dir:  "/home/m/.config/Status/tmp/netcache"
INF 2022-03-12 22:57:45+03:30 Starting application...                    topics="main" tid=7896 file=nim_status_client.nim:264
Network Cache Dir:  "/home/m/.config/Status/tmp/netcache"
DBG 2022-03-12 22:57:53+03:30 Login requested                            tid=7896 file=accounts.nim:208 user="Left Darkorange Swallowtail"
DBG 2022-03-12 22:57:54+03:30 callPrivateRPC                             topics="rpc" tid=7915 file=core.nim:20 rpc_method=settings_getSettings
DBG 2022-03-12 22:57:54+03:30 callPrivateRPC                             topics="rpc" tid=7915 file=core.nim:20 rpc_method=mailservers_getMailservers
DBG 2022-03-12 22:57:54+03:30 Verifying mailserver connection state...   topics="mailserver model" tid=7915 file=model.nim:196
WRN 2022-03-12 22:57:54+03:30 Automatically switching mailserver         topics="mailserver model" tid=7915 file=model.nim:186
WRN 2022-03-12 22:57:54+03:30 Finding a new mailserver...                topics="mailserver model" tid=7915 file=model.nim:164
DBG 2022-03-12 22:57:54+03:30 callPrivateRPC                             topics="rpc" tid=7915 file=core.nim:20 rpc_method=mailservers_ping
[proxychains] DLL init: proxychains-ng 4.16

(gst-plugin-scanner:7951): GStreamer-WARNING **: 22:57:54.675: Failed to load plugin '/tmp/.mount_StatusrbGwdb/usr/lib/gstreamer-1.0/libgstasf.so': /usr/lib/libgio-2.0.so.0: undefined symbol: g_module_open_full

(gst-plugin-scanner:7951): GStreamer-WARNING **: 22:57:54.753: Failed to load plugin '/tmp/.mount_StatusrbGwdb/usr/lib/gstreamer-1.0/libgstbluez.so': /usr/lib/libgio-2.0.so.0: undefined symbol: g_module_open_full
DBG 2022-03-12 22:57:54+03:30 Connecting to mailserver                   topics="mailserver model" tid=7915 file=model.nim:84 enode=1a4ab7d1d5dd67ca27427@178.128.142.94:443
DBG 2022-03-12 22:57:54+03:30 callPrivateRPC                             topics="rpc" tid=7915 file=core.nim:20 rpc_method=wakuext_updateMailservers

(gst-plugin-scanner:7951): GStreamer-WARNING **: 22:57:55.161: Failed to load plugin '/tmp/.mount_StatusrbGwdb/usr/lib/gstreamer-1.0/libgstdashdemux.so': /usr/lib/libgio-2.0.so.0: undefined symbol: g_module_open_full

(gst-plugin-scanner:7951): GStreamer-WARNING **: 22:57:55.353: Failed to load plugin '/tmp/.mount_StatusrbGwdb/usr/lib/gstreamer-1.0/libgstgdkpixbuf.so': /usr/lib/libgio-2.0.so.0: undefined symbol: g_module_open_full

(gst-plugin-scanner:7951): GStreamer-WARNING **: 22:57:55.361: Failed to load plugin '/tmp/.mount_StatusrbGwdb/usr/lib/gstreamer-1.0/libgstgio.so': /usr/lib/libgio-2.0.so.0: undefined symbol: g_module_open_full

(gst-plugin-scanner:7951): GStreamer-WARNING **: 22:57:55.524: Failed to load plugin '/tmp/.mount_StatusrbGwdb/usr/lib/gstreamer-1.0/libgstgtksink.so': /usr/lib/libgio-2.0.so.0: undefined symbol: g_module_open_full

(gst-plugin-scanner:7951): GStreamer-WARNING **: 22:57:56.229: Failed to load plugin '/tmp/.mount_StatusrbGwdb/usr/lib/gstreamer-1.0/libgstmultifile.so': /usr/lib/libgio-2.0.so.0: undefined symbol: g_module_open_full

(gst-plugin-scanner:7951): GStreamer-WARNING **: 22:57:56.458: Failed to load plugin '/tmp/.mount_StatusrbGwdb/usr/lib/gstreamer-1.0/libgstopencv.so': /usr/lib/libgio-2.0.so.0: undefined symbol: g_module_open_full

(gst-plugin-scanner:7951): GStreamer-WARNING **: 22:57:56.529: Failed to load plugin '/tmp/.mount_StatusrbGwdb/usr/lib/gstreamer-1.0/libgstpango.so': /usr/lib/libgio-2.0.so.0: undefined symbol: g_module_open_full

(gst-plugin-scanner:7951): GStreamer-WARNING **: 22:57:56.576: Failed to load plugin '/tmp/.mount_StatusrbGwdb/usr/lib/gstreamer-1.0/libgstrfbsrc.so': /usr/lib/libgio-2.0.so.0: undefined symbol: g_module_open_full

(gst-plugin-scanner:7951): GStreamer-WARNING **: 22:57:56.581: Failed to load plugin '/tmp/.mount_StatusrbGwdb/usr/lib/gstreamer-1.0/libgstrmdemux.so': /usr/lib/libgio-2.0.so.0: undefined symbol: g_module_open_full

(gst-plugin-scanner:7951): GStreamer-WARNING **: 22:57:56.609: Failed to load plugin '/tmp/.mount_StatusrbGwdb/usr/lib/gstreamer-1.0/libgstrsvg.so': /usr/lib/libgio-2.0.so.0: undefined symbol: g_module_open_full

(gst-plugin-scanner:7951): GStreamer-WARNING **: 22:57:56.646: Failed to load plugin '/tmp/.mount_StatusrbGwdb/usr/lib/gstreamer-1.0/libgstrtpmanager.so': /usr/lib/libgio-2.0.so.0: undefined symbol: g_module_open_full

(gst-plugin-scanner:7951): GStreamer-WARNING **: 22:57:56.662: Failed to load plugin '/tmp/.mount_StatusrbGwdb/usr/lib/gstreamer-1.0/libgstrtsp.so': /usr/lib/libgio-2.0.so.0: undefined symbol: g_module_open_full

(gst-plugin-scanner:7951): GStreamer-WARNING **: 22:57:56.731: Failed to load plugin '/tmp/.mount_StatusrbGwdb/usr/lib/gstreamer-1.0/libgstsdpelem.so': /usr/lib/libgio-2.0.so.0: undefined symbol: g_module_open_full

Error: no DISPLAY environment variable specified

2019-10-11T19:37:02.461000Z

Hi. I am new using this tool. When executing it, it gives me the following message:

root@mynamepc:~# proxychains firefox www.google.com
ProxyChains-3.1 (http://proxychains.sf.net)
No protocol specified
Unable to init server: Could not connect: Connection refused
Error: cannot open display: :0.0

This is my configuration in the file proxychains.conf

# 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
tcp_read_time_out 15000
tcp_connect_time_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

Note: I have started and stopped the program several times but the problem persists.

Applications that need binding a port

2019-07-07T03:24:24.817000Z

I need to run an app called Lethean through proxychain it need to start listenning on a port but does not allow this. I only want proxychains proxifies this app outgoing connections

Proxychains Timeout issue..

2019-02-05T21:49:49.524000Z

You are lucky!. My problem is worse. I don't even get any feedbback just the Proxychains-3.1 thing and nothing more. It just doesnt work

Proxychains not working for FQDN in proxychains.conf

2018-04-19T09:52:11.376000Z

When I am configuring a FQDN address in proxychains it is not working. I have to replace it with the IP address of the proxy server to make it work.

Not working:
http abcdxyz.com 8080 justu hidden

Have anyone noticed similar issue?

Thanks In advance..

Recent posts to Discussion