Tor Browser Bundle 1.2.5 and 1.2.6 released

by phobos | August 6, 2009

Tor Browser Bundle 1.2.5 and 1.2.6 are released.

The changes for the respective releases are:

1.2.5: Released 2009-07-25
update Tor to 0.2.1.18

1.2.6: Released 2009-07-28
update Tor to 0.2.1.19

Comments

Please note that the comment area below has been archived.

I'm having trouble

I'm having trouble conncecting to the tor network on my win xp laptop. I can connect fine on my vista pc... Here is the message log, thanks.

Aug 05 01:21:02.750 [Notice] Tor v0.2.1.19. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 2 [workstation] {terminal services, single user})
Aug 05 01:21:02.859 [Notice] Initialized libevent version 1.4.11-stable using method win32. Good.
Aug 05 01:21:02.859 [Notice] Opening Socks listener on 127.0.0.1:9050
Aug 05 01:21:02.859 [Notice] Opening Control listener on 127.0.0.1:9051
Aug 05 01:21:02.859 [Notice] Parsing GEOIP file.
Aug 05 01:21:04.156 [Notice] Bootstrapped 20%: Asking for networkstatus consensus.
Aug 05 01:21:04.234 [Notice] Bootstrapped 25%: Loading networkstatus consensus.
Aug 05 01:21:05.265 [Warning] Our clock is 23 hours, 38 minutes behind the time published in the consensus network status document (2009-08-06 07:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
Aug 05 01:21:05.265 [Notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
Aug 05 01:23:22.093 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Aug 05 01:25:22.468 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Aug 05 01:25:22.546 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Aug 05 01:25:48.156 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Aug 05 01:27:22.562 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Aug 05 01:27:22.562 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Aug 05 01:27:22.593 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Aug 05 01:27:48.578 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Aug 05 01:28:56.453 [Notice] Tor v0.2.1.19. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 2 [workstation] {terminal services, single user})
Aug 05 01:28:56.562 [Notice] Initialized libevent version 1.4.11-stable using method win32. Good.
Aug 05 01:28:56.562 [Notice] Opening Socks listener on 127.0.0.1:9050
Aug 05 01:28:56.562 [Notice] Opening Control listener on 127.0.0.1:9051
Aug 05 01:28:56.562 [Notice] Parsing GEOIP file.
Aug 05 01:28:58.656 [Notice] Bootstrapped 15%: Establishing an encrypted directory connection.
Aug 05 01:28:59.093 [Notice] Bootstrapped 20%: Asking for networkstatus consensus.
Aug 05 01:28:59.281 [Notice] Bootstrapped 25%: Loading networkstatus consensus.
Aug 05 02:30:00.906 [Warning] Our clock is 23 hours, 30 minutes behind the time published in the consensus network status document (2009-08-06 08:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
Aug 05 02:30:00.906 [Notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
Aug 05 04:29:57.640 [Warning] Our clock is 23 hours, 30 minutes behind the time published in the consensus network status document (2009-08-06 10:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
Aug 05 04:29:57.640 [Notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
Aug 05 05:30:00.359 [Warning] Our clock is 23 hours, 30 minutes behind the time published in the consensus network status document (2009-08-06 11:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
Aug 05 05:30:00.359 [Notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.

re: trouble

Well, this is probably your biggest problem:

"Our clock is 23 hours, 30 minutes behind the time published in the consensus network status document (2009-08-06 11:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!"

you should fix your clock first.

Tor giving trouble

My tor used to work fine until 3 days back but now I am getting these these msges in log file and am not getting any relays.

Sep 04 01:43:29.360 [Notice] Tor v0.2.1.19. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 3 [workstation] {personal} {terminal services, single user})
Sep 04 01:43:29.360 [Notice] Initialized libevent version 1.4.11-stable using method win32. Good.
Sep 04 01:43:29.360 [Notice] Opening Socks listener on 127.0.0.1:9050
Sep 04 01:43:29.460 [Notice] Opening Control listener on 127.0.0.1:9051
Sep 04 01:43:29.460 [Notice] Parsing GEOIP file.
Sep 04 01:43:32.474 [Debug] conn_read_callback(): socket 1660 wants to read.
Sep 04 01:43:32.474 [Debug] conn_read_callback(): socket 1660 wants to read.
Sep 04 01:43:32.474 [Debug] conn_read_callback(): socket 1660 wants to read.
Sep 04 01:43:43.430 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 04 01:43:54.446 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 04 01:44:02.477 [Info] circuit_expire_building(): Abandoning circ 0 (state 2:connecting to server, purpose 5)
Sep 04 01:44:02.477 [Info] exit circ (length 1, exit 4A0CCD2DDC7995083D73F5D667100C8A5831F16D): $4A0CCD2DDC7995083D73F5D667100C8A5831F16D(closed)
Sep 04 01:44:02.477 [Info] connection_ap_fail_onehop(): Closing one-hop stream to '$4A0CCD2DDC7995083D73F5D667100C8A5831F16D/82.94.251.206' because the OR conn just failed.
Sep 04 01:44:02.477 [Info] connection_ap_fail_onehop(): Closing one-hop stream to '$4A0CCD2DDC7995083D73F5D667100C8A5831F16D/82.94.251.206' because the OR conn just failed.
Sep 04 01:44:02.477 [Debug] circuit_increment_failure_count(): n_circuit_failures now 1.
Sep 04 01:44:02.477 [Debug] conn_close_if_marked(): Cleaning up connection (fd -1).
Sep 04 01:44:02.477 [Debug] connection_remove(): removing socket -1 (type Socks), n_conns now 8
Sep 04 01:44:02.477 [Info] _connection_free(): Freeing linked Socks connection [waiting for circuit] with 99 bytes on inbuf, 0 on outbuf.
Sep 04 01:44:02.477 [Debug] conn_close_if_marked(): Cleaning up connection (fd -1).
Sep 04 01:44:02.477 [Debug] connection_remove(): removing socket -1 (type Socks), n_conns now 7
Sep 04 01:44:02.477 [Info] _connection_free(): Freeing linked Socks connection [waiting for circuit] with 99 bytes on inbuf, 0 on outbuf.
Sep 04 01:44:02.477 [Debug] conn_read_callback(): socket -1 wants to read.
Sep 04 01:44:02.477 [Info] connection_dir_client_reached_eof(): 'fetch' response not all here, but we're at eof. Closing.
Sep 04 01:44:02.477 [Debug] conn_close_if_marked(): Cleaning up connection (fd -1).
Sep 04 01:44:02.477 [Info] connection_dir_request_failed(): Giving up on directory server at '82.94.251.206'; retrying
Sep 04 01:44:02.477 [Debug] connection_remove(): removing socket -1 (type Directory), n_conns now 6
Sep 04 01:44:02.477 [Info] _connection_free(): Freeing linked Directory connection [client reading] with 0 bytes on inbuf, 0 on outbuf.
Sep 04 01:44:02.477 [Debug] conn_read_callback(): socket -1 wants to read.
Sep 04 01:44:02.487 [Info] connection_dir_client_reached_eof(): 'fetch' response not all here, but we're at eof. Closing.
Sep 04 01:44:02.487 [Debug] conn_close_if_marked(): Cleaning up connection (fd -1).
Sep 04 01:44:02.487 [Info] connection_dir_request_failed(): Giving up on directory server at '82.94.251.206'; retrying
Sep 04 01:44:02.487 [Debug] connection_remove(): removing socket -1 (type Directory), n_conns now 5
Sep 04 01:44:02.487 [Info] _connection_free(): Freeing linked Directory connection [client reading] with 0 bytes on inbuf, 0 on outbuf.
Sep 04 01:44:05.471 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 04 01:44:16.487 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 04 01:44:27.533 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 04 01:44:33.542 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 04 01:44:38.549 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)

re: no need for debug level

The info level log, and notice level logs tell you all you need to know:

"no running bridges known"

i think i have same problem

hi
i am from iran, and i use tor for passing filtering,
from the uprising of people on friday(18 sep) at
first government stop https protocol and tor obviously has stoped,
and now gmail, yahoo and many https services has been back but tor is not working
please help me slove this problem
the vidalia has been stoped at "establishing an encrypted directory connection"
status message

here is my log
Sep 20 19:56:14.937 [Notice] Tor v0.2.1.19. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows "Longhorn" Service Pack 2 [workstation] {terminal services, single user})
Sep 20 19:56:14.937 [Notice] Initialized libevent version 1.4.11-stable using method win32. Good.
Sep 20 19:56:14.938 [Notice] Opening Socks listener on 127.0.0.1:9050
Sep 20 19:56:14.938 [Notice] Opening Control listener on 127.0.0.1:9051
Sep 20 19:56:15.045 [Notice] Parsing GEOIP file.
Sep 20 19:56:18.012 [Notice] Bootstrapped 10%: Finishing handshake with directory server.
Sep 20 19:56:47.990 [Notice] No current certificate known for authority moria1; launching request.
Sep 20 19:56:47.990 [Notice] No current certificate known for authority tor26; launching request.
Sep 20 19:56:47.990 [Notice] No current certificate known for authority dizum; launching request.
Sep 20 19:56:47.990 [Notice] No current certificate known for authority ides; launching request.
Sep 20 19:56:47.991 [Notice] No current certificate known for authority gabelmoo; launching request.
Sep 20 19:56:47.991 [Notice] No current certificate known for authority dannenberg; launching request.
Sep 20 19:58:19.065 [Notice] No current certificate known for authority moria1; launching request.
Sep 20 19:58:19.065 [Notice] No current certificate known for authority tor26; launching request.
Sep 20 19:58:19.065 [Notice] No current certificate known for authority dizum; launching request.
Sep 20 19:58:19.066 [Notice] No current certificate known for authority ides; launching request.
Sep 20 19:58:19.066 [Notice] No current certificate known for authority gabelmoo; launching request.
Sep 20 19:58:19.067 [Notice] No current certificate known for authority dannenberg; launching request.
Sep 20 20:04:25.521 [Notice] No current certificate known for authority moria1; launching request.
Sep 20 20:04:25.521 [Notice] No current certificate known for authority tor26; launching request.
Sep 20 20:04:25.521 [Notice] No current certificate known for authority dizum; launching request.
Sep 20 20:04:25.522 [Notice] No current certificate known for authority ides; launching request.
Sep 20 20:04:25.522 [Notice] No current certificate known for authority gabelmoo; launching request.
Sep 20 20:04:25.522 [Notice] No current certificate known for authority dannenberg; launching request.
Sep 20 20:15:36.221 [Notice] No current certificate known for authority moria1; launching request.
Sep 20 20:15:36.221 [Notice] No current certificate known for authority tor26; launching request.
Sep 20 20:15:36.222 [Notice] No current certificate known for authority dizum; launching request.
Sep 20 20:15:36.222 [Notice] No current certificate known for authority ides; launching request.
Sep 20 20:15:36.222 [Notice] No current certificate known for authority gabelmoo; launching request.
Sep 20 20:15:36.222 [Notice] No current certificate known for authority dannenberg; launching request.

thanks for your time
Mohsen

The tor is blocked in Establishing and encrypted directory conne

Sep 21 20:35:10.988 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:35:21.134 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:35:32.296 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:35:43.457 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:35:54.618 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:35:55.633 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:36:05.779 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:36:16.941 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:36:27.087 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:36:38.249 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:36:49.410 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:36:56.513 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:37:00.571 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:37:11.733 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:37:22.894 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:37:33.040 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:37:44.202 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:37:55.363 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:37:57.392 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:38:06.524 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:38:17.686 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:38:28.847 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:38:40.008 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:38:51.169 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:38:58.272 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:39:02.331 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:39:13.492 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:39:24.653 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:39:35.815 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:39:46.976 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:39:57.123 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:39:59.152 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:40:08.284 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:40:19.445 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:40:30.606 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:40:41.768 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:40:52.929 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:41:00.032 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:41:03.076 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:41:14.237 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:41:25.398 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:41:36.560 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:41:47.721 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:41:58.882 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:42:01.926 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:42:09.029 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:42:20.190 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:42:31.351 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:42:42.513 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:42:53.674 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:43:02.806 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:43:04.835 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:43:15.997 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:43:26.143 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:43:37.304 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:43:48.466 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:43:59.627 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:44:03.686 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:44:10.788 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:44:21.950 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:44:32.096 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:44:43.273 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:44:54.434 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:45:04.581 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:45:05.596 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:45:16.757 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:45:27.918 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:45:38.065 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:45:49.226 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:46:00.388 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:46:05.461 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:46:11.549 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:46:22.710 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:46:33.871 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:46:44.018 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:46:55.179 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:47:06.341 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:47:06.341 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:47:17.502 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:47:28.663 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:47:39.825 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:47:50.986 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:48:01.132 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:48:07.220 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Sep 21 20:48:12.309 [Información] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)

TOR problem in China

hi, please help me.. i can't connect to Tor Network.. the ff. are the error messages i get..

Sep 25 06:19:30.390 [Notice] Closing old Control listener on 127.0.0.1:9051
Sep 25 06:19:36.656 [Notice] Tor v0.2.1.19. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 2 [workstation] {terminal services, single user})
Sep 25 06:19:36.656 [Notice] Initialized libevent version 1.4.11-stable using method win32. Good.
Sep 25 06:19:36.656 [Notice] Opening Socks listener on 127.0.0.1:9050
Sep 25 06:19:36.718 [Notice] Opening Control listener on 127.0.0.1:1080
Sep 25 06:19:37.093 [Notice] No current certificate known for authority moria1; launching request.
Sep 25 06:19:37.093 [Notice] No current certificate known for authority tor26; launching request.
Sep 25 06:19:37.093 [Notice] No current certificate known for authority dizum; launching request.
Sep 25 06:19:37.093 [Notice] No current certificate known for authority ides; launching request.
Sep 25 06:19:37.093 [Notice] No current certificate known for authority gabelmoo; launching request.
Sep 25 06:19:37.093 [Notice] No current certificate known for authority dannenberg; launching request.
Sep 25 06:19:37.093 [Notice] Bootstrapped 5%: Connecting to directory server.
Sep 25 06:19:37.093 [Notice] I learned some more directory information, but not enough to build a circuit: We have no network-status consensus.
Sep 25 06:19:57.984 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 1; recommendation warn)
Sep 25 06:19:57.984 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 2; recommendation warn)
Sep 25 06:19:57.984 [Notice] No current certificate known for authority moria1; launching request.
Sep 25 06:19:57.984 [Notice] No current certificate known for authority tor26; launching request.
Sep 25 06:19:57.984 [Notice] No current certificate known for authority dizum; launching request.
Sep 25 06:19:57.984 [Notice] No current certificate known for authority ides; launching request.
Sep 25 06:19:57.984 [Notice] No current certificate known for authority gabelmoo; launching request.
Sep 25 06:19:58.000 [Notice] No current certificate known for authority dannenberg; launching request.
Sep 25 06:21:05.562 [Notice] Tor v0.2.1.19. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 2 [workstation] {terminal services, single user})
Sep 25 06:21:05.562 [Notice] Initialized libevent version 1.4.11-stable using method win32. Good.
Sep 25 06:21:05.578 [Notice] Opening Socks listener on 127.0.0.1:9050
Sep 25 06:21:05.578 [Notice] Opening Control listener on 127.0.0.1:9051
Sep 25 06:21:26.968 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 1; recommendation warn)
Sep 25 06:21:26.984 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 2; recommendation warn)
Sep 25 06:21:27.000 [Notice] No current certificate known for authority moria1; launching request.
Sep 25 06:21:27.000 [Notice] No current certificate known for authority tor26; launching request.
Sep 25 06:21:27.000 [Notice] No current certificate known for authority dizum; launching request.
Sep 25 06:21:27.000 [Notice] No current certificate known for authority ides; launching request.
Sep 25 06:21:27.000 [Notice] No current certificate known for authority gabelmoo; launching request.
Sep 25 06:21:27.000 [Notice] No current certificate known for authority dannenberg; launching request.
Sep 25 06:21:47.984 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 3; recommendation warn)
Sep 25 06:21:48.000 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 4; recommendation warn)
Sep 25 06:23:08.000 [Notice] No current certificate known for authority moria1; launching request.
Sep 25 06:23:08.015 [Notice] No current certificate known for authority tor26; launching request.
Sep 25 06:23:08.031 [Notice] No current certificate known for authority dizum; launching request.
Sep 25 06:23:08.031 [Notice] No current certificate known for authority ides; launching request.
Sep 25 06:23:08.031 [Notice] No current certificate known for authority gabelmoo; launching request.
Sep 25 06:23:08.031 [Notice] No current certificate known for authority dannenberg; launching request.
Sep 25 06:23:28.984 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 5; recommendation warn)
Sep 25 06:29:14.000 [Notice] No current certificate known for authority moria1; launching request.
Sep 25 06:29:14.015 [Notice] No current certificate known for authority tor26; launching request.
Sep 25 06:29:14.015 [Notice] No current certificate known for authority dizum; launching request.
Sep 25 06:29:14.015 [Notice] No current certificate known for authority ides; launching request.
Sep 25 06:29:14.015 [Notice] No current certificate known for authority gabelmoo; launching request.
Sep 25 06:29:14.015 [Notice] No current certificate known for authority dannenberg; launching request.
Sep 25 06:29:34.921 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 6; recommendation warn)
Sep 25 06:29:35.015 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 7; recommendation warn)

