#1686 Error 502 often...

[Peter Müller]

Hello there,

I often get the attached error 502:

No Server or forwarder data received ...

I've set in my config:

forwarded-connect-retries 10
forward-socks5t / 127.0.0.1:9050 .

No Firewall or Antivirus software installed.

but I still often receive this weird error... does anyone has an idea?

[Peter Müller]

Hello,
thanks very much!
Now I'm getting another error:
503, Socks5 connection refused.
why and how can I solve it?

[omgiafs]

Hi!
I had same problem. But i found that's not Privoxy problem, but Tor configuration problem.
You need to add this line to /etc/tor/torrc:

SocksPolicy accept 127.0.0.1/32

Privoxy and Tor works at one host (most users), so Privoxy connects to Tor through loopback interface, I think in this way.

Because of /Edit 2 i suggest this is Privoxy problem. Polipo works perfect with same Tor configuration.

/Edit Nope. Error 502 appears again...

/Edit 2 I tried to use Polipo with Tor. Polipo works perfect, no 502 errors at the same sites.
Minimal Polipo config:

logSyslog = false
logFile = /var/log/polipo/polipo.log

# Uncomment this if you want to disable the on-disk cache:
diskCacheRoot = ""

# Uncomment one of these if you want to allow remote clients to connect:
# proxyAddress = "::0"        # both IPv4 and IPv6
proxyAddress = "0.0.0.0"    # IPv4 only - Allow all connections - restrict the
# allowed clients below

proxyPort = 8118 # port on which to run the proxy

# If you do that, you'll want to restrict the set of hosts allowed to
# connect:
# allowedClients = "127.0.0.1, 134.157.168.57"
# allowedClients = "127.0.0.1, 134.157.168.0/24"

allowedClients = 127.0.0.1 # allow connections from the localhost
allowedClients = 192.168.1.0/24 # only allow connections from your network. 
allowedPorts = 1-65535

# Uncomment this if there's only one user using this instance of Polipo:
#cacheIsShared = false

# Uncomment this if you want to use a parent SOCKS proxy:
socksParentProxy = "localhost:9050" # Tor SOCKS proxy
socksProxyType = socks5

[Pastafarianist]

Has the fix from CVS become a part of any release?

[Fabian Keil]

Yes.

"When using socks5t, send the request body optimistically as well. Previously the request body wasn't guaranteed to be sent at all and the error message incorrectly blamed the server. Fixes #1686 reported by Peter Müller and G4JC."
http://www.privoxy.org/3.0.24/user-manual/whatsnew.html

The reason the ticket was still open is that Sourceforge broke the bug tracker a couple of months ago (even further), which prevented me from changing attributes or commenting from the browser. Looks like I found a workaround for this.

[Pastafarianist]

I wonder why you still haven't moved to Github then.

[Fabian Keil]

While Github may (currently!) be not as bad as SourceForge,
it still would be a poor choice for Privoxy.

For details, please have a look at our requirements:
http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO?view=markup#l465

I'm optimistic that the repository migration will happen
in the near future, though:
"- Users who don't trust binaries served by SourceForge
can get them from a mirror. Migrating away from SourceForge
is planned for 2016 (TODO list item #53)."
http://www.privoxy.org/3.0.24/user-manual/whatsnew.html