OldOOOH
Junior Member | Редактировать | Профиль | Сообщение | Цитировать | Сообщить модератору
10.11.2014 21:53:11.188 [NOTICE] Opening Socks listener on 127.0.0.1:9150
10.11.2014 21:53:11.188 [NOTICE] Renaming old configuration file to "C:\Users\Àëåêñàíäð\Desktop\Tor Browser\Browser\TorBrowser\Data\Tor\torrc.orig.1"
10.11.2014 21:53:12.123 [NOTICE] Bootstrapped 5%: Connecting to directory server
10.11.2014 21:53:12.336 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
10.11.2014 21:53:13.812 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection
10.11.2014 21:53:14.328 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus
10.11.2014 21:53:14.539 [NOTICE] Bootstrapped 25%: Loading networkstatus consensus
10.11.2014 21:53:25.224 [WARN] Received directory with skewed time (server '208.83.223.34:80'): It seems that our clock is behind by 1 hours, 0 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings.
10.11.2014 21:53:25.224 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
10.11.2014 21:53:25.717 [NOTICE] Bootstrapped 40%: Loading authority key certs
10.11.2014 21:53:25.917 [WARN] Received directory with skewed time (server '193.23.244.244:443'): It seems that our clock is behind by 1 hours, 0 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings.
10.11.2014 21:53:25.917 [WARN] Our clock is 6 minutes, 35 seconds behind the time published in the consensus network status document (2014-11-10 18:00:00 UTC). Tor needs an accurate clock to work correctly. Please check your time and date settings!
10.11.2014 21:53:25.917 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
10.11.2014 21:53:33.155 [NOTICE] Delaying directory fetches: No running bridges
10.11.2014 21:53:36.113 [NOTICE] new bridge descriptor 'ndnop2' (fresh): $4C331FA9B3D1D6D8FB0D8FBBF0C259C360D97E6A~ndnop2 at 109.105.109.163
10.11.2014 21:53:36.113 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
10.11.2014 21:53:36.115 [NOTICE] new bridge descriptor 'ndnop0' (fresh): $1E05F577A0EC0213F971D81BF4D86A9E4E8229ED~ndnop0 at 109.105.109.163
10.11.2014 21:53:36.115 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
10.11.2014 21:53:36.549 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
10.11.2014 21:53:39.319 [NOTICE] new bridge descriptor 'LeifEricson' (fresh): $A09D536DD1752D542E1FBB3C9CE4449D51298239~LeifEricson at 83.212.101.3
10.11.2014 21:53:39.319 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
10.11.2014 21:53:39.531 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
10.11.2014 21:53:56.397 [WARN] Proxy Client: unable to connect to 209.141.36.236:45496 ("Connection refused")
10.11.2014 21:53:56.397 [WARN] Proxy Client: unable to connect to 208.79.90.242:35658 ("Connection refused")
10.11.2014 21:55:16.720 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
|