connecting to a relay directory failed

九月 25 09:27:04.187 [注意] No current certificate known for authority tor26; launching request.
九月 25 09:27:04.187 [注意] No current certificate known for authority dizum; launching request.
九月 25 09:27:04.187 [注意] No current certificate known for authority ides; launching request.
九月 25 09:27:04.187 [注意] No current certificate known for authority gabelmoo; launching request.
九月 25 09:27:04.187 [注意] No current certificate known for authority dannenberg; launching request.
九月 25 09:27:25.031 [警告] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 5; recommendation warn)
九月 25 09:27:25.031 [警告] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 6; recommendation warn)
九月 25 09:29:52.468 [注意] Tor v0.2.1.19. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 3 [workstation] {terminal services, single user})
九月 25 09:29:52.468 [注意] Initialized libevent version 1.4.11-stable using method win32. Good.
九月 25 09:29:52.468 [注意] Opening Socks listener on 127.0.0.1:9050
九月 25 09:29:52.468 [注意] Opening Control listener on 127.0.0.1:9051
九月 25 09:29:52.468 [注意] Parsing GEOIP file.
九月 25 09:30:15.312 [警告] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 1; recommendation warn)
九月 25 09:30:15.312 [注意] No current certificate known for authority moria1; launching request.
九月 25 09:30:15.312 [注意] No current certificate known for authority tor26; launching request.
九月 25 09:30:15.312 [注意] No current certificate known for authority dizum; launching request.
九月 25 09:30:15.312 [注意] No current certificate known for authority ides; launching request.
九月 25 09:30:15.312 [注意] No current certificate known for authority gabelmoo; launching request.
九月 25 09:30:15.312 [注意] No current certificate known for authority dannenberg; launching request.
九月 25 09:30:15.421 [警告] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 2; recommendation warn)
九月 25 09:30:36.437 [警告] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 3; recommendation warn)
九月 25 09:30:36.640 [警告] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 4; recommendation warn)
九月 25 09:31:56.453 [注意] No current certificate known for authority moria1; launching request.
九月 25 09:31:56.453 [注意] No current certificate known for authority tor26; launching request.
九月 25 09:31:56.453 [注意] No current certificate known for authority dizum; launching request.
九月 25 09:31:56.453 [注意] No current certificate known for authority ides; launching request.
九月 25 09:31:56.453 [注意] No current certificate known for authority gabelmoo; launching request.
九月 25 09:31:56.453 [注意] No current certificate known for authority dannenberg; launching request.
九月 25 09:32:17.328 [警告] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 5; recommendation warn)
九月 25 09:38:02.453 [注意] No current certificate known for authority moria1; launching request.
九月 25 09:38:02.453 [注意] No current certificate known for authority tor26; launching request.
九月 25 09:38:02.453 [注意] No current certificate known for authority dizum; launching request.
九月 25 09:38:02.453 [注意] No current certificate known for authority ides; launching request.
九月 25 09:38:02.453 [注意] No current certificate known for authority gabelmoo; launching request.
九月 25 09:38:02.453 [注意] No current certificate known for authority dannenberg; launching request.
九月 25 09:38:23.453 [警告] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 6; recommendation warn)
九月 25 09:49:13.453 [注意] No current certificate known for authority moria1; launching request.
九月 25 09:49:13.453 [注意] No current certificate known for authority tor26; launching request.
九月 25 09:49:13.453 [注意] No current certificate known for authority dizum; launching request.
九月 25 09:49:13.453 [注意] No current certificate known for authority ides; launching request.
九月 25 09:49:13.453 [注意] No current certificate known for authority gabelmoo; launching request.
九月 25 09:49:13.453 [注意] No current certificate known for authority dannenberg; launching request.
九月 25 09:49:34.375 [警告] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 7; recommendation warn)
九月 25 09:49:34.375 [警告] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 8; recommendation warn)
九月 25 09:52:47.515 [注意] Application request when we're believed to be offline. Optimistically trying directory fetches again.
九月 25 09:53:08.578 [警告] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 9; recommendation warn)
九月 25 09:53:29.593 [警告] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 10; recommendation warn)
九月 25 09:54:47.453 [注意] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
九月 25 09:55:07.453 [注意] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
九月 25 09:55:40.312 [警告] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 11; recommendation warn)
How to solve problems

