How to get Tor to work?

SentralOrigin · 04-10-2009, 12:14 PM

I just installed a fresh copy of stable Debian, and apt-get installed Iceweasel and Tor/Privoxy (apt-get install tor automatically obtains Privoxy). I went into /etc/privoxy/config and uncommented the socks4a line that makes Tor and Privoxy work together. I made sure /etc/init.d/tor and /etc/init.d/privoxy were both started, Then I got iceweasel-torbutton with apt-get. I fired up Iceweasel and turned on Torbutton, but after a while I get the Privoxy page error with every website I go to. I tried doing "torify iceweasel" in the terminal, but I get the same Privoxy page error. What settings do I need to change?

repo · 04-10-2009, 12:26 PM

Take a look in
/var/log/tor/log
for error messages.

Take a look at
http://www.torproject.org/docs/tor-doc-unix.html.en
for a step to step guide

SentralOrigin · 04-10-2009, 01:02 PM

Code:

Apr 10 08:56:08.011 [warn] Received directory with skewed time (server '128.31.0.34:9001'): It seems that our clock is behind by 4 hours, 1 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time and date settings.
Apr 10 08:56:08.019 [notice] I learned some more directory information, but not enough to build a circuit: We have no network-status consensus.
Apr 10 08:56:11.533 [warn] Received directory with skewed time (server '216.224.124.114:9090'): It seems that our clock is behind by 4 hours, 1 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time and date settings.
Apr 10 08:56:11.576 [warn] Our clock is 3 hours, 3 minutes behind the time published in the consensus network status document (2009-04-10 16:00:00 GMT).  Tor needs an accurate clock to work correctly. Please check your time and date settings!
Apr 10 08:56:11.576 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
Apr 10 08:58:44.013 [notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Apr 10 08:58:57.713 [notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Apr 10 09:00:22.211 [notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Apr 10 09:00:44.309 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Apr 10 09:00:57.361 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Apr 10 09:02:22.711 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Apr 10 09:02:55.833 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Apr 10 09:03:43.086 [notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Apr 10 09:03:57.496 [notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Apr 10 09:04:58.624 [notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Apr 10 09:05:00.541 [warn] Our clock is 3 hours, 55 minutes behind the time published in the consensus network status document (2009-04-10 17:00:00 GMT).  Tor needs an accurate clock to work correctly. Please check your time and date settings!
Apr 10 09:05:00.541 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
Apr 10 09:05:43.469 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Apr 10 09:05:57.521 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Apr 10 09:06:58.749 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Apr 10 09:53:19.129 [notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Apr 10 09:55:19.013 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Apr 10 09:57:19.589 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Apr 10 09:57:19.589 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)

repo · 04-10-2009, 01:15 PM

Did you followed the steps on
http://www.torproject.org/docs/tor-doc-unix.html.en

SentralOrigin · 04-10-2009, 01:42 PM

Yea, I did:
apt-get install tor
edit /etc/privoxy/config
apt-get install iceweasel-torbutton

That's what the instructions said

And my browser says:

Code:

503  	
This is Privoxy 3.0.9 on localhost (127.0.0.1), port 8118, enabled
Warning:

This Privoxy version is based on beta code and not intended for production systems!
Use at your own risk. See the license for details.
Forwarding failure

Privoxy was unable to socks4a-forward your request https://check.torproject.org:443/ through 127.0.0.1: SOCKS request rejected or failed.

Just try again to see if this is a temporary problem, or check your forwarding settings and make sure that all forwarding servers are working correctly and listening where they are supposed to be listening.

It says this for every website I try to go to (not just https://check.torproject.org)

AlucardZero · 04-10-2009, 01:48 PM

Wait 10 minutes for a circuit and try again?

SentralOrigin · 04-10-2009, 01:49 PM

Quote:

Originally Posted by AlucardZero

Wait 10 minutes for a circuit and try again?

What is that? Anyway, I'll wait 10 minutes and restart my browser and turn on Tor and try it again

repo · 04-10-2009, 01:51 PM

did you added

Quote:

forward-socks4a / 127.0.0.1:9050 .

any firewall proxy?
try to disable the firewall

Make sure your clock is correct

more tips
https://wiki.torproject.org/noreply/...nectionPrivate

SentralOrigin · 04-10-2009, 02:06 PM

Oh, I just fixed my computer clock time and now it works. Wow