I am pretty sure that you will not even haven to use the
workaround if
you make the suggested change to /etc/hosts.
Florian
Just an update - I deleted the redundant "localhost" entry in the
/etc/hosts file as suggested and accepted the Tor and Privoxy upgra
Florian Kulzer wrote:
On Wed, Jun 03, 2009 at 19:46:54 +0100, AG wrote:
Florian Kulzer wrote:
On Wed, Jun 03, 2009 at 18:31:43 +0100, AG wrote:
AG wrote:
I am attempting to get Tor and Privoxy working with Iceweasel,
but it keeps throwing up errors.
[.
On Wed, Jun 03, 2009 at 19:46:54 +0100, AG wrote:
> Florian Kulzer wrote:
>> On Wed, Jun 03, 2009 at 18:31:43 +0100, AG wrote:
AG wrote:
>
> I am attempting to get Tor and Privoxy working with Iceweasel,
> but it keeps throwing up errors.
[...]
> The following is my /etc/pri
Florian Kulzer wrote:
On Wed, Jun 03, 2009 at 18:31:43 +0100, AG wrote:
AG wrote:
Hello
I am attempting to get Tor and Privoxy working with Iceweasel, but it
keeps throwing up errors.
[...]
The following is my /etc/privoxy/config file (without the commented
sections
On Wed, Jun 03, 2009 at 18:31:43 +0100, AG wrote:
>> AG wrote:
>>> Hello
>>>
>>> I am attempting to get Tor and Privoxy working with Iceweasel, but it
>>> keeps throwing up errors.
[...]
>>> The following is my /etc/privoxy/config file (without the commented
>>> sections):
[...]
>>> listen-a
AG wrote:
AG wrote:
Hello
I am attempting to get Tor and Privoxy working with Iceweasel, but it
keeps throwing up errors.
The logfile has been enabled to record debugging info (1024 "Log the
destination for requests Privoxy didn't let through, and the reason
why", 4096 "start up banner and w
6 matches
Mail list logo
