You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to reproduce the following example on my macOS (Monterey 12.6.3) and it fails with the following error: (I have brew installed proxychain version 4.16 )
$ ssh -fqCN -D 8080 some.example.com
$ PROXYCHAINS_SOCKS5=8080 proxychains4 zsh
I should add that I am currently using stunnel (using squid) here is my stunnel.conf
over this port and it is working fine on browsers, but it doesn't work on my bash (eg curl fails with socks5).
~$curl ifconfig
returns the following error, and I was/am hoping that proxychains can fix this. I have tried various combination of socks5, and --socks5-hostname, ... none has resolved this particular issue.
Trying 172.64.195.16:80...
Connected to ifconfig.io (172.64.195.16) port 80 (#0)
GET / HTTP/1.1
Host: ifconfig.io
User-Agent: curl/7.87.0
Accept: /
Empty reply from server
Closing connection 0
curl: (52) Empty reply from server
The text was updated successfully, but these errors were encountered:
Trying to reproduce the following example on my macOS (Monterey 12.6.3) and it fails with the following error: (I have brew installed proxychain version 4.16 )
$ ssh -fqCN -D 8080 some.example.com
$ PROXYCHAINS_SOCKS5=8080 proxychains4 zsh
I should add that I am currently using stunnel (using squid) here is my stunnel.conf
sslVersion = all
debug = 7
[squid]
client = yes
options = NO_SSLv2
options = DONT_INSERT_EMPTY_FRAGMENTS
cert = /usr/local/etc/stunnel/stunnel.pem
accept = 127.0.0.1:8080
connect = "host_ip":8888
over this port and it is working fine on browsers, but it doesn't work on my bash (eg curl fails with socks5).
~$curl ifconfig
returns the following error, and I was/am hoping that proxychains can fix this. I have tried various combination of socks5, and --socks5-hostname, ... none has resolved this particular issue.
curl: (52) Empty reply from server
The text was updated successfully, but these errors were encountered: