[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Tor not working
Yes, I've checked the Tor config file and it's the original that is
installed, no changes by anyone, since I'm the only user. Also
checked the Vidalia log file, and here is what it says:
Oct 03 17:39:49:956 [Notice] Tor v0.1.1.24. This is experimental
software. Do not rely on it for strong anonymity.
Oct 03 17:39:49:975 [Notice] Initialized libevent version 1.1b using
method poll. Good.
Oct 03 17:39:49:984 [Notice] connection_create_listener(): Opening
Socks listener on 127.0.0.1:9050
Oct 03 17:39:49:993 [Notice] connection_create_listener(): Opening
Control listener on 127.0.0.1:9051
Oct 03 17:39:56:102 [Notice] We now have enough directory information
to build circuits.
Oct 03 17:40:10:227 [Warning] router_add_to_routerlist(): Dropping
unrecognized descriptor for router 'HTTPDNet'
Oct 03 17:40:10:234 [Warning] router_add_to_routerlist(): Dropping
unrecognized descriptor for router 'rodos'
Oct 03 17:40:10:242 [Warning] router_add_to_routerlist(): Dropping
unrecognized descriptor for router 'messerjocke'
Oct 03 17:40:15:752 [Notice] Tor has successfully opened a circuit.
Looks like client functionality is working.
So, any ideas as to how to solve this problem?
On Oct 3, 2006, at 5:39 PM, Fabian Keil wrote:
Spin Doctor <nil.bitbucket@xxxxxxxxx> top posted again:
On Oct 3, 2006, at 10:11 AM, Fabian Keil wrote:
Spin Doctor <nil.bitbucket@xxxxxxxxx> top posted (please don't):
Firefox displays the 503 error page, saying " This is Privoxy 3.0.3
on localhost (127.0.0.1), port 8118, enabled"
Your request for http://foo@xxxxxxxxxxx could not be fulfilled,
because the connection to foo@xxxxxxxxxxx (127.0.0.1) could not be
This is often a temporary failure, so you might just try again."
The easiest way to get this error message is not to start Tor,
or have it listening on another address than Privoxy is expecting.
Make sure that Tor is running and that its local address
is the one Privoxy is configured to use:
fk@TP51 ~ $lynx -dump http://config.privoxy.org/show-status | grep
forward-socks4a / 10.0.0.2:9050 .
fk@TP51 ~ $sockstat -4l -p 9050
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN
256 tor 862 5 tcp4 10.0.0.2:9050 *:*
No, it's running, as I made sure to use the startprivoxy.command file
in Terminal. I've checked the config file and it's as it should be;
no changes have been made. Torbutton is configured correctly, too.
If Tor was running and Privoxy was configured to use it,
you wouldn't see the error message for every request.
I also doubt that you are using a vanilla Privoxy configuration.
If you didn't change the configuration file, someone else did
it for you or your DNS settings are seriously broken.
I don't know what the "startprivoxy.command file" is supposed
to do, but from the name I would guess that it starts Privoxy
but not Tor.
Privoxy and Tor can operate on their own and it makes little
sense to control both with the same script.
Did you verify that you have a Tor process running?
Did you check Tor's log file as suggested by Roger and others?