Hey!

have you tried to download a new Tor browser, and unpack it in a new
folder ?
May be your current Tor Browser is corrupted ?

Let's give a try ;)


Le 03/01/2017 à 17:28, Jason Long a écrit :
> Hello.I use Debian 8.6 amd64 and the last version of TorBrowser.When I run my 
> TorBrowser and like to use "obsf4" or others it show me below error:
> 01/02/2017 19:54:02.500 [NOTICE] DisableNetwork is set. Tor will not make or 
> accept non-control network connections. Shutting down all existing 
> connections. 01/02/2017 19:54:02.500 [NOTICE] DisableNetwork is set. Tor will 
> not make or accept non-control network connections. Shutting down all 
> existing connections. 01/02/2017 19:54:02.500 [NOTICE] DisableNetwork is set. 
> Tor will not make or accept non-control network connections. Shutting down 
> all existing connections. 01/02/2017 19:54:02.500 [NOTICE] Opening Socks 
> listener on 127.0.0.1:9150 01/02/2017 19:54:02.500 [NOTICE] Renaming old 
> configuration file to 
> "/home/jason/Desktop/Tors/tor-browser_en-US/Browser/TorBrowser/Data/Tor/torrc.orig.1"
>  01/02/2017 19:54:05.600 [NOTICE] Bootstrapped 5%: Connecting to directory 
> server 01/02/2017 19:54:05.600 [NOTICE] Bootstrapped 10%: Finishing handshake 
> with directory server 01/02/2017 19:54:06.600 [NOTICE] Bootstrapped 15%: 
> Establishing an encrypted directory connection 01/02/2017 19:54:07.100 
> [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus 01/02/2017 
> 19:54:07.700 [NOTICE] new bridge descriptor 'wisctorbridge03' (fresh): 
> $A17A40775FBD2CA1184BF80BFC330A77ECF9D0E9~wisctorbridge03 at 128.105.214.163 
> 01/02/2017 19:54:07.700 [NOTICE] I learned some more directory information, 
> but not enough to build a circuit: We have no usable consensus. 01/02/2017 
> 19:54:08.400 [NOTICE] new bridge descriptor 'wisctorbridge02' (fresh): 
> $FC562097E1951DCC41B7D7F324D88157119BB56D~wisctorbridge02 at 128.105.214.162 
> 01/02/2017 19:54:08.400 [NOTICE] I learned some more directory information, 
> but not enough to build a circuit: We have no usable consensus. 01/02/2017 
> 19:54:09.600 [NOTICE] Bootstrapped 25%: Loading networkstatus consensus 
> 01/02/2017 19:54:16.200 [NOTICE] I learned some more directory information, 
> but not enough to build a circuit: We have no usable consensus. 01/02/2017 
> 19:54:16.500 [NOTICE] Bootstrapped 40%: Loading authority key certs 
> 01/02/2017 19:54:16.700 [WARN] Our clock is 11 hours, 5 minutes behind the 
> time published in the consensus network status document (2017-01-03 15:00:00 
> UTC).  Tor needs an accurate clock to work correctly. Please check your time 
> and date settings! 01/02/2017 19:54:16.700 [NOTICE] I learned some more 
> directory information, but not enough to build a circuit: We have no recent 
> usable consensus. 01/02/2017 19:54:35.600 [WARN] Proxy Client: unable to 
> connect to 131.252.210.150:8080 ("TTL expired") 01/02/2017 19:55:36.900 
> [WARN] Our clock is 12 hours, 4 minutes behind the time published in the 
> consensus network status document (2017-01-03 16:00:00 UTC).  Tor needs an 
> accurate clock to work correctly. Please check your time and date settings! 
> 01/02/2017 19:55:36.900 [NOTICE] I learned some more directory information, 
> but not enough to build a circuit: We have no recent usable consensus. 
> 01/02/2017 19:56:26.300 [NOTICE] Closing no-longer-configured Socks listener 
> on 127.0.0.1:9150 01/02/2017 19:56:26.300 [NOTICE] DisableNetwork is set. Tor 
> will not make or accept non-control network connections. Shutting down all 
> existing connections. 01/02/2017 19:56:26.300 [NOTICE] Closing old Socks 
> listener on 127.0.0.1:9150 01/02/2017 19:56:26.600 [NOTICE] Delaying 
> directory fetches: DisableNetwork is set. 
>
> Why?
> Thank you.

-- 
Petrusko
C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2 3AE5


Attachment: signature.asc
Description: OpenPGP digital signature

-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

Reply via email to