Why won't Tor Browser connect?

Question

linux

Elementary OS Loki 64bit (Ubuntu 16.04).
Can't start tor browser. The time on the computer is correct, if you try to google errors from the logs, then everyone only advises you to check the accuracy of the time in the operating system .. What could be the problem?
Here is the log:

2016/11/17 18:07:46.600 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2016/11/17 18:07:53.600 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2016/11/17 18:07:53.600 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2016/11/17 18:07:53.600 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
11/17/2016 18:07:53.600 [NOTICE] Opening Socks listener on 127.0.0.1:9150
11/17/2016 18:07:54.000 [NOTICE] Bootstrapped 5%: Connecting to directory server
11/17/2016 18:07:54.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
11/17/2016 18:11:58.800 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection
11/17/2016 18:11:59.000 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus
11/17/2016 19:07:53.700 [NOTICE] Bootstrapped 25%: Loading networkstatus consensus
11/17/2016 19 :07:54.800 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
11/17/2016 7:09:55.100 PM [NOTICE] Bootstrapped 40%: Loading authority key certs 11/17/2016
7:09:55.600 PM [NOTICE] Bootstrapped 45%: Asking for relay descriptors
11/17/2016 7:09:55.600 PM [NOTICE] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7123, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of exit bw = 0% of path bw.)
11/17/2016 7:14:55.200 PM [WARN] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (DONE; DONE; count 10; recommendation warn; host C0F508ADA14AE7EA9F8F6650AF149B8DFC35B598 at 89.187.143.81:443) 11/17/2016
19:14:55.200 [WARN] 10 connections have failed:
11/17/2016 19:14:55 [WARN.2] died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE 11/17/2016
19:14:55.200 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)
2016/11/17 19:14:55.200 [WARN] 1 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN
11/17/2016 19:22:41.400 [WARN] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (DONE; DONE; count 11; recommendation warn; host 2647FCDDA4FB7331A9B67B8D9EE76824239C02E3 at 62.210.81.152:9001) 11/17/2016
19:22:41.400 [WARN] 11 connections have failed:
17.11RN.2016 19:24 died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE 11/17/2016
19:22:41.400 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)
11/17/2016 19:22:41.400 [WARN] 1 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN
11/17/2016 19:22:41.400 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
11/17/2016 7:22:41.400 PM [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2016/11/17 19:22:41.400 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
2016/17/17 19:22:41.400 [NOTICE] Delaying directory fetches: DisableNetwork is set.

Previously put the torus, worked without problems. I tried to put it on Windows, it connected to the network for about 5 minutes, then it started up and worked quietly for a couple of hours, then suddenly the sites stopped opening. After the reboot, it no longer connects to the network, the log seems to be approximately similar, something about SSL. Then I tried to put it under Linux, but I can’t connect to the network for the reasons described above .. Tell me?

Answer 1

The most common reasons for this behavior are:
1) Incorrect time on the equipment (not synchronized).
2) Outdated version of Tor.
3) Tor is being blocked by a firewall on your PC or router.
4) Tor is being blocked by your ISP.
The first, in your case, we dismiss - there is no corresponding message in the logs and you have already checked. The second one, too, I think.
Try to set an item in the Tor settings about blocking or censoring the connection by the provider and play around with the types of transport.