On 06/06/2015 06:17 AM, Liam O'Toole wrote:
On 2015-06-06, Kailash Kalyani <listskail...@gmail.com> wrote:
On Saturday 06 June 2015 08:41 AM, Kailash Kalyani wrote:
On Friday 05 June 2015 10:00 PM, Liam O'Toole wrote:
On 2015-06-05, Kailash Kalyani <listskail...@gmail.com> wrote:
On Friday 05 June 2015 08:37 PM, Liam O'Toole wrote:
On 2015-06-05, Kailash Kalyani <listskail...@gmail.com> wrote:
Hi All,
Came across privoxy and wanted to test it out so I installed it
sudo apt-get install privoxy
And configured my browser to use the proxy at
127.0.0.1 port 8118
I keep getting the error: "The proxy server is refusing connections"
I checked the privoxy config file and the log file. Log file's
empty and
the config file has a line:
listen-address localhost:8118
Would anyone have pointers on how to solve this?
Regards,
Kailash
Are you sure that privoxy is running?
Here's the output from ps.
$ps -ax | grep privoxy
1601 ? Ss 0:00 /usr/sbin/privoxy --pidfile
/var/run/privoxy.pid --user privoxy /etc/privoxy/config
So, looks like it is and it's using the correct config file.
Thanks,
Kailash
Yes, it does. Does "localhost" resolve to 127.0.0.1 correctly? I would
be surprised if it did not, but it's worth checking.
$ ping localhost
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.037 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.059 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.050 ms
64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.055 ms
I wonder if it's something in the config file, but I couldn't figure
it out.
Turns out that Liam was correct about the localhost issue. privoxy was
listening on the ipv6 localhost and not the ipv4.
A search on privoxy.org's mailing list resolved this:
http://sourceforge.net/p/ijbswa/mailman/message/30642470/
$sudo netstat -tunlp
tcp6 0 0 ::1:8118 :::* LISTEN 1601/privoxy
Went into /etc/privoxy/config and changed
listen-address localhost:8118
to
listen-address 127.0.0.1:8118
And now the issue's resolved.
Kailash
That's good news. It should also work if you approach it from the other
direction, i.e., tell the browser to connect to localhost instead of
127.0.0.1.
I wonder what he has in /etc/hosts?? Ric
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/55732bea.1050...@gmail.com
