[Privoxy-users] Privoxy can't forward socks requests

Mon Mar 27 20:11:42 UTC 2017

Hello, everyone.

I have a little problem with privoxy. When I'm trying to connect to any host
via socks of the privoxy I have a connection timeout problem. I'm trying to
use privoxy as proxy for tor network. But if I'm trying to use tor network
directly there is no any problem. I don't such problems at the HTTP proxy
mode. Only socks traffic can't be forwarded.

I did try to install privoxy on Windows (version 3.0.24 and 3.0.26), CentOS
(3.0.10 - from sources, 3.0.24 - RPM, 3.0.26 - RPM), Ubuntu-Server (3.0.26 -
deb). And at every system I had the same problem: privoxy can't forward
requests via socks. Does anyone have any ideas what can cause this type of
problem?

Here is some debugging info:

$ ss -tan

State       Recv-Q Send-Q  Local Address:Port     Peer Address:Port

LISTEN      0      128      192.168.0.16:43700               *:*

LISTEN      0      128         127.0.0.1:9050                *:*

$ curl -A test -x Socks5://192.168.0.16:43700 http://api.ipify.org

curl: (28) SOCKS5 read timeout

Output of all level debug is:

2017-03-25 22:32:23.943 7fe8cc5ce740 Connect: Waiting for the next client
connection. Currently active threads: 1

2017-03-25 22:32:23.943 7fe8cb336700 Connect: Accepted connection from
192.168.0.15 on socket 5

2017-03-25 22:32:23.944 7fe8cb336700 Received: from socket 5:
\x05\x02\x00\x01

2017-03-25 22:34:25.556 7fe8cc5ce740 Connect: Waiting for the next client
connection. Currently active threads: 2

2017-03-25 22:34:25.556 7fe8cab35700 Connect: Accepted connection from
192.168.0.2 on socket 3

2017-03-25 22:34:25.558 7fe8cab35700 Received: from socket 3:
\x04\x01\x01\xbbhk'FAlex\x00

2017-03-25 22:34:25.575 7fe8cc5ce740 Connect: Waiting for the next client
connection. Currently active threads: 3

2017-03-25 22:34:25.576 7fe8ca334700 Connect: Accepted connection from
192.168.0.2 on socket 7

2017-03-25 22:34:25.576 7fe8ca334700 Received: from socket 7:
\x04\x01\x00Phk'FAlex\x00

2017-03-25 22:34:28.016 7fe8cc5ce740 Connect: Waiting for the next client
connection. Currently active threads: 4

2017-03-25 22:34:28.017 7fe8c9b33700 Connect: Accepted connection from
192.168.0.2 on socket 8

2017-03-25 22:34:28.017 7fe8c9b33700 Received: from socket 8:
\x04\x01\x01\xbb\xb9U\x0d\x9aAlex\x00

2017-03-25 22:35:25.465 7fe8cc5ce740 Connect: Waiting for the next client
connection. Currently active threads: 5

2017-03-25 22:35:25.465 7fe8c9332700 Connect: Accepted connection from
192.168.0.2 on socket 9

2017-03-25 22:35:25.465 7fe8c9332700 Received: from socket 9:
\x04\x01\x01\xbb]\xb8\xdd\xc8Alex\x00

2017-03-25 22:35:26.062 7fe8cc5ce740 Connect: Waiting for the next client
connection. Currently active threads: 6

2017-03-25 22:35:26.063 7fe8c8b31700 Connect: Accepted connection from
192.168.0.2 on socket 10

2017-03-25 22:35:26.063 7fe8c8b31700 Received: from socket 10:
\x04\x01\x01\xbb]\xb8\xdd\xc8Alex\x00

2017-03-25 22:35:30.556 7fe8cc5ce740 Connect: Waiting for the next client
connection. Currently active threads: 7

2017-03-25 22:35:30.557 7fe8b3fff700 Connect: Accepted connection from
192.168.0.2 on socket 11