The same problem

Hi all people....
I have the same problem.. "No current certificate known for authority xxxxxx launching request".
And I dont know what to do...

Anybody who knows HELP UUUUUUUS!!

Thank you a lot!

I can't be a Tor Bridge Relay in China.

Now it is very hard to connect to Tor Network in China.
Once i can connect, i hope to be a Tor Bridge Relay, to help other people can connect to Tor.

I have set Vidalia/Sharing to 'Help censored user reach the Tor network'.
But my log tell me, i don't config the firewall well.
I wonder i have added those ports on my WinXP SP3 Firewall Exceptions already,
but the problem is continue.
i am sure that there is no other firewall software in my computer.

Does china block me from become a Tor Relay?
Here is the Log (I modifed my IP )
------------------
Sept 25 15:27:15.953 [Notice] We're missing a certificate from authority with signing key B7A209B31ACDD633258D0F07715482BD04F88F4F: launching request.
Sept 25 15:44:58.218 [Warning] Your server (221.175.XXX.XXX:443) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
Sept 25 15:44:58.218 [Warning] Your server (221.175.XXX.XXX:9030) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
.
.
.
Sept 25 19:04:58.171 [Warning] Your server (221.175.XXX.XXX:443) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
Sept 25 19:04:58.171 [Warning] Your server (221.175.XXX.XXX:9030) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.

