You are not logged in.

#1 2015-09-25 06:58:16

Niiic
Member
Registered: 2015-09-25
Posts: 1

Privoxy + Tor not communicating?

Hey everyone.

I'm having trouble with Privoxy routing Http requests through Tor on port 8118.
both services are activated and running, and I added "forward-socks5 / localhost:9050 ." to /etc/privoxy/conf

Tor works on its own, When I specify localhost:9050 in firefox. And Privoxy is enabled at 127.0.0.1:8118, but when I check 127.0.0.1, other than saying it is enabled on the correct port, it shows an error saying "Privoxy was unable to socks5-forward your request http://127.0.0.1/ through localhost: SOCKS5 request failed".

and when I check tor.service's status, it says "[warn] Rejecting SOCKS request for anonymous connection to private address [scrubbed]."
but privoxy.service's status shows nothing abnormal.

also, when I try to try to route vlc's socks5 using tor i recieve the errors...
[000003ba44000ee8] core access error: socks: CONNECT request failed
[000003ba44000ee8] core access error: SOCKS handshake failed
[000003ba44000ee8] http access error: cannot connect to localhost:8118

without even specifying that I wanted it to route Http through privoxy's 8118 port.

So what I've understood is that Privoxy is working and trying to route the connection through the proper port, but Tor isn't allowing it, for whatever reason, I havent editted the /etc/tor/torrc at all and the only change I've made to /etc/privoxy/config was the above line to forward traffic through 9050 so I'm unsure how to follow up.

Any help is much appreciated, I've spent all day trying to mess around with settings but can't seem to make it work. The frustrating thing is I had the two working together seemlessly on a previous install.

UPDATE: vlc issue was fixed when I unset the http_proxy environment variable. I'm able to manually set it to route http through port 8118 (unsure if this is doing anything at the moment due to the privoxy problem), And also use tor's 9050 port as well with no issues. while firefox still needs tor specifically listed, if not no proxy connection happens. So in all, the core issue still exists, but my association of vlc's issue with it was probably wrong.

Last edited by Niiic (2015-09-25 07:25:44)

Offline

Board footer

Powered by FluxBB