2017-03-25 22:35:30.557 7fe8b3fff700 Received: from socket 11:
\x04\x01\x01\xbb\xccO\xc5\xc8Alex\x00

2017-03-25 22:37:23.962 7fe8cb336700 Connect: The client side of the
connection on socket 5 got closed without sending a complete request line.

2017-03-25 22:37:23.962 7fe8cb336700 Connect: Closing client socket 5.
Keep-alive: 0. Socket alive: 0. Data available: 0. Configuration file change
detected: 0. Requests received: 1.

2017-03-25 22:37:27.766 7fe8cc5ce740 Connect: Waiting for the next client
connection. Currently active threads: 7

2017-03-25 22:37:27.766 7fe8cb336700 Connect: Accepted connection from
192.168.0.2 on socket 5

2017-03-25 22:37:27.767 7fe8cb336700 Received: from socket 5:
\x04\x01\x01\xbb\xb9U\x0d\x9aAlex\x00

2017-03-25 22:39:25.653 7fe8cab35700 Connect: No request line on socket 3
received in time. Timeout: 300.

2017-03-25 22:39:25.653 7fe8cab35700 Writing: to socket 3: HTTP/1.1 504
Connection timeout\x0d\x0aContent-Type: text/plain\x0d\x0aConnection:
close\x0d\x0a\x0d\x0aThe connection timed out because the client request
didn't arrive in time.\x0d\x0a

2017-03-25 22:39:25.653 7fe8cab35700 Connect: Closing client socket 3.
Keep-alive: 0. Socket alive: 1. Data available: 0. Configuration file change
detected: 0. Requests received: 1.

2017-03-25 22:39:25.654 7fe8ca334700 Connect: No request line on socket 7
received in time. Timeout: 300.

2017-03-25 22:39:25.654 7fe8ca334700 Writing: to socket 7: HTTP/1.1 504
Connection timeout\x0d\x0aContent-Type: text/plain\x0d\x0aConnection:
close\x0d\x0a\x0d\x0aThe connection timed out because the client request
didn't arrive in time.\x0d\x0a

2017-03-25 22:39:25.654 7fe8ca334700 Connect: Closing client socket 7.
Keep-alive: 0. Socket alive: 1. Data available: 0. Configuration file change
detected: 0. Requests received: 1.

2017-03-25 22:39:28.054 7fe8c9b33700 Connect: No request line on socket 8
received in time. Timeout: 300.

2017-03-25 22:39:28.054 7fe8c9b33700 Writing: to socket 8: HTTP/1.1 504
Connection timeout\x0d\x0aContent-Type: text/plain\x0d\x0aConnection:
close\x0d\x0a\x0d\x0aThe connection timed out because the client request
didn't arrive in time.\x0d\x0a

2017-03-25 22:39:28.054 7fe8c9b33700 Connect: Closing client socket 8.
Keep-alive: 0. Socket alive: 1. Data available: 0. Configuration file change
detected: 0. Requests received: 1.

2017-03-25 22:40:25.562 7fe8c9332700 Connect: No request line on socket 9
received in time. Timeout: 300.

2017-03-25 22:40:25.562 7fe8c9332700 Writing: to socket 9: HTTP/1.1 504
Connection timeout\x0d\x0aContent-Type: text/plain\x0d\x0aConnection:
close\x0d\x0a\x0d\x0aThe connection timed out because the client request
didn't arrive in time.\x0d\x0a

2017-03-25 22:40:25.562 7fe8c9332700 Connect: Closing client socket 9.
Keep-alive: 0. Socket alive: 1. Data available: 0. Configuration file change
detected: 0. Requests received: 1.

2017-03-25 22:40:26.163 7fe8c8b31700 Connect: No request line on socket 10
received in time. Timeout: 300.

2017-03-25 22:40:26.163 7fe8c8b31700 Writing: to socket 10: HTTP/1.1 504
Connection timeout\x0d\x0aContent-Type: text/plain\x0d\x0aConnection:
close\x0d\x0a\x0d\x0aThe connection timed out because the client request
didn't arrive in time.\x0d\x0a