Opps, i just realize

Opps, i just realize that
Tor bundle browser version which i am using is out-date.
because google link me to
http://sedvblmbog.tudasnich.de/download.html.en

but latest version is at
http://sedvblmbog.tudasnich.de/easy-download.html.en
i will try to download new version and see if the problem has been solved.

it seem both is newest version

it seem both is newest version,
the number is just tell it is stable or un-stable version.

Today i still can connect to Tor.
but Becoming Tor Relay problem still continue.

Does anyone know how to self-check as i wish (not to wait for 20 min)?
so i can test immediately if i re-config my firewall well.
or any idea how to track the problem?

i can't connect to Tor Network in china.help me please!

i can't connect to Tor Network.here are the error messsages:
九月 27 13:10:31.977 [注意] No current certificate known for authority dannenberg; launching request.
九月 27 13:10:52.997 [注意] While fetching directory info, no running dirservers known. Will try again later. (purpose 5)
九月 27 13:12:13.383 [注意] No current certificate known for authority moria1; launching request.
九月 27 13:12:13.383 [注意] No current certificate known for authority tor26; launching request.
九月 27 13:12:13.383 [注意] No current certificate known for authority dizum; launching request.
九月 27 13:12:13.383 [注意] No current certificate known for authority ides; launching request.
九月 27 13:12:13.383 [注意] No current certificate known for authority gabelmoo; launching request.
九月 27 13:12:13.383 [注意] No current certificate known for authority dannenberg; launching request.
九月 27 13:12:43.536 [注意] Your DNS provider gave an answer for "s3nkqw4vs.invalid", which is not supposed to exist. Apparently they are hijacking DNS failures. Trying to correct for this. We've noticed 1 possibly bad address so far.
九月 27 13:12:44.728 [注意] Your DNS provider has given "59.37.71.87" as an answer for 6 different invalid addresses. Apparently they are hijacking DNS failures. I'll try to correct for this by treating future occurrences of "59.37.71.87" as 'not found'.
九月 27 13:18:19.940 [注意] No current certificate known for authority moria1; launching request.
九月 27 13:18:19.940 [注意] No current certificate known for authority tor26; launching request.
九月 27 13:18:19.940 [注意] No current certificate known for authority dizum; launching request.
九月 27 13:18:19.940 [注意] No current certificate known for authority ides; launching request.
九月 27 13:18:19.940 [注意] No current certificate known for authority gabelmoo; launching request.
九月 27 13:18:19.940 [注意] No current certificate known for authority dannenberg; launching request.
九月 27 13:18:45.987 [注意] Interrupt: will shut down in 30 seconds. Interrupt again to exit now.
九月 27 13:18:50.023 [注意] Tor v0.2.1.19. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 3 [workstation] {terminal services, single user})
九月 27 13:18:50.023 [注意] Your ContactInfo config option is not set. Please consider setting it, so we can contact you if your server is misconfigured or something else goes wrong.
九月 27 13:18:50.023 [注意] Initialized libevent version 1.4.11-stable using method win32. Good.
九月 27 13:18:50.023 [注意] Opening OR listener on 0.0.0.0:9001
九月 27 13:18:50.023 [注意] Opening Directory listener on 0.0.0.0:9030
九月 27 13:18:50.023 [注意] Opening Socks listener on 127.0.0.1:9050
九月 27 13:18:50.023 [注意] Opening Control listener on 127.0.0.1:9051
九月 27 13:19:15.119 [注意] No current certificate known for authority moria1; launching request.
九月 27 13:19:15.149 [注意] No current certificate known for authority tor26; launching request.
九月 27 13:19:15.149 [注意] No current certificate known for authority dizum; launching request.
九月 27 13:19:15.149 [注意] No current certificate known for authority ides; launching request.
九月 27 13:19:15.149 [注意] No current certificate known for authority gabelmoo; launching request.
九月 27 13:19:15.149 [注意] No current certificate known for authority dannenberg; launching request.
九月 27 13:19:57.079 [注意] While fetching directory info, no running dirservers known. Will try again later. (purpose 5)
九月 27 13:20:22.436 [注意] Your DNS provider gave an answer for "zm2q.invalid", which is not supposed to exist. Apparently they are hijacking DNS failures. Trying to correct for this. We've noticed 1 possibly bad address so far.
九月 27 13:20:56.405 [注意] No current certificate known for authority moria1; launching request.
九月 27 13:20:56.405 [注意] No current certificate known for authority tor26; launching request.
九月 27 13:20:56.405 [注意] No current certificate known for authority dizum; launching request.
九月 27 13:20:56.405 [注意] No current certificate known for authority ides; launching request.
九月 27 13:20:56.405 [注意] No current certificate known for authority gabelmoo; launching request.
九月 27 13:20:56.405 [注意] No current certificate known for authority dannenberg; launching request.
九月 27 13:27:02.952 [注意] No current certificate known for authority moria1; launching request.
九月 27 13:27:02.952 [注意] No current certificate known for authority tor26; launching request.
九月 27 13:27:02.952 [注意] No current certificate known for authority dizum; launching request.
九月 27 13:27:02.952 [注意] No current certificate known for authority ides; launching request.
九月 27 13:27:02.952 [注意] No current certificate known for authority gabelmoo; launching request.
九月 27 13:27:02.962 [注意] No current certificate known for authority dannenberg; launching request.
九月 27 13:38:13.987 [注意] No current certificate known for authority moria1; launching request.
九月 27 13:38:13.987 [注意] No current certificate known for authority tor26; launching request.
九月 27 13:38:13.987 [注意] No current certificate known for authority dizum; launching request.
九月 27 13:38:13.987 [注意] No current certificate known for authority ides; launching request.
九月 27 13:38:13.987 [注意] No current certificate known for authority gabelmoo; launching request.
九月 27 13:38:13.997 [注意] No current certificate known for authority dannenberg; launching request.
how to solve the problem?
thanks!

