First and foremost, I am ethnically and biologically Chinese, though I don’t regard myself as a Chinese in anyway whatsoever, the point is I am behind the notorious not-so-great «Great Firewall of China», which censors and blocks accesses to free world websites and restricts freedom of speech and freedom of information—and it’s very good at what it does.
The GFW implements methods like Deep Packet Inspection, Network Black-holing, DNS Spoofing, Quality of Service, TCP reset and TLS attacking, and it can block Tor Network access, the GFW is not to be underestimated.
I used to edit hosts file to gain access to websites like Wikipedia and DeviantArt that are blocked by DNS poisoning only. I am free to access Wikipedia and DeviantArt and other websites blocked by the same technique. But not websites like Google, Quora etc. that are blocked by more advanced technologies (Black-holing, Man-in-the-middle, TCP reset, Deep Packet Inspection). To gain access to latter websites I need to establish encrypted connection to computers outside of the GFW, and this comes often at a cost of money.
I have no money, otherwise I would use Virtual Private Networks like most imbecile mundane masses do, they pay money to make others do the thinking for them so that they don’t need do the thinking themselves. That’s why I use Tor, of course I also use other free proxies like ShadowSocksR, Lantern, V2RayN and Psiphon3, but none of them are as reliable as Tor, however none of them are as slow as Tor either.
Tor used to be my most reliable method of bypassing the GFW and almost never failed. Well, it used to be, up until late October 2020, when it suddenly stops working altogether.
So I keep getting error messages. below are an inexhaustive list of them.
Tor failed to establish a Tor network connection.
Retrieving network status failed ( done — 0.0.2.0:2).
Unable to obtain a bridge from BridgeDB.
NS_ERROR_NET_INTERRUPT
Tor failed to establish a Tor network connection.
Loading relay information failed ( done — 0.0.2.0:2).
Tor failed to establish a Tor network connection.
Retrieving network status failed (TLS_ERROR — 0.0.2.0:2 ).
And before you start, I have already tried all the steps in the picture below long before it stopped functioning, and I tried again and again and just got the same error messages:
I used to use meek-azure to connect to Tor Network and obfs4 was far less reliable than meek-azure somehow.
And I never saw FTE, obfs3 and ScrambleSuit listed in Built-in Bridges drop list, I am sure of it, well I used torbrowser-install-win64-10.0.2_en-US.exe recently before switching to torbrowser-install-10.5a2_en-US.exe, and in these versions there are only obfs4 and meek (and snowflake in 10.5a2). And all of these failed.
Well I gmailed bridges@bridges.torproject.org with «get bridges», «get transport obfs4», and «get ipv6», got the bridges, provided the bridges I know, and they worked, and they worked well, but only the first time, after an hour or so, I don’t know how long, the connections got interrupted while using Tor, and Tor can’t reconnect to the provided bridges. The problem is I can only send a gmail once every 3 hours and I can only get a maximum of 3 bridges with a minimum of 1 bridge in one reply and I have only one gmail account and all the bridges’ ip address have ping round-trip time longer than 250 milliseconds and often time out…
(Well I recently found that I can use https://bridges.torproject.org/bridges?transport=obfs4 to get bridges,
no 3 hour limit like gmail, but the bridges are also far away.)
So here are some logs, I hope you find it relevant and informational.
11/1/20, 06:02:04.886 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
11/1/20, 06:02:04.887 [NOTICE] Opening Socks listener on 127.0.0.1:9150
11/1/20, 06:02:04.887 [NOTICE] Opened Socks listener on 127.0.0.1:9150
11/1/20, 06:02:05.654 [NOTICE] Bridge ‘dktoke’ has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a0c:4d80:42:702::1]:27015) based on the configured Bridge address.
11/1/20, 06:02:05.654 [NOTICE] Bootstrapped 1% (conn_pt): Connecting to pluggable transport
11/1/20, 06:02:05.655 [NOTICE] Bootstrapped 2% (conn_done_pt): Connected to pluggable transport
11/1/20, 06:02:05.833 [NOTICE] Ignoring directory request, since no bridge nodes are available yet.
11/1/20, 06:02:07.434 [NOTICE] Bootstrapped 10% (conn_done): Connected to a relay
11/1/20, 06:02:07.805 [NOTICE] Bootstrapped 14% (handshake): Handshaking with a relay
11/1/20, 06:02:08.540 [NOTICE] Bootstrapped 15% (handshake_done): Handshake with a relay done
11/1/20, 06:02:08.542 [NOTICE] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
11/1/20, 06:02:08.941 [NOTICE] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
11/1/20, 06:02:09.540 [NOTICE] Bridge ‘dktoke’ has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a0c:4d80:42:702::1]:27015) based on the configured Bridge address.
11/1/20, 06:02:10.555 [NOTICE] Bridge ‘dktoke’ has both an IPv4 and an IPv6 address. Will prefer using its IPv4 address (45.145.95.6:27015) based on the configured Bridge address.
11/1/20, 06:02:17.130 [NOTICE] Bootstrapped 50% (loading_descriptors): Loading relay descriptors
11/1/20, 06:02:26.698 [WARN] Proxy Client: unable to connect to 209.148.46.65:443 («general SOCKS server failure»)
11/1/20, 06:02:26.699 [WARN] Proxy Client: unable to connect to 144.217.20.138:80 («general SOCKS server failure»)
11/1/20, 06:02:26.699 [WARN] Proxy Client: unable to connect to 146.57.248.225:22 («general SOCKS server failure»)
11/1/20, 06:02:26.700 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 («general SOCKS server failure»)
11/1/20, 06:02:26.701 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 («general SOCKS server failure»)
11/1/20, 06:02:26.701 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 («general SOCKS server failure»)
11/1/20, 06:02:26.702 [WARN] Proxy Client: unable to connect to 193.11.166.194:27015 («general SOCKS server failure»)
11/1/20, 06:02:26.702 [WARN] Proxy Client: unable to connect to 192.95.36.142:443 («general SOCKS server failure»)
11/1/20, 06:02:26.702 [WARN] Proxy Client: unable to connect to 37.218.245.14:38224 («general SOCKS server failure»)
11/1/20, 06:02:26.703 [WARN] Proxy Client: unable to connect to 193.11.166.194:27020 («general SOCKS server failure»)
11/1/20, 06:02:26.703 [WARN] Proxy Client: unable to connect to 193.11.166.194:27025 («general SOCKS server failure»)
11/1/20, 06:02:26.703 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 («general SOCKS server failure»)
11/1/20, 06:02:29.674 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
11/1/20, 06:02:29.674 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
11/1/20, 06:02:29.842 [WARN] Pluggable Transport process terminated with status code 0
11/1/20, 06:02:30.594 [NOTICE] Delaying directory fetches: DisableNetwork is set.
11/1/20, 06:02:37.717 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
11/1/20, 06:02:37.717 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
11/1/20, 06:02:37.717 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
11/1/20, 06:02:37.717 [NOTICE] Opening Socks listener on 127.0.0.1:9150
11/1/20, 06:02:37.718 [NOTICE] Opened Socks listener on 127.0.0.1:9150
11/1/20, 06:02:40.154 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
11/1/20, 06:02:40.154 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
11/1/20, 06:02:40.154 [WARN] Problem bootstrapping. Stuck at 50% (loading_descriptors): Loading relay descriptors. (DONE; DONE; count 1; recommendation warn; host 97700DFE9F483596DDA6264C4D7DF7641E1E39CE at 0.0.2.0:2)
11/1/20, 06:02:40.154 [WARN] 13 connections have failed:
11/1/20, 06:02:40.154 [WARN] 12 connections died in state handshaking (proxy) with SSL state (No SSL object)
11/1/20, 06:02:40.154 [WARN] 1 connections died in state handshaking (TLS) with SSL state SSLv3/TLS write client hello in HANDSHAKE
11/1/20, 06:02:40.197 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
11/1/20, 06:02:40.832 [WARN] Pluggable Transport process terminated with status code 0
11/1/20, 06:09:49.275 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
11/1/20, 06:09:49.275 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
11/1/20, 06:09:49.275 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
11/1/20, 06:09:49.275 [NOTICE] Opening Socks listener on 127.0.0.1:9150
11/1/20, 06:09:49.275 [NOTICE] Opened Socks listener on 127.0.0.1:9150
11/1/20, 06:09:50.278 [NOTICE] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
11/1/20, 06:09:50.549 [NOTICE] Bootstrapped 76% (ap_conn_pt): Connecting to pluggable transport to build circuits
11/1/20, 06:09:50.550 [NOTICE] Bootstrapped 77% (ap_conn_done_pt): Connected to pluggable transport to build circuits
11/1/20, 06:09:52.570 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
11/1/20, 06:09:52.570 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
11/1/20, 06:09:52.839 [WARN] Pluggable Transport process terminated with status code 0
11/1/20, 06:09:53.354 [NOTICE] Delaying directory fetches: DisableNetwork is set.
I have found Tor BrowserBrowserTorBrowserTorTor.exe but when I type tor and enter in cmd (of course I cd’ed to that directory), there are no responces whatsoever, I tried tor /?, tor /help, tor /h, tor -?, tor -h and tor -help, no responces.
I have found Tor BrowserBrowserTorBrowserTorPluggableTransports directory and there are obfs4proxy.exe and snowflake-client.exe (in 10.5.a2 version), but no fte, scramblesuit and obfs3, how do I get them to use with the latest version and how do I config Tor BrowserBrowserTorBrowserDataTortorrc file to actually use them (as clients, not servers)?
I have found Tor BrowserBrowserTorBrowserDataTorgeoip and geoip6 files which are based on GeoLite2-Country.mmdb on 2019-12-03 and outdated so I updated them. They are now based on 2020-10-27 version of GeoLite2-Country.mmdb.
I want to change Tor Browser ports, are the following correct?
SocksListenAddress 127.0.0.1:9180
SocksPort 9180
ControlPort 9081
How do I change default relays used by Tor Browser? I think they might have been compromised so I want to know the relays and make Tor Browser connect to working relays.
And I read somewhere using uTLS and HTTP/2 transport will make Tor Browser more resistant to GFW, how can I do this?
That’s all, folks. If you can help me, I would be really grateful.
Компьютерный форум
Здесь решают различные задачи сообща. Присоединяйтесь!
Ребята не работает Тор
Модератор: Tim308
Ребята не работает Тор
Сообщение Азамат » 21 июл 2016, 18:34
Ребята не работает Тор
Сообщение 6yHTapb » 21 июл 2016, 18:48
Азамат , там где выбираете мост obfs3, есть кнопка «справка», где указано ровно следующее:
«Если вы не можете подключиться к сети Tor, возможно ваш провайдер (ISP) или иная организация блокирует Tor. Часто эту проблему можно обойти при помощи мостов Tor, не перечисленных в публичных списках, которые сложнее заблокировать.Вы можете воспользоваться готовым сконфигурированным набором адресов мостов, либо получить пользовательский список адресов с помощью одного из следующих методов:
1)В Интернете — Откройте в веб-браузере https://bridges.torproject.org.
2)Через автоответчик электронной почты — Отправьте имейл по адресу bridges@torproject.org со строкой ‘get bridges’ в теле сообщения. Однако чтобы усложнить сбор атакующими адресов всех мостов, от Вас требуется отправить запрос с одного из следующих адресов (в порядке предпочтения)https://www.riseup.net, https://mail.google.com, или https://mail.yahoo.com»
пройдите по адресу https://bridges.torproject.org, нажмите кнопку «просто дайте мне мосты», введите капчу, скопируйте полученные данные в поле для ввода при выделенной радио-кнопке «ввести мосты вручную».
Ребята не работает Тор
Сообщение Азамат » 21 июл 2016, 20:40
Не помогло, вот я скинул журнал или как его, может поможет как нибудь, я не бум бум во всей етой теме
21.07.2016 17:46:49.700 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
21.07.2016 17:46:49.700 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
21.07.2016 17:46:49.700 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
21.07.2016 17:46:49.700 [NOTICE] Opening Socks listener on 127.0.0.1:9150
21.07.2016 17:46:49.700 [NOTICE] Renaming old configuration file to «C:UsersÀçàìàòDesktopTor BrowserBrowserTorBrowserDataTortorrc.orig.1»
21.07.2016 17:46:50.200 [NOTICE] Bootstrapped 5%: Connecting to directory server
21.07.2016 17:46:50.500 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
21.07.2016 17:51:35.900 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
21.07.2016 17:51:35.900 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
21.07.2016 17:51:35.900 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
21.07.2016 17:51:36.200 [NOTICE] Delaying directory fetches: DisableNetwork is set.
21.07.2016 17:51:48.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
21.07.2016 17:51:48.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
21.07.2016 17:51:48.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
21.07.2016 17:51:48.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150
21.07.2016 17:52:28.400 [WARN] Proxy Client: unable to connect to 83.212.101.3:80 («general SOCKS server failure»)
21.07.2016 17:52:29.700 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (IOERROR; IOERROR; count 6; recommendation warn; host AF9F66B7B04F8FF6F32D455F05135250A16543C9 at 169.229.59.75:46328)
21.07.2016 17:52:29.700 [WARN] 7 connections have failed:
21.07.2016 17:52:29.700 [WARN] 3 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN
21.07.2016 17:52:29.700 [WARN] 3 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE
21.07.2016 17:52:29.700 [WARN] 1 connections died in state handshaking (proxy) with SSL state (No SSL object)
21.07.2016 17:52:32.700 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
21.07.2016 17:52:32.700 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
21.07.2016 17:52:32.700 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
21.07.2016 17:52:41.200 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
21.07.2016 17:52:41.200 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
21.07.2016 17:52:41.200 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
21.07.2016 17:52:41.200 [NOTICE] Opening Socks listener on 127.0.0.1:9150
21.07.2016 17:52:47.900 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection
21.07.2016 17:52:48.100 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus
21.07.2016 17:52:48.400 [NOTICE] new bridge descriptor ‘ndnop5’ (fresh): $BBB28DF0F201E706BE564EFE690FE9577DD8386D
ndnop5 at 109.105.109.147
21.07.2016 17:52:48.400 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
21.07.2016 17:52:48.600 [NOTICE] new bridge descriptor ‘ndnop3’ (fresh): $8DFCD8FB3285E855F5A55EDDA35696C743ABFC4E
ndnop3 at 109.105.109.165
21.07.2016 17:52:48.600 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
21.07.2016 17:52:49.000 [NOTICE] new bridge descriptor ‘riemann’ (fresh): $752CF7825B3B9EA6A98C83AC41F7099D67007EA5
riemann at 198.245.60.50
21.07.2016 17:52:49.000 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
21.07.2016 17:52:49.000 [NOTICE] new bridge descriptor ‘noether’ (fresh): $7B126FAB960E5AC6A629C729434FF84FB5074EC2
noether at 192.99.11.54
21.07.2016 17:52:49.000 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
21.07.2016 17:52:49.400 [NOTICE] Bootstrapped 25%: Loading networkstatus consensus
21.07.2016 17:53:08.200 [WARN] Proxy Client: unable to connect to 83.212.101.3:41213 («general SOCKS server failure»)
21.07.2016 17:53:08.200 [WARN] Proxy Client: unable to connect to 104.131.108.182:56880 («general SOCKS server failure»)
21.07.2016 17:53:08.300 [WARN] Proxy Client: unable to connect to 154.35.22.11:443 («general SOCKS server failure»)
21.07.2016 17:53:40.800 [WARN] Proxy Client: unable to connect to 154.35.22.10:80 («general SOCKS server failure»)
21.07.2016 17:53:42.900 [WARN] Proxy Client: unable to connect to 154.35.22.9:80 («general SOCKS server failure»)
21.07.2016 17:53:42.900 [WARN] Proxy Client: unable to connect to 154.35.22.12:80 («general SOCKS server failure»)
21.07.2016 18:07:49.900 [NOTICE] new bridge descriptor ‘Azadi’ (fresh): $FE7840FE1E21FE0A0639ED176EDA00A3ECA1E34D
Azadi at 154.35.22.13
21.07.2016 18:07:49.900 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
21.07.2016 18:08:08.200 [WARN] Proxy Client: unable to connect to 154.35.22.11:443 («general SOCKS server failure»)
21.07.2016 18:08:08.200 [WARN] Proxy Client: unable to connect to 104.131.108.182:56880 («general SOCKS server failure»)
21.07.2016 18:08:08.300 [WARN] Proxy Client: unable to connect to 83.212.101.3:41213 («general SOCKS server failure»)
21.07.2016 18:08:42.900 [WARN] Proxy Client: unable to connect to 154.35.22.9:80 («general SOCKS server failure»)
21.07.2016 18:08:42.900 [WARN] Proxy Client: unable to connect to 154.35.22.10:80 («general SOCKS server failure»)
21.07.2016 18:08:42.900 [WARN] Proxy Client: unable to connect to 154.35.22.12:80 («general SOCKS server failure»)
21.07.2016 18:23:08.200 [WARN] Proxy Client: unable to connect to 83.212.101.3:41213 («general SOCKS server failure»)
21.07.2016 18:23:08.300 [WARN] Proxy Client: unable to connect to 154.35.22.11:443 («general SOCKS server failure»)
21.07.2016 18:23:08.300 [WARN] Proxy Client: unable to connect to 104.131.108.182:56880 («general SOCKS server failure»)
21.07.2016 18:23:42.900 [WARN] Proxy Client: unable to connect to 154.35.22.9:80 («general SOCKS server failure»)
21.07.2016 18:23:42.900 [WARN] Proxy Client: unable to connect to 154.35.22.10:80 («general SOCKS server failure»)
21.07.2016 18:23:45.000 [WARN] Proxy Client: unable to connect to 154.35.22.12:80 («general SOCKS server failure»)
21.07.2016 18:32:07.800 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
21.07.2016 18:32:07.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
21.07.2016 18:32:07.800 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
21.07.2016 18:32:08.200 [NOTICE] Delaying directory fetches: DisableNetwork is set.
21.07.2016 18:32:17.300 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
21.07.2016 18:32:17.300 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
21.07.2016 18:32:17.300 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
21.07.2016 18:32:17.300 [NOTICE] Opening Socks listener on 127.0.0.1:9150
21.07.2016 18:32:25.400 [NOTICE] new bridge descriptor ‘ndnop3’ (fresh): $8DFCD8FB3285E855F5A55EDDA35696C743ABFC4E
ndnop3 at 109.105.109.165
21.07.2016 18:32:25.400 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
21.07.2016 18:32:26.100 [NOTICE] new bridge descriptor ‘noether’ (fresh): $7B126FAB960E5AC6A629C729434FF84FB5074EC2
noether at 192.99.11.54
21.07.2016 18:32:26.100 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
21.07.2016 18:32:26.400 [NOTICE] new bridge descriptor ‘GreenBelt’ (fresh): $C73ADBAC8ADFDBF0FC0F3F4E8091C0107D093716
GreenBelt at 154.35.22.9
21.07.2016 18:32:26.400 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
21.07.2016 18:32:26.700 [NOTICE] new bridge descriptor ‘Mosaddegh’ (fresh): $8FB9F4319E89E5C6223052AA525A192AFBC85D55
Mosaddegh at 154.35.22.10
21.07.2016 18:32:26.700 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
21.07.2016 18:32:45.200 [WARN] Proxy Client: unable to connect to 83.212.101.3:41213 («general SOCKS server failure»)
21.07.2016 18:32:45.200 [WARN] Proxy Client: unable to connect to 104.131.108.182:56880 («general SOCKS server failure»)
21.07.2016 18:32:45.200 [WARN] Proxy Client: unable to connect to 154.35.22.11:49868 («general SOCKS server failure»)
21.07.2016 18:33:19.900 [WARN] Proxy Client: unable to connect to 154.35.22.12:80 («general SOCKS server failure»)
21.07.2016 18:39:41.800 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
21.07.2016 18:39:41.900 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
21.07.2016 18:39:41.900 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
21.07.2016 18:39:42.200 [NOTICE] Delaying directory fetches: DisableNetwork is set.
21.07.2016 18:39:46.600 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
21.07.2016 18:39:46.600 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
21.07.2016 18:39:46.600 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
21.07.2016 18:39:46.600 [NOTICE] Opening Socks listener on 127.0.0.1:9150
21.07.2016 21:27:11.700 [NOTICE] Your system clock just jumped 9893 seconds forward; assuming established circuits no longer work.
21.07.2016 21:27:22.400 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
21.07.2016 21:27:22.400 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
21.07.2016 21:27:22.400 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
21.07.2016 21:27:22.400 [WARN] connection_connect_sockaddr(): Bug: Tried to open a socket with DisableNetwork set. (on Tor 0.2.7.6 7a489a6389110120)
21.07.2016 21:27:22.400 [WARN] Problem bootstrapping. Stuck at 25%: Loading networkstatus consensus. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 8; recommendation warn; host BD6A829255CB08E66FBE7D3748363586E46B3810 at 171.25.193.9:80)
21.07.2016 21:27:22.400 [WARN] 30 connections have failed:
21.07.2016 21:27:22.400 [WARN] 23 connections died in state handshaking (proxy) with SSL state (No SSL object)
21.07.2016 21:27:22.400 [WARN] 3 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN
21.07.2016 21:27:22.400 [WARN] 3 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE
Источник
Tor Browser is unable to connect to Tor network, connecting to relays failed with TLS_ERROR, so Tor Browser can’t connect to bridges.
First and foremost, I am ethnically and biologically Chinese, though I don’t regard myself as a Chinese in anyway whatsoever, the point is I am behind the notorious not-so-great «Great Firewall of China», which censors and blocks accesses to free world websites and restricts freedom of speech and freedom of information—and it’s very good at what it does.
The GFW implements methods like Deep Packet Inspection, Network Black-holing, DNS Spoofing, Quality of Service, TCP reset and TLS attacking, and it can block Tor Network access, the GFW is not to be underestimated.
I used to edit hosts file to gain access to websites like Wikipedia and DeviantArt that are blocked by DNS poisoning only. I am free to access Wikipedia and DeviantArt and other websites blocked by the same technique. But not websites like Google, Quora etc. that are blocked by more advanced technologies (Black-holing, Man-in-the-middle, TCP reset, Deep Packet Inspection). To gain access to latter websites I need to establish encrypted connection to computers outside of the GFW, and this comes often at a cost of money.
I have no money, otherwise I would use Virtual Private Networks like most imbecile mundane masses do, they pay money to make others do the thinking for them so that they don’t need do the thinking themselves. That’s why I use Tor, of course I also use other free proxies like ShadowSocksR, Lantern, V2RayN and Psiphon3, but none of them are as reliable as Tor, however none of them are as slow as Tor either.
Tor used to be my most reliable method of bypassing the GFW and almost never failed. Well, it used to be, up until late October 2020, when it suddenly stops working altogether.
So I keep getting error messages. below are an inexhaustive list of them.
Tor failed to establish a Tor network connection. Retrieving network status failed ( done — 0.0.2.0:2).
Unable to obtain a bridge from BridgeDB. NS_ERROR_NET_INTERRUPT
Tor failed to establish a Tor network connection. Loading relay information failed ( done — 0.0.2.0:2).
Tor failed to establish a Tor network connection. Retrieving network status failed (TLS_ERROR — 0.0.2.0:2 ).
And before you start, I have already tried all the steps in the picture below long before it stopped functioning, and I tried again and again and just got the same error messages: 
I used to use meek-azure to connect to Tor Network and obfs4 was far less reliable than meek-azure somehow. And I never saw FTE, obfs3 and ScrambleSuit listed in Built-in Bridges drop list, I am sure of it, well I used torbrowser-install-win64-10.0.2_en-US.exe recently before switching to torbrowser-install-10.5a2_en-US.exe, and in these versions there are only obfs4 and meek (and snowflake in 10.5a2). And all of these failed.
Well I gmailed bridges@bridges.torproject.org with «get bridges», «get transport obfs4», and «get ipv6», got the bridges, provided the bridges I know, and they worked, and they worked well, but only the first time, after an hour or so, I don’t know how long, the connections got interrupted while using Tor, and Tor can’t reconnect to the provided bridges. The problem is I can only send a gmail once every 3 hours and I can only get a maximum of 3 bridges with a minimum of 1 bridge in one reply and I have only one gmail account and all the bridges’ ip address have ping round-trip time longer than 250 milliseconds and often time out. (Well I recently found that I can use https://bridges.torproject.org/bridges?transport=obfs4 to get bridges, no 3 hour limit like gmail, but the bridges are also far away.)
So here are some logs, I hope you find it relevant and informational.
11/1/20, 06:02:04.886 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 11/1/20, 06:02:04.887 [NOTICE] Opening Socks listener on 127.0.0.1:9150 11/1/20, 06:02:04.887 [NOTICE] Opened Socks listener on 127.0.0.1:9150 11/1/20, 06:02:05.654 [NOTICE] Bridge ‘dktoke’ has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a0c:4d80:42:702::1]:27015) based on the configured Bridge address. 11/1/20, 06:02:05.654 [NOTICE] Bootstrapped 1% (conn_pt): Connecting to pluggable transport 11/1/20, 06:02:05.655 [NOTICE] Bootstrapped 2% (conn_done_pt): Connected to pluggable transport 11/1/20, 06:02:05.833 [NOTICE] Ignoring directory request, since no bridge nodes are available yet. 11/1/20, 06:02:07.434 [NOTICE] Bootstrapped 10% (conn_done): Connected to a relay 11/1/20, 06:02:07.805 [NOTICE] Bootstrapped 14% (handshake): Handshaking with a relay 11/1/20, 06:02:08.540 [NOTICE] Bootstrapped 15% (handshake_done): Handshake with a relay done 11/1/20, 06:02:08.542 [NOTICE] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection 11/1/20, 06:02:08.941 [NOTICE] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus 11/1/20, 06:02:09.540 [NOTICE] Bridge ‘dktoke’ has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a0c:4d80:42:702::1]:27015) based on the configured Bridge address. 11/1/20, 06:02:10.555 [NOTICE] Bridge ‘dktoke’ has both an IPv4 and an IPv6 address. Will prefer using its IPv4 address (45.145.95.6:27015) based on the configured Bridge address. 11/1/20, 06:02:17.130 [NOTICE] Bootstrapped 50% (loading_descriptors): Loading relay descriptors 11/1/20, 06:02:26.698 [WARN] Proxy Client: unable to connect to 209.148.46.65:443 («general SOCKS server failure») 11/1/20, 06:02:26.699 [WARN] Proxy Client: unable to connect to 144.217.20.138:80 («general SOCKS server failure») 11/1/20, 06:02:26.699 [WARN] Proxy Client: unable to connect to 146.57.248.225:22 («general SOCKS server failure») 11/1/20, 06:02:26.700 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 («general SOCKS server failure») 11/1/20, 06:02:26.701 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 («general SOCKS server failure») 11/1/20, 06:02:26.701 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 («general SOCKS server failure») 11/1/20, 06:02:26.702 [WARN] Proxy Client: unable to connect to 193.11.166.194:27015 («general SOCKS server failure») 11/1/20, 06:02:26.702 [WARN] Proxy Client: unable to connect to 192.95.36.142:443 («general SOCKS server failure») 11/1/20, 06:02:26.702 [WARN] Proxy Client: unable to connect to 37.218.245.14:38224 («general SOCKS server failure») 11/1/20, 06:02:26.703 [WARN] Proxy Client: unable to connect to 193.11.166.194:27020 («general SOCKS server failure») 11/1/20, 06:02:26.703 [WARN] Proxy Client: unable to connect to 193.11.166.194:27025 («general SOCKS server failure») 11/1/20, 06:02:26.703 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 («general SOCKS server failure») 11/1/20, 06:02:29.674 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150 11/1/20, 06:02:29.674 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 11/1/20, 06:02:29.842 [WARN] Pluggable Transport process terminated with status code 0 11/1/20, 06:02:30.594 [NOTICE] Delaying directory fetches: DisableNetwork is set. 11/1/20, 06:02:37.717 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 11/1/20, 06:02:37.717 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 11/1/20, 06:02:37.717 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 11/1/20, 06:02:37.717 [NOTICE] Opening Socks listener on 127.0.0.1:9150 11/1/20, 06:02:37.718 [NOTICE] Opened Socks listener on 127.0.0.1:9150 11/1/20, 06:02:40.154 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150 11/1/20, 06:02:40.154 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 11/1/20, 06:02:40.154 [WARN] Problem bootstrapping. Stuck at 50% (loading_descriptors): Loading relay descriptors. (DONE; DONE; count 1; recommendation warn; host 97700DFE9F483596DDA6264C4D7DF7641E1E39CE at 0.0.2.0:2) 11/1/20, 06:02:40.154 [WARN] 13 connections have failed: 11/1/20, 06:02:40.154 [WARN] 12 connections died in state handshaking (proxy) with SSL state (No SSL object) 11/1/20, 06:02:40.154 [WARN] 1 connections died in state handshaking (TLS) with SSL state SSLv3/TLS write client hello in HANDSHAKE 11/1/20, 06:02:40.197 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 11/1/20, 06:02:40.832 [WARN] Pluggable Transport process terminated with status code 0 11/1/20, 06:09:49.275 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 11/1/20, 06:09:49.275 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 11/1/20, 06:09:49.275 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 11/1/20, 06:09:49.275 [NOTICE] Opening Socks listener on 127.0.0.1:9150 11/1/20, 06:09:49.275 [NOTICE] Opened Socks listener on 127.0.0.1:9150 11/1/20, 06:09:50.278 [NOTICE] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits 11/1/20, 06:09:50.549 [NOTICE] Bootstrapped 76% (ap_conn_pt): Connecting to pluggable transport to build circuits 11/1/20, 06:09:50.550 [NOTICE] Bootstrapped 77% (ap_conn_done_pt): Connected to pluggable transport to build circuits 11/1/20, 06:09:52.570 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150 11/1/20, 06:09:52.570 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 11/1/20, 06:09:52.839 [WARN] Pluggable Transport process terminated with status code 0 11/1/20, 06:09:53.354 [NOTICE] Delaying directory fetches: DisableNetwork is set.
I have found Tor BrowserBrowserTorBrowserTorTor.exe but when I type tor and enter in cmd (of course I cd’ed to that directory), there are no responces whatsoever, I tried tor /?, tor /help, tor /h, tor -?, tor -h and tor -help, no responces.
I have found Tor BrowserBrowserTorBrowserTorPluggableTransports directory and there are obfs4proxy.exe and snowflake-client.exe (in 10.5.a2 version), but no fte, scramblesuit and obfs3, how do I get them to use with the latest version and how do I config Tor BrowserBrowserTorBrowserDataTortorrc file to actually use them (as clients, not servers)?
I have found Tor BrowserBrowserTorBrowserDataTorgeoip and geoip6 files which are based on GeoLite2-Country.mmdb on 2019-12-03 and outdated so I updated them. They are now based on 2020-10-27 version of GeoLite2-Country.mmdb.
I want to change Tor Browser ports, are the following correct? SocksListenAddress 127.0.0.1:9180 SocksPort 9180 ControlPort 9081
How do I change default relays used by Tor Browser? I think they might have been compromised so I want to know the relays and make Tor Browser connect to working relays.
And I read somewhere using uTLS and HTTP/2 transport will make Tor Browser more resistant to GFW, how can I do this?
That’s all, folks. If you can help me, I would be really grateful.
Источник
Hi everyone,
I freshly installed tor from the community repo, edited the configuration file to work as an exit node, and now I try to run it as a service, but it won’t start and I can’t figure out why. When using systemctl to start it, there is no output at all. Looking at the journal, it says it exited for no apparent reason:
$ / systemctl start tor
$ / systemctl status tor
tor.service - Anonymizing Overlay Network
Loaded: loaded (/usr/lib/systemd/system/tor.service; enabled)
Active: failed (Result: exit-code) since Tue 2013-08-20 23:54:46 CEST; 2s ago
Process: 3006 ExecStart=/usr/bin/tor -f /etc/tor/torrc (code=exited, status=255)
Aug 20 23:54:46 meteor systemd[1]: Started Anonymizing Overlay Network.
Aug 20 23:54:46 meteor tor[3006]: Aug 20 23:54:46.829 [notice] Tor v0.2.3.25 (git-17c24b3118224d65) running on Linux.
Aug 20 23:54:46 meteor tor[3006]: Aug 20 23:54:46.830 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Aug 20 23:54:46 meteor tor[3006]: Aug 20 23:54:46.830 [notice] Read configuration file "/etc/tor/torrc".
Aug 20 23:54:46 meteor tor[3006]: Aug 20 23:54:46.834 [notice] Initialized libevent version 2.0.21-stable using method epoll (with changelist). Good.
Aug 20 23:54:46 meteor systemd[1]: tor.service: main process exited, code=exited, status=255/n/a
Aug 20 23:54:46 meteor systemd[1]: Unit tor.service entered failed state.This is what /etc/systemd/system/multi-user.target.wants/tor.service looks like:
[Unit]
Description=Anonymizing Overlay Network
After=network.target
[Service]
User=tor
Type=simple
ExecStart=/usr/bin/tor -f /etc/tor/torrc
KillSignal=SIGINT
LimitNOFILE=65536
[Install]
WantedBy=multi-user.targetWhen I execute tor directly by hand, it works fine and writes successfully to its logfile. When called via systemctl, it doesn’t even get to touch its logfile.
$ / /usr/bin/tor -f /etc/tor/torrc
Aug 20 23:58:18.368 [notice] Tor v0.2.3.25 (git-17c24b3118224d65) running on Linux.
Aug 20 23:58:18.369 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Aug 20 23:58:18.369 [notice] Read configuration file "/etc/tor/torrc".
Aug 20 23:58:18.372 [notice] Initialized libevent version 2.0.21-stable using method epoll (with changelist). Good.
Aug 20 23:58:18.372 [notice] Opening OR listener on 0.0.0.0:443
Aug 20 23:58:18.372 [notice] Opening Directory listener on 0.0.0.0:80After calling tor by hand, the logfile reads:
Aug 20 23:58:18.000 [notice] Tor 0.2.3.25 (git-17c24b3118224d65) opening log file.
Aug 20 23:58:18.000 [notice] Parsing GEOIP file /usr/share/tor/geoip.
Aug 20 23:58:18.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
Aug 20 23:58:18.000 [notice] This version of OpenSSL has a known-good EVP counter-mode implementation. Using it.
Aug 20 23:58:18.000 [notice] OpenSSL OpenSSL 1.0.1e 11 Feb 2013 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation
Aug 20 23:58:18.000 [notice] Your Tor server's identity key fingerprint is 'xxxxx XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
Aug 20 23:58:18.000 [notice] Reloaded microdescriptor cache. Found 4424 descriptors.
Aug 20 23:58:19.000 [notice] We now have enough directory information to build circuits.
Aug 20 23:58:19.000 [notice] Bootstrapped 80%: Connecting to the Tor network.
Aug 20 23:58:20.000 [notice] Heartbeat: It seems like we are not in the cached consensus.
Aug 20 23:58:20.000 [notice] Heartbeat: Tor's uptime is 0:00 hours, with 2 circuits open. I've sent 0 kB and received 0 kB.
Aug 20 23:58:20.000 [notice] Bootstrapped 85%: Finishing handshake with first hop.
Aug 20 23:58:20.000 [notice] Bootstrapped 90%: Establishing a Tor circuit.
Aug 20 23:58:21.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Aug 20 23:58:21.000 [notice] Bootstrapped 100%: Done.
Aug 20 23:58:21.000 [notice] Now checking whether ORPort XXX.XXX.XXX.XXX:443 and DirPort XXX.XXX.XXX.XXX:80 are reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Aug 20 23:58:21.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Aug 20 23:58:21.000 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.
Aug 20 23:58:34.000 [notice] Performing bandwidth self-test...done.
Aug 21 00:00:12.000 [notice] Interrupt: we have stopped accepting new connections, and will shut down in 30 seconds. Interrupt again to exit now.
Aug 21 00:00:42.000 [notice] Clean shutdown finished. Exiting.I assume the configuration is correct. Tor is running as the user tor, also indicated in the config file /etc/tor/torrc:
I’d be grateful for any help with this!
Last edited by tyo (2013-08-21 05:03:04)