Menu
▾
▴
#1207 SOCKS4 negotiation write fails.
Ubuntu Jaunty, Privoxy 3.0.13, Firefox 3.0.3, whatever the latest version of Tor is.
When Tor is not on, and Privoxy is, I get this (of course, if Privoxy's config file is screwed, Tor doesn't work at all):
"Privoxy was unable to socks4a-forward your request <website> through 127.0.0.1: SOCKS4 negotiation write failed."
Config file is stock, except for the addition of: "forward-socks4a / 127.0.0.1:9050 ." to the top. The logfile is inexplicably empty (I didn't comment it out.)
What is going on? And how can this be fixed?
msalzer (AT) cox (DOT) net
The Privoxy config is telling it to forward your requests through Tor via your local TCP port 9050. When Tor is not on, then Privoxy gives that error because it's unable to forward them to Tor. If you comment out that forward-socks4a line in Privoxy then it will no longer try to send everything through Tor.
Okay, commenting out the socks-forwarding worked to get Privoxy working sans Tor. However, Privoxy + Tor still doesn't work when I want to use socks4a-fowarding:
"Privoxy was unable to socks4a-forward your request <http://google.com/> through 127.0.0.1: connect_to failed: see logfile for details."
Found the problem. Tor needed to be restarted on the command line for it to work. You can close this artifact up. Thanks.
Thanks for letting us know that you got it working.