Clock Problem

I don´t speak english. how fix that?

sep 29 22:08:17.718 [Advertencia] Received directory with skewed time (server '216.224.124.114:9090'): It seems that our clock is behind by 23 hours, 59 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings.

sep 29 22:08:24.250 [Advertencia] Our clock is 23 hours, 51 minutes behind the time published in the consensus network status document (2009-10-01 01:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!

PLEASE I NEED HELP!!!

中国的朋友们，这是

中国的朋友们，这是天朝发威了，防火墙大发威了。
期待强人升级，早日突破封锁。

Help!! Problem Bootstrapping

Hihi. I have some problems running Tor.. There's a problem bootstrapping. any ideas how to get round this? Many thanks in advance!!

Oct 20 10:10:41.881 [Notice] Tor v0.2.1.19. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 3 [workstation] {terminal services, single user})
Oct 20 10:10:41.881 [Notice] Initialized libevent version 1.4.12-stable using method win32. Good.
Oct 20 10:10:41.897 [Notice] Opening Socks listener on 127.0.0.1:9050
Oct 20 10:10:41.897 [Notice] Opening Control listener on 127.0.0.1:9051
Oct 20 10:11:06.298 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 1; recommendation warn)
Oct 20 10:11:06.519 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 2; recommendation warn)
Oct 20 10:11:06.519 [Notice] No current certificate known for authority moria1; launching request.
Oct 20 10:11:06.519 [Notice] No current certificate known for authority tor26; launching request.
Oct 20 10:11:06.519 [Notice] No current certificate known for authority dizum; launching request.
Oct 20 10:11:06.519 [Notice] No current certificate known for authority ides; launching request.
Oct 20 10:11:06.519 [Notice] No current certificate known for authority gabelmoo; launching request.
Oct 20 10:11:06.519 [Notice] No current certificate known for authority dannenberg; launching request.
Oct 20 10:11:27.486 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 3; recommendation warn)
Oct 20 10:11:27.817 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 4; recommendation warn)
Oct 20 10:12:47.779 [Notice] No current certificate known for authority moria1; launching request.
Oct 20 10:12:47.779 [Notice] No current certificate known for authority tor26; launching request.
Oct 20 10:12:47.779 [Notice] No current certificate known for authority dizum; launching request.
Oct 20 10:12:47.779 [Notice] No current certificate known for authority ides; launching request.
Oct 20 10:12:47.779 [Notice] No current certificate known for authority gabelmoo; launching request.
Oct 20 10:12:47.779 [Notice] No current certificate known for authority dannenberg; launching request.
Oct 20 10:13:08.966 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 5; recommendation warn)
Oct 20 10:18:53.673 [Notice] No current certificate known for authority moria1; launching request.
Oct 20 10:18:53.673 [Notice] No current certificate known for authority tor26; launching request.
Oct 20 10:18:53.673 [Notice] No current certificate known for authority dizum; launching request.
Oct 20 10:18:53.673 [Notice] No current certificate known for authority ides; launching request.
Oct 20 10:18:53.673 [Notice] No current certificate known for authority gabelmoo; launching request.
Oct 20 10:18:53.673 [Notice] No current certificate known for authority dannenberg; launching request.
Oct 20 10:19:14.846 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 6; recommendation warn)
Oct 20 10:19:14.846 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 7; recommendation warn)

http://www.cqun.com/2009/10/t

http://www.cqun.com/2009/10/tor-connecting-to-relay-directory.html

My tor was working

My tor was working perfectly, but now the company stopped direct connect and we connects to Proxy server. I setup the proxy parameters but still not working any help

Nov 12 08:14:48.310 [Warning] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 8; recommendation warn)

one week ago,i still can

one week ago,i still can connect to the tor network,but now,i can't.OH,great China, great CCP

Tor Don't start

Hello,

I have this problem.

Tor button does not appear on my browser.Everything is installed.

Could you please help me?

Thank you.

Tor will not connect

Hi
I'm in Oman which blocks sites like Skype, Tor, etc. I've tried inserting several bridges, but Vidalia never connects. The status stops about 1/3 way through with the message "establishing an encrypted directory connection failed (done)"
The log shows:
Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE;"
I'm using PortableTor - Portable Vidalia Bundle - Version 0.2.1.19, but have tried several other versions as well, with the same result.
Thanks for any help you can give.

Tor will not connect if you get the above message

It all means that your Internet service provider has blocked it..........
we are still working on it to over come

If Comcast is your ISP, and

If Comcast is your ISP, and you are receiving the "Apparently they are hijacking DNS failures" error, you can follow the directions linked below to turn off "hijacking."

http://dns-opt-out.comcast.net/help-index.php

Hi I have Tor running on mac

