Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

socket error when http request #87

Closed
toniss opened this issue Oct 8, 2015 · 6 comments
Closed

socket error when http request #87

toniss opened this issue Oct 8, 2015 · 6 comments

Comments

@toniss
Copy link

toniss commented Oct 8, 2015

proxychains works fine when the request is https but gives me an error if the request is http. This is my config:

strict_chain
chain_len = 1

quiet_mode

proxy_dns
remote_dns_subnet 127
remote_dns_subnet 10
tcp_read_time_out 15000
tcp_connect_time_out 8000
localnet 127.0.0.0/255.0.0.0
localnet 10.0.0.0/255.0.0.0
[ProxyList]
http 127.0.0.1 8082

and this is an output example using iceweasel browser

[proxychains] Strict chain ... 127.0.0.1:8080 ... google.com:80 <--socket error or timeout!
[proxychains] Strict chain ... 127.0.0.1:8080 ... google.com:80 <--socket error or timeout!
[proxychains] Strict chain ... 127.0.0.1:8080 ... google.com:80 <--socket error or timeout!
[proxychains] Strict chain ... 127.0.0.1:8080 ... google.com:80 <--socket error or timeout!
[proxychains] Strict chain ... 127.0.0.1:8080 ... google.com:80 <--socket error or timeout!
[proxychains] Strict chain ... 127.0.0.1:8080 ... google.com:80 <--socket error or timeout!

I tried everything that I found on google, so far nothing work. Help!

@rofl0r
Copy link
Owner

rofl0r commented Oct 8, 2015

your proxy seems to be a local application. maybe it's misconfigured ?

@dkreider
Copy link

dkreider commented Oct 8, 2015

Your config file shows " http 127.0.0.1 8082 " and the output is 127.0.01:8080.

Why would this be if proxychains is configured to use port 8082? Port redirects?

@rofl0r
Copy link
Owner

rofl0r commented Oct 8, 2015

oh btw you should put remote_dns_subnet 224 in your config and remove the 2 entries you have there
they overlap with your localnet and with the address of your proxy so thats a seriously wrong setup.

@toniss
Copy link
Author

toniss commented Oct 9, 2015

the problem persist, these are two output examples:

#proxychains4 nc google.com 80
[proxychains] config file found: /etc/proxychains.conf
[proxychains] preloading /usr/local/lib/libproxychains4.so
[proxychains] DLL init: proxychains-ng 4.10
[proxychains] Strict chain ... 127.0.0.1:8082 ... google.com:80 <--socket error or timeout!
google.com [224.0.0.1] 80 (http) : Connection refused

#proxychains4 nc google.com 443
[proxychains] config file found: /etc/proxychains.conf
[proxychains] preloading /usr/local/lib/libproxychains4.so
[proxychains] DLL init: proxychains-ng 4.10
[proxychains] Strict chain ... 127.0.0.1:8082 ... google.com:443 ... OK
^C
the conf is this:

chain_len = 1
#dynamic_chain
strict_chain
#quiet_mode
proxy_dns
remote_dns_subnet 224
tcp_read_time_out 15000
tcp_connect_time_out 8000
localnet 10.0.0.0/255.0.0.0
[ProxyList]
http 127.0.0.1 8082

@rofl0r
Copy link
Owner

rofl0r commented Oct 9, 2015

in that case it's your proxy thats misconfigured...

@toniss
Copy link
Author

toniss commented Oct 13, 2015

The problem was the proxy only accept method connect at port 443.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants