Looks like someone "customized" your Privoxy installation,
it also seems to be outdated (based on 3.0.3).
Please provide some information about how your Privoxy
version differs from the official configuration. If you're
unsure, just try again with the official Privoxy 3.0.6
from the download section.
If you're using a packet filter, you might want to check
it's configuration to make sure Privoxy is allowed to reach 217.12.10.252.
You could also try to ping 217.12.10.252, although a ping
success doesn't necessarily mean HTTP works as well.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Connect failed message
Logged In: YES
user_id=875547
Originator: NO
Looks like someone "customized" your Privoxy installation,
it also seems to be outdated (based on 3.0.3).
Please provide some information about how your Privoxy
version differs from the official configuration. If you're
unsure, just try again with the official Privoxy 3.0.6
from the download section.
If you're using a packet filter, you might want to check
it's configuration to make sure Privoxy is allowed to reach 217.12.10.252.
You could also try to ping 217.12.10.252, although a ping
success doesn't necessarily mean HTTP works as well.
Logged In: YES
user_id=1312539
Originator: NO
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).