Hi I have Tor running on mac osx 10.5.8 & been running fine for a long time now, just today I started to get no connection to the TOR network here is my error messages from the message log:
Jan 22 12:58:58.881 [Notice] Tor v0.2.1.22. This is experimental software. Do not rely on it for strong anonymity. (Running on Darwin i386)
Jan 22 12:58:58.882 [Notice] Initialized libevent version 1.4.13-stable using method kqueue. Good.
Jan 22 12:58:58.882 [Notice] Opening Socks listener on 127.0.0.1:9050
Jan 22 12:58:58.883 [Notice] Opening Control listener on 127.0.0.1:9051
Jan 22 12:58:59.915 [Warning] TLS error: unexpected close while renegotiating
Jan 22 12:58:59.916 [Notice] We're missing a certificate from authority with signing key B7A209B31ACDD633258D0F07715482BD04F88F4F: launching request.
Jan 22 12:58:59.916 [Notice] We're missing a certificate from authority with signing key 665711AF821C459DC59A8491FAD1B9D7A7800ECF: launching request.
Jan 22 12:58:59.916 [Notice] We're missing a certificate from authority with signing key 6584DF098CFC68ACBF5E551532C8A58674586820: launching request.
Jan 22 12:59:00.512 [Warning] TLS error: unexpected close while renegotiating

Any Help please??

thanks

Same thing happened with me

Same thing happened with me too, I was wondering if it might have anything to do with the Security Update that was downloaded from Apple the day before?

Same here. Worked fine until

Same here. Worked fine until I loaded the Apple security update and threafter it produced the error message 'vidalia establishing an encrypted directory connection (done) failed'

Any suggestions?

I am having the exact same

I am having the exact same problem. Running Tor on Mac OS 10.6.2.

Exact same problem here on

Exact same problem here on Mac OS 10.6.2.

I also am having issues with

I also am having issues with tor after loading the apple security update.

Here is the contents of my Message Log:
Jan 24 23:54:03.817 [Notice] Tor v0.2.1.22. This is experimental software. Do not rely on it for strong anonymity. (Running on Darwin i386)
Jan 24 23:54:03.818 [Notice] Initialized libevent version 1.4.13-stable using method kqueue. Good.
Jan 24 23:54:03.818 [Notice] Opening Socks listener on 127.0.0.1:9050
Jan 24 23:54:03.819 [Notice] Opening Control listener on 127.0.0.1:9051
Jan 24 23:54:05.336 [Warning] TLS error: unexpected close while renegotiating
Jan 24 23:54:05.337 [Notice] We're missing a certificate from authority with signing key B7A209B31ACDD633258D0F07715482BD04F88F4F: launching request.
Jan 24 23:54:05.337 [Notice] We're missing a certificate from authority with signing key 665711AF821C459DC59A8491FAD1B9D7A7800ECF: launching request.
Jan 24 23:54:05.337 [Notice] We're missing a certificate from authority with signing key 6584DF098CFC68ACBF5E551532C8A58674586820: launching request.
Jan 24 23:54:06.336 [Warning] TLS error: unexpected close while renegotiating
Jan 24 23:54:38.836 [Notice] Renaming old configuration file to "/Users/none/Library/Vidalia/torrc.orig.1"
Jan 24 23:55:06.016 [Notice] We're missing a certificate from authority with signing key B7A209B31ACDD633258D0F07715482BD04F88F4F: launching request.
Jan 24 23:55:06.017 [Notice] We're missing a certificate from authority with signing key 665711AF821C459DC59A8491FAD1B9D7A7800ECF: launching request.
Jan 24 23:55:06.017 [Notice] We're missing a certificate from authority with signing key 6584DF098CFC68ACBF5E551532C8A58674586820: launching request.
Jan 24 23:55:06.193 [Warning] TLS error: unexpected close while renegotiating
Jan 24 23:58:02.944 [Notice] We're missing a certificate from authority with signing key B7A209B31ACDD633258D0F07715482BD04F88F4F: launching request.
Jan 24 23:58:02.945 [Notice] We're missing a certificate from authority with signing key 665711AF821C459DC59A8491FAD1B9D7A7800ECF: launching request.
Jan 24 23:58:02.946 [Notice] We're missing a certificate from authority with signing key 6584DF098CFC68ACBF5E551532C8A58674586820: launching request.
Jan 24 23:58:03.024 [Notice] Bootstrapped 10%: Finishing handshake with directory server.
Jan 24 23:58:03.240 [Warning] TLS error: unexpected close while renegotiating
Jan 24 23:59:34.955 [Notice] We're missing a certificate from authority with signing key B7A209B31ACDD633258D0F07715482BD04F88F4F: launching request.
Jan 24 23:59:34.956 [Notice] We're missing a certificate from authority with signing key 665711AF821C459DC59A8491FAD1B9D7A7800ECF: launching request.
Jan 24 23:59:34.956 [Notice] We're missing a certificate from authority with signing key 6584DF098CFC68ACBF5E551532C8A58674586820: launching request.
Jan 24 23:59:35.454 [Warning] TLS error: unexpected close while renegotiating

having the same problem

Having the same problem

Having the same problem after latest Mac OSX security update.

me too

I'm also having a problem

I'm also having a problem after loading the security update. Any ideas?

I too am having the same

I too am having the same problem with Mac OS X version 10.6.2. Does anyone know of a way to manually correct it?

The problem on Mac OS X Snow

The problem on Mac OS X Snow Leopard 10.6.2 is from a bundled security update affecting the Mac implementation of OpenSSH, the program that is used to create secure connections to peers on the Tor network. The only known work-around involves installing the correct libraries from MacPorts and compiling Tor to use those rather than the default mac ones. Then one would have to point the Vidalia configuration to the newly compiled Tor. Several people have reported that this works, but it is certainly more technically demanding. The details can be found here: https://ocewjwkdco.tudasnich.de/blog/new-stable-released-tor-02121 Look about 3/4's of the way down the page.

The problem on Mac OS X Snow

Thank you, I will try this

Thank you, I will try this and I will report if it works.

I am using Vidalia version

I am using Vidalia version 0.2.6. I have set the proxy and bridge (because my ISP blocks connections to the TOR network). Unfortunately, I am getting the following status:
"Connection to a relay directory failed (no route to host)"...
............................................................................................................................
Furthermore, the message log shows the following:
............................................................................................................................
Jan 28 11:43:18.207 [Notice] Tor v0.2.1.21. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows "Longhorn" Service Pack 2 [workstation] {personal} {terminal services, single user})
Jan 28 11:43:18.208 [Notice] Initialized libevent version 1.4.12-stable using method win32. Good.
Jan 28 11:43:18.208 [Notice] Opening Socks listener on 127.0.0.1:9050
Jan 28 11:43:18.208 [Notice] Opening Control listener on 127.0.0.1:9051
Jan 28 11:43:18.208 [Notice] Parsing GEOIP file.
Jan 28 11:43:41.919 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 1; recommendation warn)
Jan 28 11:43:41.942 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 2; recommendation warn)
Jan 28 11:43:41.944 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 3; recommendation warn)
............................................................................................................................
Can anybody help me please to run Vidalia as a client?

