Tor stuck in 25% Loading networkstatus consensus
I installed the Tor Bridge. When launched, it gets stuck:
Dec 04 10:42:33.943 [notice] Tor 0.3.4.9 running on Linux with Libevent 2.1.8-stable, OpenSSL LibreSSL 2.8.2, Zlib 1.2.8, Liblzma N/A, and Libzstd N/A. Dec 04 10:42:33.944 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Dec 04 10:42:33.944 [notice] Read configuration file "/etc/tor/torrc". Dec 04 10:42:33.947 [notice] Scheduler type KIST has been enabled. Dec 04 10:42:33.947 [notice] Opening Socks listener on 127.0.0.1:9050 Dec 04 10:42:33.000 [notice] Parsing GEOIP IPv4 file /usr/local/share/tor/geoip. Dec 04 10:42:34.000 [notice] Parsing GEOIP IPv6 file /usr/local/share/tor/geoip6. Dec 04 10:42:34.000 [notice] We were built to run on a 64-bit CPU, with OpenSSL 1.0.1 or later, but with a version of OpenSSL that apparently lacks accelerated support for the NIST P-224 and P-256 groups. Building openssl with such support (using the enable-ec_nistp_64_gcc_128 option when configuring it) would make ECDH much faster. Dec 04 10:42:34.000 [notice] Bootstrapped 0%: Starting Dec 04 10:42:34.000 [notice] Starting with guard context "bridges" Dec 04 10:42:34.000 [notice] new bridge descriptor 'huy' (cached): $3E0CFCEE7183970DCC70ABC2D10518BC288BF0DE~huy at 188.8.131.52 Dec 04 10:42:34.000 [notice] Delaying directory fetches: Pluggable transport proxies still configuring Dec 04 10:42:35.000 [notice] Bootstrapped 5%: Connecting to directory server Dec 04 10:42:35.000 [notice] Bootstrapped 10%: Finishing handshake with directory server Dec 04 10:42:35.000 [notice] Bootstrapped 15%: Establishing an encrypted directory connection Dec 04 10:42:35.000 [notice] Bootstrapped 20%: Asking for networkstatus consensus Dec 04 10:42:35.000 [notice] Bootstrapped 25%: Loading networkstatus consensus Dec 04 10:47:39.000 [notice] Delaying directory fetches: No running bridges
My ISP does not block Tor. This problem does not depend on the country, because I tested the Tor client with my bridge in Russia, Germany and the Netherlands. The same problem occurs without using obfs4proxy. I think that in this case it has nothing to do with the time zone.