Answer the question
In order to leave comments, you need to log in
Can't connect to the Tor network, why?
Here is the log
1/8/2017 0:40:52.000 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2017/01/8 0:40:52.000 [NOTICE] Opening Socks listener on 127.0.0.1:9150
2017/08/08 0:40:58.800 [NOTICE] Bootstrapped 5%: Connecting to directory server
1/8/2017 0:40:58.800 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
1/8/2017 0:40:59.700 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection
1/8/2017 0:40:59.900 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus
08.01. 2017 0:41:00.200 [NOTICE] new bridge descriptor 'ndnop3' (fresh): $8DFCD8FB3285E855F5A55EDDA35696C743ABFC4E~ndnop3 at 109.105.109.165
01/08/2017 0:41:00.200 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
2017-01-08 0:41:00.900 [NOTICE] new bridge descriptor 'LeifEricson' (fresh): $A09D536DD1752D542E1FBB3C9CE4449D51298239~LeifEricson at 83.212.101.3
01/08/2017 0:41:00.900 learned directory [NOT] to build a circuit: We have no usable consensus.
2017-01-08 0:41:00.900 [NOTICE] new bridge descriptor 'riemann' (fresh): $752CF7825B3B9EA6A98C83AC41F7099D67007EA5~riemann at 198.245.60.50 1/8/2017
0:41:00.900 to build a circuit: We have no usable consensus.
2017/01/08 0:41:01.100 [NOTICE] new bridge descriptor 'noether' (fresh): $7B126FAB960E5AC6A629C729434FF84FB5074EC2~noether at 192.99.11.54 1/8/2017
0:41:01.100 [NOTICE] I learned some more information, but not more information, but not more information to build a circuit: We have no usable consensus.
2017/01/8 0:41:01.400 [NOTICE] Bootstrapped 25%: Loading networkstatus consensus
2017/01/8 0:41:19.800 [WARN] Proxy Client: unable to connect to 154.35.22.9:80 ("general SOCKS server failure")
08.01 .2017 0:41:19.800 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
2017-01-08 0:41:19.800 [WARN] Proxy Client: unable to connect to 154.35. 11/22:2413 ("general SOCKS server failure")
2017/01/08 0:41:59.100 [WARN] Proxy Client: unable to connect to 154.35.22.12:80 ("general SOCKS server failure")
2017/01/08 0:41:59.100 [WARN] Proxy Client: unable to connect to 154.35 .22.10:80 ("general SOCKS server failure")
1/8/2017 0:44:24.200 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
1/8/2017 0:44:24.200 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2017/01/08 0:44:24.200 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
2017/08/08 0:44:24.600 [NOTICE] Delaying directory fetches: DisableNetwork is set.
01/08/2017 0:45:46.700 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
01/08/2017 0:45:46.700 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
01/08/2017 0:45:46.700 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2017/01/08 0:45:46.700 [NOTICE] Opening Socks listener on 127.0.0.1:9150
2017/08/08 0:45:48.500 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
01/08/2017 0:45:48.500 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2017/01/08 0:45:48.500 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
2017/08/08 0:45:48.600 [NOTICE] Delaying directory fetches: DisableNetwork is set.
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question