Any one can help, i've just

Any one can help, i've just installed vidalia and status shows Establishing an encrypted directory connection for 20mins

Feb 25 00:50:57.747 [Notice] Tor v0.2.1.22. This is experimental software. Do not rely on it for strong anonymity. (Running on Darwin i386)
Feb 25 00:50:57.747 [Notice] Initialized libevent version 1.4.13-stable using method kqueue. Good.
Feb 25 00:50:57.748 [Notice] Opening Socks listener on 127.0.0.1:9050
Feb 25 00:50:57.748 [Notice] Opening Control listener on 127.0.0.1:9051
Feb 25 00:51:03.158 [Notice] Bootstrapped 10%: Finishing handshake with directory server.
Feb 25 00:51:04.549 [Warning] TLS error: unexpected close while renegotiating
Feb 25 00:51:04.551 [Notice] No current certificate known for authority moria1; launching request.
Feb 25 00:51:04.551 [Notice] No current certificate known for authority tor26; launching request.
Feb 25 00:51:04.552 [Notice] No current certificate known for authority dizum; launching request.
Feb 25 00:51:04.552 [Notice] No current certificate known for authority ides; launching request.
Feb 25 00:51:04.552 [Notice] No current certificate known for authority gabelmoo; launching request.
Feb 25 00:51:04.553 [Notice] No current certificate known for authority dannenberg; launching request.
Feb 25 00:51:04.553 [Notice] No current certificate known for authority urras; launching request.
Feb 25 00:51:05.702 [Warning] TLS error: unexpected close while renegotiating
Feb 25 00:53:04.839 [Notice] No current certificate known for authority moria1; launching request.
Feb 25 00:53:04.840 [Notice] No current certificate known for authority tor26; launching request.
Feb 25 00:53:04.840 [Notice] No current certificate known for authority dizum; launching request.
Feb 25 00:53:04.841 [Notice] No current certificate known for authority ides; launching request.
Feb 25 00:53:04.841 [Notice] No current certificate known for authority gabelmoo; launching request.
Feb 25 00:53:04.842 [Notice] No current certificate known for authority dannenberg; launching request.
Feb 25 00:53:04.842 [Notice] No current certificate known for authority urras; launching request.
Feb 25 00:53:07.576 [Warning] TLS error: unexpected close while renegotiating
Feb 25 00:58:09.896 [Notice] No current certificate known for authority moria1; launching request.
Feb 25 00:58:09.898 [Notice] No current certificate known for authority tor26; launching request.
Feb 25 00:58:09.899 [Notice] No current certificate known for authority dizum; launching request.
Feb 25 00:58:09.899 [Notice] No current certificate known for authority ides; launching request.
Feb 25 00:58:09.900 [Notice] No current certificate known for authority gabelmoo; launching request.
Feb 25 00:58:09.900 [Notice] No current certificate known for authority dannenberg; launching request.
Feb 25 00:58:09.901 [Notice] No current certificate known for authority urras; launching request.
Feb 25 00:58:13.006 [Warning] TLS error: unexpected close while renegotiating
Feb 25 00:59:17.395 [Warning] TLS error: unexpected close while renegotiating

I used tor for just one day

I used tor for just one day on my pc and it stopped working. This is the message log. please help:

Apr 28 15:20:56.359 [Notice] Tor v0.2.1.25. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 2 [workstation] {terminal services, single user})
Apr 28 15:20:56.468 [Notice] Initialized libevent version 1.4.12-stable using method win32. Good.
Apr 28 15:20:56.468 [Notice] Opening Socks listener on 127.0.0.1:9050
Apr 28 15:20:56.468 [Notice] Opening Control listener on 127.0.0.1:9051
Apr 28 15:20:56.578 [Notice] Parsing GEOIP file.
Apr 28 15:22:01.062 [Notice] No current certificate known for authority moria1; launching request.
Apr 28 15:22:01.062 [Notice] No current certificate known for authority tor26; launching request.
Apr 28 15:22:01.062 [Notice] No current certificate known for authority dizum; launching request.
Apr 28 15:22:01.062 [Notice] No current certificate known for authority ides; launching request.
Apr 28 15:22:01.062 [Notice] No current certificate known for authority gabelmoo; launching request.
Apr 28 15:22:01.062 [Notice] No current certificate known for authority dannenberg; launching request.
Apr 28 15:22:01.062 [Notice] No current certificate known for authority urras; launching request.
Apr 28 15:27:06.343 [Notice] No current certificate known for authority moria1; launching request.
Apr 28 15:27:06.343 [Notice] No current certificate known for authority tor26; launching request.
Apr 28 15:27:06.343 [Notice] No current certificate known for authority dizum; launching request.
Apr 28 15:27:06.343 [Notice] No current certificate known for authority ides; launching request.
Apr 28 15:27:06.343 [Notice] No current certificate known for authority gabelmoo; launching request.
Apr 28 15:27:06.343 [Notice] No current certificate known for authority dannenberg; launching request.
Apr 28 15:27:06.343 [Notice] No current certificate known for authority urras; launching request.

my email address is hargoon2002@yahoo.com
thanks in anticipation.

here i also just cant

here i also just cant connect to tor,which just shows like this:
[Notice] No current certificate known for authority xxxxx; launching request.
what's wrong?
and the tragedy is before i update to the latest version, i once make it to get linked.

五月 08 19:22:34.468

五月 08 19:22:34.468 [Notice] Tor v0.2.1.25. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 2 [workstation] {terminal services, single user})
五月 08 19:22:34.468 [Notice] Initialized libevent version 1.4.12-stable using method win32. Good.
五月 08 19:22:34.468 [Notice] Opening Socks listener on 127.0.0.1:9050
五月 08 19:22:34.468 [Notice] Opening Control listener on 127.0.0.1:9051
五月 08 19:22:34.468 [Notice] Parsing GEOIP file.
五月 08 19:22:35.625 [Notice] Bootstrapped 10%: Finishing handshake with directory server.
五月 08 19:22:39.593 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 3; recommendation warn)
五月 08 19:22:44.437 [Notice] Tor v0.2.1.25. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 2 [workstation] {terminal services, single user})
五月 08 19:22:44.437 [Notice] Initialized libevent version 1.4.12-stable using method win32. Good.
五月 08 19:22:44.437 [Notice] Opening Socks listener on 127.0.0.1:9050
五月 08 19:22:44.437 [Notice] Opening Control listener on 127.0.0.1:9051
五月 08 19:22:44.437 [Notice] Parsing GEOIP file.
五月 08 19:22:45.421 [Notice] Bootstrapped 10%: Finishing handshake with directory server.
五月 08 19:23:05.890 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 3; recommendation warn)