2017-03-25 22:40:26.163 7fe8c8b31700 Connect: Closing client socket 10.
Keep-alive: 0. Socket alive: 1. Data available: 0. Configuration file change
detected: 0. Requests received: 1.

2017-03-25 22:40:28.074 7fe8cc5ce740 Connect: Waiting for the next client
connection. Currently active threads: 3

2017-03-25 22:40:28.074 7fe8c8b31700 Connect: Accepted connection from
192.168.0.2 on socket 3

2017-03-25 22:40:28.074 7fe8c8b31700 Received: from socket 3:
\x04\x01\x01\xbb\xb9U\x0d\x9aAlex\x00

2017-03-25 22:40:30.653 7fe8b3fff700 Connect: No request line on socket 11
received in time. Timeout: 300.

2017-03-25 22:40:30.653 7fe8b3fff700 Writing: to socket 11: HTTP/1.1 504
Connection timeout\x0d\x0aContent-Type: text/plain\x0d\x0aConnection:
close\x0d\x0a\x0d\x0aThe connection timed out because the client request
didn't arrive in time.\x0d\x0a

2017-03-25 22:40:30.653 7fe8b3fff700 Connect: Closing client socket 11.
Keep-alive: 0. Socket alive: 1. Data available: 0. Configuration file change
detected: 0. Requests received: 1.

2017-03-25 22:42:27.859 7fe8cb336700 Connect: No request line on socket 5
received in time. Timeout: 300.

2017-03-25 22:42:27.859 7fe8cb336700 Writing: to socket 5: HTTP/1.1 504
Connection timeout\x0d\x0aContent-Type: text/plain\x0d\x0aConnection:
close\x0d\x0a\x0d\x0aThe connection timed out because the client request
didn't arrive in time.\x0d\x0a

2017-03-25 22:42:27.859 7fe8cb336700 Connect: Closing client socket 5.
Keep-alive: 0. Socket alive: 1. Data available: 0. Configuration file change
detected: 0. Requests received: 1.

2017-03-25 22:43:28.094 7fe8cc5ce740 Connect: Waiting for the next client
connection. Currently active threads: 2

2017-03-25 22:43:28.094 7fe8cb336700 Connect: Accepted connection from
192.168.0.2 on socket 5

2017-03-25 22:43:28.094 7fe8cb336700 Received: from socket 5:
\x04\x01\x01\xbb\xb9U\x0d\x9aAlex\x00

2017-03-25 22:44:37.731 7fe8c8b31700 Connect: The client side of the
connection on socket 3 got closed without sending a complete request line.

2017-03-25 22:44:37.731 7fe8c8b31700 Connect: Closing client socket 3.
Keep-alive: 0. Socket alive: 0. Data available: 0. Configuration file change
detected: 0. Requests received: 1.

The tor network is working well:

curl -A test --socks5 127.0.0.1:9050 http://api.ipify.org        

217.170.201.106

My configuration file is (without full debug):

confdir /etc/privoxy

logdir /var/log/privoxy

logfile privoxy.log

actionsfile match-all.action

actionsfile default.action

actionsfile user.action

filterfile default.filter

filterfile user.filter

debug     1

debug  1024

debug  4096

debug  8192

toggle  1

enable-remote-toggle  0

enable-remote-http-toggle  0

enable-edit-actions 0

enforce-blocks 0

buffer-limit 4096

enable-proxy-authentication-forwarding 0

forwarded-connect-retries  0

accept-intercepted-requests 1

allow-cgi-request-crunching 0

split-large-forms 0

keep-alive-timeout 5

tolerate-pipelining 1

socket-timeout 300

listen-address 192.168.0.16:43700

forward / .

forward-socks5t / 127.0.0.1:9050 .

There is no firewall or selinux. So I'm out of ideas why it don't work.

Best Regards,

Aleksabder.