hi i just downloaded tor

hi i just downloaded tor browser for windows.but it keeps saying no route to tor network.host not found.pls help me email:kingsdezmund@yahoo.com

Even using bridges can't

Even using bridges can't connect to tor still.....

五月 22 13:43:48.902 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 2; recommendation warn)
五月 22 13:43:51.746 [Notice] Tor v0.2.2.10-alpha (git-81b84c0b017267b4). This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 3 [workstation])
五月 22 13:43:51.746 [Notice] Initialized libevent version 1.4.13-stable using method win32. Good.
五月 22 13:43:51.746 [Notice] Opening Socks listener on 127.0.0.1:9050
五月 22 13:43:51.746 [Notice] Opening Control listener on 127.0.0.1:9051
五月 22 13:43:51.855 [Notice] Parsing GEOIP file.
五月 22 13:43:54.481 [Notice] Bootstrapped 10%: Finishing handshake with directory server.
五月 22 13:43:54.684 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 2; recommendation warn)
五月 22 13:43:57.809 [Notice] Tor v0.2.2.10-alpha (git-81b84c0b017267b4). This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 3 [workstation])
五月 22 13:43:57.809 [Notice] Initialized libevent version 1.4.13-stable using method win32. Good.
五月 22 13:43:57.809 [Notice] Opening Socks listener on 127.0.0.1:9050
五月 22 13:43:57.809 [Notice] Opening Control listener on 127.0.0.1:9051
五月 22 13:43:57.919 [Notice] Parsing GEOIP file.
五月 22 13:44:00.560 [Notice] Bootstrapped 10%: Finishing handshake with directory server.
五月 22 13:44:00.763 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 2; recommendation warn)
五月 22 13:44:02.341 [Notice] Tor v0.2.2.10-alpha (git-81b84c0b017267b4). This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 3 [workstation])
五月 22 13:44:02.341 [Notice] Initialized libevent version 1.4.13-stable using method win32. Good.
五月 22 13:44:02.341 [Notice] Opening Socks listener on 127.0.0.1:9050
五月 22 13:44:02.451 [Notice] Opening Control listener on 127.0.0.1:9051
五月 22 13:44:02.451 [Notice] Parsing GEOIP file.
五月 22 13:44:05.060 [Notice] Bootstrapped 10%: Finishing handshake with directory server.
五月 22 13:44:05.232 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 2; recommendation warn)
五月 22 13:44:07.655 [Notice] Tor v0.2.2.10-alpha (git-81b84c0b017267b4). This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 3 [workstation])
五月 22 13:44:07.655 [Notice] Initialized libevent version 1.4.13-stable using method win32. Good.
五月 22 13:44:07.655 [Notice] Opening Socks listener on 127.0.0.1:9050
五月 22 13:44:07.655 [Notice] Opening Control listener on 127.0.0.1:9051
五月 22 13:44:07.764 [Notice] Parsing GEOIP file.
五月 22 13:44:10.436 [Notice] Bootstrapped 10%: Finishing handshake with directory server.
五月 22 13:44:10.624 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 2; recommendation warn)
五月 22 13:45:41.858 [Notice] Tor v0.2.2.10-alpha (git-81b84c0b017267b4). This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 3 [workstation])
五月 22 13:45:41.967 [Notice] Initialized libevent version 1.4.13-stable using method win32. Good.
五月 22 13:45:41.967 [Notice] Opening Socks listener on 127.0.0.1:9050
五月 22 13:45:41.967 [Notice] Opening Control listener on 127.0.0.1:9051
五月 22 13:45:41.967 [Notice] Parsing GEOIP file.
五月 22 13:45:44.624 [Notice] Bootstrapped 10%: Finishing handshake with directory server.
五月 22 13:45:44.843 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 2; recommendation warn)
五月 22 13:50:54.940 [Notice] Tor v0.2.2.10-alpha (git-81b84c0b017267b4). This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 3 [workstation])
五月 22 13:50:54.940 [Notice] Initialized libevent version 1.4.13-stable using method win32. Good.
五月 22 13:50:54.940 [Notice] Opening Socks listener on 127.0.0.1:9050
五月 22 13:50:54.940 [Notice] Opening Control listener on 127.0.0.1:9051
五月 22 13:50:54.940 [Notice] Parsing GEOIP file.
五月 22 13:50:57.581 [Notice] Bootstrapped 10%: Finishing handshake with directory server.
五月 22 13:50:57.769 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 2; recommendation warn)
五月 22 13:51:00.332 [Notice] Tor v0.2.2.10-alpha (git-81b84c0b017267b4). This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 3 [workstation])
五月 22 13:51:00.332 [Notice] Initialized libevent version 1.4.13-stable using method win32. Good.
五月 22 13:51:00.332 [Notice] Opening Socks listener on 127.0.0.1:9050
五月 22 13:51:00.332 [Notice] Opening Control listener on 127.0.0.1:9051
五月 22 13:51:00.332 [Notice] Parsing GEOIP file.
五月 22 13:51:03.145 [Notice] Bootstrapped 10%: Finishing handshake with directory server.
五月 22 13:51:03.332 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 2; recommendation warn)

Pretty pitiful that NOT A

Pretty pitiful that NOT A SINGLE SUGGESTION has been made for this critical problem in over 4 months. although it is clear that the sparkies over at the GFW have made some changes that wipe any references to the TOR network including the certificate references and, of course, ports and IP Address. I can add new bridges every ten minutes and none get recognized, in fact, the error log sees them as been "dangerous" and rejects the connection but NOW it just can't find any bridge routes, period.

Even though this is a bad situation gone catastrophic, you would think that someone on the TOR side of the fence would have something to say about it, even if its just a "like to help but can't... " but not a single response from any one on the TOR team? WTF is that all about?

There are tons of responses

There are tons of responses by us. Our research from within China shows the GFW is blocking ip:port combinations of the public relays and the bridges available by our bridge website. There are comments littered throughout this blog about tor bridges and china.

We're experimenting with other means of access inside china, see http://metrics.torproject.org/bridge-users-graphs.html#china for the results so far. A few thousand people continue to connect without issue.

It's unclear what you mean by "error log sees them as dangerous", that's not something in our code.

It's unclear what you mean by "GFW have made some changes that wipe any references to the TOR network including the certificate references".

phobos, lots of people

phobos,
lots of people under the GFW are pitifully ungreatful bastards, i think it's a bit about the environment here. i haven't been on my facebook account for something like 6 months now, i hope one day i can see it again.

for those who have their freedom limited by choices they make or by accident of birth.

continue to push, continue to fight, take what is yours, take what is right.