|
|
|
Dicrock
Стаж: 13 лет 1 месяц Сообщений: 1175
|
Dicrock ·
31-Май-24 03:42
(1 год назад)
LeonMskRu писал(а):
собрано на windows10 64bit
работа на 32 и win7 не проверялась
Под 7-кой x64 всё грустно :
скрытый текст
Цитата:
i686-gnu_20240523_1930\i686-gnu\arti.exe
---------------------------
Точка входа в процедуру GetSystemTimePreciseAsFileTime не найдена в библиотеке DLL kernel32.dll.
***
i686-msvc_20240523_1930\i686-msvc\arti.exe
---------------------------
Ошибка при запуске приложения (0xc0000005). Для выхода из приложения нажмите кнопку "ОК".
***
x86_64-gnu_20240523_1930\x86_64-gnu\arti.exe
---------------------------
Точка входа в процедуру GetSystemTimePreciseAsFileTime не найдена в библиотеке DLL kernel32.dll.
***
x86_64-msvc_20240523_1931\x86_64-msvc\arti.exe
---------------------------
Ошибка при запуске приложения (0xc000007b).
LeonMskRu писал(а):
уже 20+ лет "не программировал" (писал совсем простой парсер логов АТС на perl)
А собственно что это парсится ? В первом, втором и третьем случае ? Чуть более развёрнуто ? Это применимо к обычному тору в качестве мостов ?
Цитата:
но это у кого linux есть. в винде так и не понял как JQ с такими ключами запустить
jq: error: syntax error, unexpected INVALID_CHARACTER (Windows cmd shell quoting issues?)
Оптимизировать и адаптировать не проблема, опыт работы с jq есть. Только мне надо сначала понять, что и зачем 
|
|
|
|
artenax
Стаж: 2 года 11 месяцев Сообщений: 1714
|
artenax ·
01-Июн-24 22:37
(спустя 1 день 18 часов)
Dicrock писал(а):
86325434Под 7-кой x64 всё грустно
Под Windows 8.0 32 bit работает. gnu и msvc.
|
|
|
|
LeonMskRu
Стаж: 17 лет 10 месяцев Сообщений: 88
|
LeonMskRu ·
01-Июн-24 23:45
(спустя 1 час 8 мин., ред. 01-Июн-24 23:45)
это официальный https://metrics.torproject.org/rs.html#advanced
например https://metrics.torproject.org/rs.html#search/flag:guard%20country:ru%20running:true%20
а https://onionoo.torproject.org/details?search=flag:guard и другие примеры это кому надо скачать JSON/CSV/etc
c АРТИ все немного сложней (пока?) чем с tor.exe
ТОР через багофичу вроде как способен соединится как с мост/bridge с любым "relay"
даже есть отдельный https://github.com/ValdikSS/tor-relay-scanner
но даже в АРТИ шанс что удастся соединится есть
флаг Guard повышает этот шанс
я убираю Exit чтобы не попадать на загруженные ноды в том числе (некоторые даже торренты через ТОР пытаются качать)
так же сортирую по consensus_weight это вроде как заявленая скорость ноды. чтобы на совсем уж левые не попадать (хотя среди Guard их не так много)
опять же лично я фильтрую по 0.4.8.11 версии клиента. ну вроде как и остальные (не все.) 0.4.8.* можно. но тут ИМХО показывает что админ следит за нодой
и получается что то типа (это вариант для проверки. в рабочем только IP + fingerprint)
[2a03: ::a2]:443 16000 se ["Fast","Guard","HSDir","Running","Stable","V2Dir","Valid"] 0.4.8.11
[2a03: ::1]:443 16000 de ["Fast","Guard","HSDir","Running","Stable","V2Dir","Valid"] 0.4.8.11
[2a02: ::1]:443 16000 de ["Fast","Guard","HSDir","Running","Stable","V2Dir","Valid"] 0.4.8.11
[2a01: ::4]:443 16000 fi ["Fast","Guard","HSDir","Running","Stable","V2Dir","Valid"] 0.4.8.11
в обычном ТОРе оно вообще работает идеально
http://imageshack.com/a/img923/5625/XcH148.png (хоть это и TCP но оно только GUI для tor.exe вроде NYX/linux и прочих)
это я прописал как Bridge то что мне подходит (в том числе IPv6)
только не забыть что в torrc формате
Bridge IP Fingerprint
p.s. можно экпортировать из TCP. тоже выбрать только Guard/etc == но оно на любителей как и АРТИ
https://i.imgur.com/M7sNVjB.gif
если использовать ExcludedNodes может быть всякое разное
Not using bridge at 31.171.155.107: it is in ExcludeNodes.
это вроде Албания и оно у меня вместе с Китай/Австралия/етк в исключениях
а еще часто бывает что страна IPv4 и страна IPv6 разные
ExcludeNodes {ad},{ae},{al},{am},{ar},{au},{az},{bd},{br},{cl},{cr},{cy},{ge},{gi},{hk},{id},{il},{in},{ir},{jp},{kg},{kr},{kz},{md},{mu},{mx},{my},{nz},{pe},{ph},{pl},{pr},{re},{sc},{sg},{th},{tr},{tw},{ua},{uy},{uz},{vn},{za}
|
|
|
|
avpopik
Стаж: 13 лет 5 месяцев Сообщений: 10
|
avpopik ·
02-Июн-24 09:30
(спустя 9 часов)
Честно скажу искал по теме ошибку, но не нашёл, в клиенте возникает ошибка при запросе к анонсеру http://bt3.t-ru.org/ann? При попытке скачивания через tor.
На других трекерах, анонсеры другие, там работает, это какое то ограничение в tor или rutracker или просто у меня руки кривые. Проблема в том, что мобильные операторы заблокировали трафик и протоколы p2p , wireguard , opnvpn и др. Пока ищу способ качать торренты.
|
|
|
|
artenax
Стаж: 2 года 11 месяцев Сообщений: 1714
|
artenax ·
02-Июн-24 10:20
(спустя 50 мин., ред. 02-Июн-24 10:20)
avpopik
Это очень странное сообщение. Связь с трекером вроде есть, он сообщает Missing port. Кто-то подделал параметр port из запроса. А если поменять в адресе трекера http > https
?
avpopik писал(а):
86333389Пока ищу способ качать торренты
Можно через shadowsocks. В простонародье - "носки".
|
|
|
|
Dicrock
Стаж: 13 лет 1 месяц Сообщений: 1175
|
Dicrock ·
02-Июн-24 16:19
(спустя 5 часов, ред. 02-Июн-24 16:19)
Всё, понял, что к чему - самостоятельно генерим bridge - relay список. Попробую на досуге это дело под win переделать.
LeonMskRu писал(а):
86332532в обычном ТОРе оно вообще работает идеально
http://imageshack.com/a/img923/5625/XcH148.png (хоть это и TCP но оно только GUI для tor.exe вроде NYX/linux и прочих)
это я прописал как Bridge то что мне подходит (в том числе IPv6)
Затолкал первые 50 бриджей из выхлопа ipv4 nl/de варианта (поначалу затолкал всё, но тор надолго задумался) - всё грустно.
Код:
Jun 02 22:01:54.000 [warn] 123 connections have failed:
Jun 02 22:01:54.000 [warn] 123 connections died in state connect()ing with SSL state (No SSL object)
Jun 02 22:01:54.000 [warn] Problem bootstrapping. Stuck at 5% (conn): Connecting to a relay. (Connection timed out [WSAETIMEDOUT ]; TIMEOUT; count 125; recommendation warn; host BD8D32F6BDD89B74FC810592F3327C96521C7529 at 176.9.90.88:54321)
Jun 02 22:01:54.000 [warn] 124 connections have failed:
Jun 02 22:01:54.000 [warn] 124 connections died in state connect()ing with SSL state (No SSL object)
Jun 02 22:01:54.000 [warn] Problem bootstrapping. Stuck at 5% (conn): Connecting to a relay. (Connection timed out [WSAETIMEDOUT ]; TIMEOUT; count 126; recommendation warn; host 42B4F52C5B11E4D39855F654955425B0D5A0598B at 5.9.121.207:443)
Jun 02 22:01:54.000 [warn] 125 connections have failed:
Jun 02 22:01:54.000 [warn] 125 connections died in state connect()ing with SSL state (No SSL object)
Позже поиграюсь с другими странами и ipv6. В разных вариациях.
LeonMskRu писал(а):
86332532только не забыть что в torrc формате
Bridge IP Fingerprint
Дык это там в конец же вкрутить можно )))
Код:
awk '{ print "Bridge " $1" "$2}'
LeonMskRu писал(а):
86332532ExcludeNodes {ad},{ae},{al},{am},{ar},{au},{az},{bd},{br},{cl},{cr},{cy},{ge},{gi},{hk},{id},{il},{in},{ir},{jp},{kg},{kr},{kz},{md},{mu},{mx},{my},{nz},{pe},{ph},{pl},{pr},{re},{sc},{sg},{th},{tr},{tw},{ua},{uy},{uz},{vn},{za}
У меня не так всё радикально, обычно достаточно "{ru},{ua},{by},{kz}", но как я уже выше писал, я пока пробовал, прописанные по дефолту nl & de 
|
|
|
|
LeonMskRu
Стаж: 17 лет 10 месяцев Сообщений: 88
|
LeonMskRu ·
02-Июн-24 17:19
(спустя 1 час, ред. 02-Июн-24 17:19)
ну тут несколько моментов
1) в РФ иногда стали блокировать почти все ТОР ноды по IP4
2) по IPv6 они же (если там 4+6) пока что работают без проблем
3) выбирать ИМХО лучше Stable/Fast и смотреть (если не автоматом все делается) как давно меняли IP:port и uptime. ну или парсить раз в день и подсовывать новые мосты через %include в torrc
так же можно попробовать
OBFS4 но тут вопрос банят ли и их по IPv4
webtunnel вроде без проблем особых пока. но 90%+ адресов что я видел пишет что входные ноды в одной сети в Польше
http://imageshack.com/a/img922/3015/8orRqT.png
это рабочие webtunnel что я нашел или получил на https://bridges.torproject.org/options/
snowflake как то неоднозначно работает. то без проблем находит мосты то может так и не найти за разумное время (минут 5:)
p.s. про tor-relay-scanner "под windows" не понял
у него на сайте .exe (бинарник python)
tor-relay-scanner-1.0.0.exe --proxy 127.0.0.1:3128 -c ru,fi,se,no -p 443 -n 4 -g 44 --timeout 3 --torrc -o bridges.conf
прокси ибо часть адресов типа *.torproject.org вроде под баном
страны свои выбирать. я по пингу смотрел
порт 443 не обязателен ибо один фиг по ИП наверно (но это неточно.) банят
пишем в torrc
%include C:\\tor\\bridges.conf
если тор как сервис то
net stop tor & net start tor
про awk/etc я в курсе просто тут мешанина...
torrc == Bridge IP hash
TCP == IP hash
ARTI == или IP hash через '''массив''' или json "IP hash", "IP hash",
и да если есть честный IPv6 то на данный момент
ClientUseIPv4 0
ClientUseIPv6 1
ClientPreferIPv6ORPort 1
творит чудеса. без всяких мостов.
правда я еще делал чистку (у меня это TOR\var) чтобы старые Guard не остались
net stop tor
copy /A /V /Y state state.BAK
grep -Ev ^Guard state.BAK > state
net start tor
|
|
|
|
Dicrock
Стаж: 13 лет 1 месяц Сообщений: 1175
|
Dicrock ·
03-Июн-24 13:50
(спустя 20 часов)
LeonMskRu писал(а):
86334902по IPv6 они же (если там 4+6) пока что работают без проблем
Загнал 2 десятка ipv6 bridge - релеев nl/de в конфиг, оно покуролесило по кругу вот так минут 15
скрытый текст
Код:
Jun 03 15:09:56.000 [notice] Bridge 'Whitetree' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a01:4f8:161:7148::2]:54782) based on the configured Bridge address.
Jun 03 15:10:03.000 [notice] Bridge 'Novastation' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a01:4f8:10b:3357::2]:8443) based on the configured Bridge address.
Jun 03 15:10:03.000 [notice] Bridge 'Henna8600' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a01:4f9:2b:8d8::2]:9001) based on the configured Bridge address.
Jun 03 15:10:11.000 [notice] Bridge 'Henna8600' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a01:4f9:2b:8d8::2]:9001) based on the configured Bridge address.
Jun 03 15:10:19.000 [notice] Bridge 'tcpsyn' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a0d:5940:38:89::]:9001) based on the configured Bridge address.
Jun 03 15:10:20.000 [notice] Bridge 'Droutnutch' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a01:4f8:10b:670::2]:9001) based on the configured Bridge address.
Jun 03 15:10:22.000 [notice] Bridge 'currentlane' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a01:4f8:202:7144:c49d:e29a:d44a:c6ea]:443) based on the configured Bridge address.
Jun 03 15:10:36.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jun 03 15:10:55.000 [notice] Bridge 'root' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a01:4f8:13a:2291::2]:443) based on the configured Bridge address.
Jun 03 15:10:59.000 [notice] Application request when we haven't used client functionality lately. Optimistically trying known bridges again.
Jun 03 15:10:59.000 [notice] Bridge 'root' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a01:4f8:13a:2291::2]:443) based on the configured Bridge address.
Jun 03 15:10:59.000 [notice] Bridge 'tcpsyn' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a0d:5940:38:89::]:9001) based on the configured Bridge address.
Jun 03 15:11:00.000 [notice] Bridge 'tcpsyn' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a0d:5940:38:89::]:9001) based on the configured Bridge address.
Jun 03 15:11:02.000 [notice] Bridge 'tcpsyn' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a0d:5940:38:89::]:9001) based on the configured Bridge address.
Jun 03 15:11:04.000 [notice] Bridge 'tcpsyn' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a0d:5940:38:89::]:9001) based on the configured Bridge address.
Jun 03 15:11:07.000 [notice] Bridge 'mickymouse' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a01:4f8:140:94d6::2]:9001) based on the configured Bridge address.
Jun 03 15:11:07.000 [notice] Bridge 'tcpsyn' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a0d:5940:38:89::]:9001) based on the configured Bridge address.
Jun 03 15:11:09.000 [notice] Bridge 'root' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a01:4f8:13a:2291::2]:443) based on the configured Bridge address.
Jun 03 15:11:10.000 [notice] Bridge 'tcpsyn' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a0d:5940:38:89::]:9001) based on the configured Bridge address.
Jun 03 15:11:11.000 [notice] Bridge 'Henna8600' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a01:4f9:2b:8d8::2]:9001) based on the configured Bridge address.
и я пока забил.
LeonMskRu писал(а):
86334902так же можно попробовать
OBFS4 но тут вопрос банят ли и их по IPv4
С obfs4 проблем нет. И не было. Вот только получить их не так просто как вданном случае. Или бот, или форма с капчей или мыло + их ограниченное количество. С веб-туннелями та же петрушка.
LeonMskRu писал(а):
86334902и да если есть честный IPv6 то на данный момент
Тут белый и серый ipv4 рандомно выдаётся при поднятии сессии, какой там ipv6
|
|
|
|
LeonMskRu
Стаж: 17 лет 10 месяцев Сообщений: 88
|
LeonMskRu ·
03-Июн-24 20:37
(спустя 6 часов, ред. 03-Июн-24 20:37)
https://github.com/LeonMskRu/arti_windows/releases/tag/1.2.3-24-06-03
OBFS4 https://github.com/scriptzteam/Tor-Bridges-Collector/blob/main/bridges-obfs4
но там все подряд. и совсем древние по версиям. и дико медленные. етк
я через TCP выдрал более или менее рабочие. но думало очень долго и даже 1 раз сам TCP крашнулся
и да. IPv4 ИМХО бесполезно в РФ использовать как bridge
можно каждый день или чаще брать https://torscan-ru.ntc.party/
но лично у меня нашло 44 рабочих IPv6 нод. и НОЛЬ IPv4 == tor-relay-scanner
хотя с IPv6 в РФ и так все уныло. а тут еще и просадка (на сезонную вроде не похоже)
https://radar.cloudflare.com/adoption-and-usage/ru?dateRange=24w
1 июля 2023 == 33%
1 февраля 2024 == 26% IPv6
1 июня 2024 == 14%
может дошло ...
я с РТ бодался где то месяц что IPv6 больше года работало а потом перестало (route/bgp похоже отключали. tracert -6 доходил до "роутера" за моим роутером и все.)
|
|
|
|
северянин
Стаж: 16 лет 10 месяцев Сообщений: 243
|
северянин ·
04-Июн-24 11:43
(спустя 15 часов, ред. 04-Июн-24 11:43)
Dicrock писал(а):
86337811С obfs4 проблем нет. И не было.
Везёт вам, а у меня теперь проблемы очень даже есть (Москва МГТС).
В мае был заблокирован бесперебойно работавший 2 года (!) обфс4-бридж, бридж от 14 мая жил две недели, следующий - три дня, а теперь они живут максимум сутки.
И на почту присылают один (обычно уже дохлый), а не два и не три, как раньше. Либо говорят no bridges currently available, sorry.
Похоже, душегубы просто нарегили себе gmail-ов.
LeonMskRu писал(а):
86338884и да если есть честный IPv6 то на данный момент
ClientUseIPv4 0
ClientUseIPv6 1
ClientPreferIPv6ORPort 1
творит чудеса. без всяких мостов.
Если вы имеете в виду дефолтные (встроенные в бинарник) IPv6 bootstrap nodes, то у меня они не работают.
|
|
|
|
artenax
Стаж: 2 года 11 месяцев Сообщений: 1714
|
artenax ·
04-Июн-24 14:00
(спустя 2 часа 16 мин., ред. 04-Июн-24 16:03)
Кстати, можно включить лог самого obfs4proxy (список его опций можно получить по obfs4proxy --help). По наблюдениям, даже в DEBUG режиме он пишет только о неудачных соединениях и разрывах (об удачных можно узнать из лога тора). [я переименовал последний lyrebird в obfs4proxy из-за сложного названия].
Вот такой конфиг .config/arti/arti.toml:
Подробнее
Код:
[proxy]
socks_listen = 9050
[logging]
console = "info"
log_sensitive_information = "true"
[address_filter]
allow_onion_addrs = true
[bridges]
enabled = true
bridges = [
"Bridge obfs4 85.31.186.26:443 91A6354697E6B02A386312F68D82CF86824D3606 cert=PBwr+S8JTVZo6MPdHnkTwXJPILWADLqfMGoVvhZClMq/Urndyd42BwX9YFJHZnBB3H0XCw iat-mode=0",
"Bridge obfs4 85.31.186.98:443 011F2599C0E9B27EE74B353155E244813763C3E5 cert=ayq0XzCwhpdysn5o0EyDUbmSOx3X/oTEbzDMvczHOdBJKlvIdHHLJGkZARtT4dcBFArPPg iat-mode=0",
"Bridge obfs4 65.21.85.99:8088 7F6051103D00F6E6615C5C8D92C4B648B32331D3 cert=DQ6XOkBQSY424G3SVbOQH5R5aQuWWaCgSI6jv4q7LnI+0h/fJHv4cPX1TMHoY2zD2FUwdQ iat-mode=0"
]
[[bridges.transports]]
protocols = ["obfs4"]
path = "/usr/local/bin/obfs4proxy"
arguments = ["-enableLogging=true", "-logLevel=DEBUG", "-unsafeLogging=true", "DEBUG"]
run_on_startup = false
Обратите внимание: запятой после последнего моста нет. arti запускается простой командой: arti proxy
Т.е. добавлено:
Код:
arguments = ["-enableLogging=true", "-logLevel=DEBUG", "-unsafeLogging=true", "DEBUG"]
Лог будет в .local/share/arti/pt_state/obfs4proxy/obfs4proxy.log
На винде не знаю, где-то в профиле arti.
Мосты просто для примера, уже не работают в РФ.
Вот пример debug obfs4proxy.log лога:
Код:
2024/06/04 17:38:16 [NOTICE]: obfs4proxy-0.0.14 - launched
2024/06/04 17:38:16 [INFO]: obfs4proxy - initializing client transport listeners
2024/06/04 17:38:16 [INFO]: obfs4 - registered listener: 127.0.0.1:43535
2024/06/04 17:38:16 [INFO]: obfs4proxy - accepting connections
2024/06/04 17:39:16 [ERROR]: obfs4(65.21.85.99:8088) - outgoing connection failed: read tcp 172.16.0.2:39670->65.21.85.99:8088: i/o timeout
2024/06/04 17:40:01 [INFO]: obfs4(85.31.186.26:443) - closed connection
2024/06/04 17:40:01 [NOTICE]: Stdin is closed or unreadable: <nil>
2024/06/04 17:40:01 [NOTICE]: obfs4proxy - terminated
Заметьте: в 17:40:01 время выхода (завершения), он пишет с какими IP завершает соединение (closed connection), т.е. можно узнать какие мосты активно использовались на момент завершения.
Для классического тора torrc опции будут такие:
Код:
ClientTransportPlugin obfs4 exec /usr/local/bin/obfs4proxy -enableLogging=true -logLevel=DEBUG -unsafeLogging=true managed
А лог храниться в /var/lib/tor/pt_state/obfs4proxy.log (в случае службы) или .tor/pt_state/obfs4proxy.log (в случае запуска под юзером, т.е. в домашней папке).
Расскажу еще о граблях, с которыми столкнулся на линуксе. Если брать lyrebird из архива Тор браузера (а не из expert bundle, впрочем, насчет expert bundle не знаю) и скопировать в /usr/local/bin/obfs4proxy (через sudo cp):
1. Надо поставить флаг исполняемости: sudo chmod +x /usr/local/bin/obfs4proxy
2. Задать права на чтение юзеру (по умолчанию только root может читать и будет ошибка при запуске тора): sudo chmod 775 /usr/local/bin/obfs4proxy
3. Возможно, из-за маскировки дата бинарника будет 2000 года (унаследована), можно освежить до актуальной: sudo touch /usr/local/bin/obfs4proxy
Upd: также можно включить собственные логи snowflake и пр.
|
|
|
|
Dicrock
Стаж: 13 лет 1 месяц Сообщений: 1175
|
Dicrock ·
04-Июн-24 18:38
(спустя 4 часа, ред. 04-Июн-24 18:38)
северянин писал(а):
86340483В мае был заблокирован бесперебойно работавший 2 года (!) обфс4-бридж, бридж от 14 мая жил две недели, следующий - три дня, а теперь они живут максимум сутки.
И на почту присылают один (обычно уже дохлый), а не два и не три, как раньше. Либо говорят no bridges currently available, sorry.
Похоже, душегубы просто нарегили себе gmail-ов.
Имелось ввиду со свежими мостами. obfs4 мосты, что мне попадались жили - 1 - 2 недели. И это вполне себе неплохо для нынешних реалий. С бридж - релеями, о которых речь шла выше, всё совсем глухо было.
|
|
|
|
северянин
Стаж: 16 лет 10 месяцев Сообщений: 243
|
северянин ·
04-Июн-24 20:27
(спустя 1 час 49 мин.)
Dicrock писал(а):
86341328Имелось ввиду со свежими мостами. obfs4 мосты, что мне попадались жили - 1 - 2 недели.
Так и я имею в виду свежие obfs4-мосты. Свежайшие.
Месяц назад они были очень даже живучими, но всё резко изменилось буквально за последнюю неделю,
и теперь только что присланный obfs4 в 80% случаев у меня уже заблокирован.
По поводу relay-scanner:
Можно посредством --url произвести какую-то фильтрацию базы, чтобы он побольше внимания уделял IPv6 и поменьше - v4?
Очень странно получается: все 20 найденных нод - IPv4, хотя v6 у меня есть и работает:
Код:
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|2606:50c0:8001::154|:443... connected.
HTTP request sent, awaiting response... 200 OK
Я мог бы скачанный JSON перелопатить и очистить от лишнего, но вдруг есть более простой путь.
|
|
|
|
LeonMskRu
Стаж: 17 лет 10 месяцев Сообщений: 88
|
LeonMskRu ·
04-Июн-24 20:37
(спустя 10 мин., ред. 04-Июн-24 20:37)
не пробовал webtunnel (шустро. вроде почти все мосты что были до сих пор работают) ?
или snowflake (медленней. нередко очень долго не может найти рабочие мосты. но нет привязки к конкретным нодами а CDNы пока еще не так массово банят) ?
OBFS4 ну можно попробовать https://github.com/LeonMskRu/arti_windows/blob/main/2024_06_04_IPv4 но как писал у меня IPv4+IPv6 так что они могут быть и забанены на уровне IPv4
это выборка из 542 найденых тут же на github
tor-relay-scanner если имеется ввиду там все сложно.. автор делает его под себя.
проще парсить самому указанные в этом топике JSON (выше и адреса и примеры как я парсил) и выдирать IPv6. ну или есть windows10+ поставить TorControlPanel и оттуда экпортировать IPv6 Guard ноды
их пока не банят и почти все Guard (runned.) рабочие
|
|
|
|
северянин
Стаж: 16 лет 10 месяцев Сообщений: 243
|
северянин ·
04-Июн-24 21:02
(спустя 25 мин.)
LeonMskRu
Понятно, займусь в ближайшее время.
На obfs4 свет клином не сошёлся, конечно. Я к нему привык, т.к. всё нормально работало,
а мосты других типов на почту получить нельзя (сейчас думаю: вот и хорошо, что нельзя).
Завтра мой текущий мост непременно сдохнет - перейду на следующий тип.
Большое спасибо за ссылку со списками и прочую ценную информацию.
|
|
|
|
LeonMskRu
Стаж: 17 лет 10 месяцев Сообщений: 88
|
LeonMskRu ·
04-Июн-24 21:48
(спустя 45 мин., ред. 04-Июн-24 21:48)
artenax
я свои собранные транспорты смог запустить
etc/apparmor.d/abstractions/tor
/usr/share/tor/lyrebird ix,
/usr/share/tor/snowflake-client ix,
/usr/share/tor/webtunnel-client ix,
права на папку и файлы debian-tor
северянин
к сожалению только https://bridges.torproject.org/options/ для webtunnel
(но они обычно долго работают)
так что смело можно искать рабочие из https://github.com/scriptzteam/Tor-Bridges-Collector/blob/main/bridges-webtunnel
snowflake я обычно проверяю https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/...c?ref_type=heads
там более менее свежие/рабочие настройки. ну или в моих сборках https://github.com/LeonMskRu/arti_windows/blob/main/config_snowflake.toml
там 4е варианта
|
|
|
|
artenax
Стаж: 2 года 11 месяцев Сообщений: 1714
|
artenax ·
04-Июн-24 21:52
(спустя 4 мин., ред. 04-Июн-24 21:53)
LeonMskRu писал(а):
86342184я свои собранные транспорты смог запустить
Только если tor как служба и установлен apparmor (помимо libapparmor). Иначе это не требуется. Я давно запускаю от юзера. Хотя, даже от юзера сишный tor проверяет файл /etc/tor/torrc (отучить его от этого можно пересборкой). Профиль будет в ~/.tor
|
|
|
|
LeonMskRu
Стаж: 17 лет 10 месяцев Сообщений: 88
|
LeonMskRu ·
05-Июн-24 07:30
(спустя 9 часов, ред. 05-Июн-24 07:30)
блин. то ли я чтото непонял. то ли "не такие как все"(c)(r)(tm)
АРТИ
[tor_network]
fallback_caches = [
{ rsa_identity = "A52CA5B56C64D864F6AE43E56F29ACBD5706DDA1", ed_identity = "4ngwAxQ6Zw2VJB241CenzfrVtT6omCDOf9yGB1XAqTs", orports = [ "100.0.0.1:9111" ] },
]
torrc
FallbackDir 89.58.0.34 orport=9001 id=A76B8398293DE18EF766C79D898DAB1DE958949C ipv6=[2a03:4000:5d:fab::1]:9001
FallbackDir 89.58.17.228 orport=46856 id=593A4431DA2E315883406AECE1D1188E02F23D8F ipv6=[2a0a:4cc0:0:f0a:a45c:7aff:fe13:2781]:46856
FallbackDir 89.58.41.156 orport=143 id=F33ECAB340E6117597A3FF5B5F2B6D7475B56187 ipv6=[2a03:4000:66:15:18a0:6bff:fe90:3147]:143
FallbackDir 89.58.61.42 orport=9001 id=E6060F09E8007FC7CFAC7BC24477F9D878B247DD ipv6=[2a0a:4cc0:1:9e::1]:9001
https://github.com/LeonMskRu/arti_windows/releases
оказалось часть сборок была без vanguards
enabled features:
bridge-client, compression, dns-proxy, harden, hickory-proto, native-tls
onion-service-client, pt-client, secmem-proc, tokio, tokio-crate, tokio-util
vanguards
|
|
|
|
северянин
Стаж: 16 лет 10 месяцев Сообщений: 243
|
северянин ·
05-Июн-24 09:14
(спустя 1 час 44 мин.)
LeonMskRu
Хотел поделиться наблюдениями, но у вас приём личных сообщений отключён. Если это случайность, то включите, пожалуйста.
В общем, всё прошло в соответствии с планом, результат - более чем удовлетворительный.
|
|
|
|
LeonMskRu
Стаж: 17 лет 10 месяцев Сообщений: 88
|
LeonMskRu ·
09-Июн-24 00:59
(спустя 3 дня, ред. 09-Июн-24 00:59)
ну на данном этапе ТОР и даже АРТИ главное зацепиться
тем более в tor.exe можно как указано выше и FallbackDIR прописать на всякий случай
http://imageshack.com/a/img922/7053/1kvksT.png
а то у меня на РТ по умолчанию совсем уныло  и это пока еще на банят почти все IPv4 тор ноды как стало модно
Мосты по умолчанию 4/15 OK (причем OONI Probe проверяет и OBFS4)
Управляющие списками 1/10 OK
http://imageshack.com/a/img922/2433/3KfueV.png
я так понимаю это "встроенные" мосты OBFS4 из Tor\Pluggable_Transports\pt_config.json
https://github.com/LeonMskRu/arti_windows/releases/tag/1.2.4
в основном фиксят .onion и прочее с ними связаное
если ктото парсит JSON можно уже искать 0.4.8.12
http://imageshack.com/a/img922/1365/2Ux4sO.png
похоже и кэш надо чистить каждый раз
особенно если проверяются разные транспорты
del /q %USERPROFILE%\AppData\Local\torproject\Arti\cache\dir_blobs\*
del /q %USERPROFILE%\AppData\Local\torproject\Arti\cache\*
del /q %USERPROFILE%\AppData\Local\torproject\Arti\data\state\*
хотя даже с этим было несколько раз когда АРТИ работает. сайты открываются. но по логам куча самых разных Error/Failed/etc
удалил кэш. якобы нашло 3и моста OBFS4 но соединения через АРТИ не работают ..
http://imageshack.com/a/img924/4973/i3ndJU.png
запустил 2ой раз. так оно даже те мосты уже не видит
http://imageshack.com/a/img922/4808/lBwD6y.png
3ий раз. после очистки кэша.. находит мосты. но связи как не было так и нету
http://imageshack.com/a/img923/1030/UCo0Gp.png
но зато каждую "версию" фиксят .onion ;-P
|
|
|
|
artenax
Стаж: 2 года 11 месяцев Сообщений: 1714
|
artenax ·
09-Июн-24 01:15
(спустя 16 мин., ред. 09-Июн-24 09:34)
LeonMskRu
У меня с obfs4 мостами проблем нет (не ru IP).
|
|
|
|
LeonMskRu
Стаж: 17 лет 10 месяцев Сообщений: 88
|
LeonMskRu ·
10-Июн-24 03:12
(спустя 1 день 1 час, ред. 10-Июн-24 03:12)
да вот сам офигел.
оно что то стало мудрить на некоторых мостах.
прописал просто мосты на момент когда IPv4 не банили
запустил с -l debug
оно долго и упорно (к сожалению точное время не засек.) долбилось в 2а адраса
при прописанных 20и
и без удаления кэша при смене проверок (obfs4 vs bridges vs webtunnel) часто вообще ни одного рабочего моста не находит
самое противное что эти же адреса/мосты на tor.exe работают. проблема не в них/системе/провайдере/етк
да чего говорить если на IPv6 не всегда соединяется. при том что мой РТ их вроде вообще не банит
про ошибки уже выше писал. то при куче ошибок все равно все работает что надо (exit-ы)
https://imagizer.imageshack.com/a/img923/1030/UCo0Gp.png
то пишет найдено два моста. успешный bootstrap и ничего. curl не может открыть ни один сайт. даже до нормальных ошибок http/proxy не доходит дело
и даже если соединилось... появились какие то дикие тормоза. и вернулись ошибки на IPv6 exit
это BAT/CMD оба curl (и -4 и без -4 который отдает обычно IPv6 exit) запускаются прям один за другим
curl.exe -I -4 -x socks5://127.0.0.1:9150 --connect-timeout 15 https://rutr.life/myip
HTTP/2 200
date: Sun, 09 Jun 2024 08: 05:04 GMT
curl.exe -I -x socks5://127.0.0.1:9150 --connect-timeout 15 https://rutr.life/myip
HTTP/2 504
date: Sun, 09 Jun 2024 08: 06:05 GMT
сurl.exe -4 -x socks5://127.0.0.1:9150 --connect-timeout 15 https://rutr.life/myip
tm: 09/Jun/2024:11: 06:21 +0300<br><br>
lcurl.exe -x socks5://127.0.0.1:9150 --connect-timeout 15 https://rutr.life/myip
error code: 504
http://imageshack.com/a/img922/5718/ZxnJ2B.png
удалил все state/cache/etc запустил без мостов. и ведь так работает..
curl.exe -x socks5://127.0.0.1:9150 --connect-timeout 15 https://rutr.life/myip
ip: 2a0b:f4c2::7 DE
во. вчера напрямую соединялось. сейчас не хочет даже после сброса state/cache/etc. IPv4 работают ноды не говоря уж о IPv6
C:\TOR\_arti\x86_64-msvc>arti-testing.exe connect -c config.toml
http://imageshack.com/a/img922/7199/6i95qH.png
2024-06-09T23:51:25.005939Z DEBUG tor_circmgr::hspool: launching 3 SHORT and 1 EXTENDED circuits
Outcome: Err(TimeoutError)
TCP stats: TcpCount { n_connect_attempt: 15, n_connect_ok: 4, n_accept: 0, n_bytes_send: 478066, n_bytes_recv: 4304728 }
Total events: Trace: 8593, Debug: 79, Info: 8, Warn: 1, Error: 0
|
|
|
|
artenax
Стаж: 2 года 11 месяцев Сообщений: 1714
|
artenax ·
10-Июн-24 04:19
(спустя 1 час 7 мин.)
LeonMskRu
У меня напрямую тоже больше не соединяется. У себя в логах вижу ipv6, на йоте эти адреса в блоке.
|
|
|
|
LeonMskRu
Стаж: 17 лет 10 месяцев Сообщений: 88
|
LeonMskRu ·
10-Июн-24 10:00
(спустя 5 часов, ред. 10-Июн-24 10:00)
да там как выше писал "через раз"
раньше так только snowflake работал
мог то мгновенно зацепиться. то весь день без толку долбится
и с IPv6 у них какие то глюки временами. тупо проверяю
https://test-ipv6.com/ https://ipv6-test.com/
бывает работает. а может и какие то левые SOCKS ERROR
вот ни конфиги не трогал. ни пересобирал .EXE
C:\TOR\_arti\x86_64-msvc>connection-checker.exe
Testing direct Tor connection...
Node: [217. .76:8443 ed25519:E4tm0PTz3IbbxCpP9f7FxFibd24FH6HFk4BVQ8ONLOk $d2add68ba9f735031893cb8a58548375e831b45b]
Node: [5. .104:9001 ed25519:JLEz7FP+12HKDcRAhih4iw+QdVBX7xe1zHdRvoovMp0 $1cd59a9804d3ffd877a5cdb58f0f1943caf4da4b]
Node: [192. .209:9003+ ed25519:d9u1dW3PJfFvzcxwOpCyCubigHEi2JHSI85WbDD32+U $8d7cec67216e5b08371d6538ba6f5a504ab6ccb4]
direct Tor connection successful!
C:\TOR\_arti\x86_64-msvc>arti-testing.exe connect -c config.toml
2024-06-10T05:54:08.901720Z DEBUG arti_client::status: 100%: connecting successfully; directory is usable, fresh until 2024-06-10 06:00:00 UTC, and valid until 2024-06-10 08:00:00 UTC
Outcome: Ok(Ok(()))
TCP stats: TcpCount { n_connect_attempt: 10, n_connect_ok: 3, n_accept: 0, n_bytes_send: 483317, n_bytes_recv: 4290931 }
Total events: Trace: 8626, Debug: 84, Info: 9, Warn: 1, Error: 0
спасибо северянин
IPv6 Bridges
https://github.com/LeonMskRu/arti_windows/tree/main/torrc
Countrys == de nl fr fi lu se gb ch ro no cz ru bg dk it is es at hu gr be ie hr pt
+Guard +Fast +Stable
-Exit -HSDir
рабочие на момент сканирования/выкладывния с Ростелеком/Калуга с IPv6 (не teredo)
|
|
|
|
artenax
Стаж: 2 года 11 месяцев Сообщений: 1714
|
artenax ·
11-Июн-24 17:37
(спустя 1 день 7 часов, ред. 11-Июн-24 18:08)
Недавно в логе увидел
Код:
Questionable guard: 51.4% of circuits died under mysterious circumstances
Код:
Сомнительный охранник: 51,4% цепей погибли при загадочных обстоятельствах
|
|
|
|
LeonMskRu
Стаж: 17 лет 10 месяцев Сообщений: 88
|
LeonMskRu ·
15-Июн-24 08:25
(спустя 3 дня, ред. 15-Июн-24 08:25)
я вот только сегодня заметил что оно похоже то ли слишком оптимистично
то ли ТСПУ на лету что то блочит
ибо написало найден Guard 1.2.3.4
и тут же что Guard 1.2.3.4 что то там "недоступен"
а еще connection-checker.exe / arti-testing.exe connect / arti.exe proxy == могут выдавать разные результаты в плане "успеха"
добавили
relay = ["arti-relay", "__is_experimental"]
experimental = ["arti-client/experimental", "experimental-api", "rpc", "relay"]
2024 06 14
fix OOM ?!
Limit the number of mds that we will fetch from sqlite at once.
https://github.com/LeonMskRu/arti_windows/releases/tag/1.2.4-24-06-14
пересобрал транспорты и для x86_64 и вроде как для i686
https://github.com/LeonMskRu/arti_windows/raw/main/_arti_20240614_1621.rar
# M:\_Microsoft\_MSYS2\usr\bin\ldd.exe client-32.exe
ntdll.dll => /c/windows/SYSTEM32/ntdll.dll (0x7ff8f76b0000)
ntdll.dll => /c/Windows/SysWOW64/ntdll.dll (0x77a60000)
wow64.dll => /c/windows/System32/wow64.dll (0x7ff8f64a0000)
wow64win.dll => /c/windows/System32/wow64win.dll (0x7ff8f7510000)
# M:\_Microsoft\_MSYS2\usr\bin\ldd.exe client-64.exe
ntdll.dll => /c/windows/SYSTEM32/ntdll.dll (0x7ff8f76b0000)
KERNEL32.DLL => /c/windows/System32/KERNEL32.DLL (0x7ff8f75b0000)
KERNELBASE.dll => /c/windows/System32/KERNELBASE.dll (0x7ff8f5200000)
apphelp.dll => /c/windows/SYSTEM32/apphelp.dll (0x7ff8f2410000)
lyrebird-32.exe: PE32 executable (console) Intel 80386, for MS Windows, 6 sections
lyrebird-64.exe: PE32+ executable (console) x86-64, for MS Windows, 8 section
2024-06-15
вот про эту фигню писал. опять/снова. 10 минут долбится в ДВА неработающих OBFS4. прописано 20+
2024-06-15T04:53:47Z WARN tor_circmgr: Problem launching a timeout testing circuit: error: Unable to select a guard relay: No usable guards. Rejected 20/40 as down, then 0/20 as pending, then 20/20 as unsuitable to purpose, then 0/0 with filter.
скрытый текст
Код:
2024/06/15 07:43:37 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:43:47 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:43:57 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:44:07 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:44:17 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:44:27 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:44:37 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:44:47 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:44:57 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:45:07 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:45:17 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:45:27 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:45:37 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:45:48 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:45:58 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:46:08 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:46:18 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:46:28 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:46:38 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:46:48 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:46:58 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:47:08 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:47:18 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:47:28 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:47:38 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:47:48 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:47:58 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:48:08 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:48:18 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:48:28 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:48:38 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:48:48 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:48:58 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:49:08 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:49:18 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:49:28 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:49:38 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:49:48 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:49:58 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:50:08 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:50:18 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:50:28 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:50:38 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:50:48 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:50:58 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:51:08 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:51:18 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:51:28 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:51:38 [ERROR]: obfs4(185.177.207.153:8443) - outgoing connection failed: dial tcp 185.177.207.153:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:43:11 [WARN]: obfs4(185.177.207.249:11249) - closed connection: writeto tcp 127.0.0.1:31306->127.0.0.1:31332: read tcp 127.0.0.1:31306->127.0.0.1:31332: wsarecv: An existing connection was forcibly closed by the remote host.
2024/06/15 07:43:37 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:43:47 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:43:57 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:44:07 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:44:17 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:44:27 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:44:37 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:44:47 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:44:57 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:45:07 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:45:17 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:45:27 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:45:37 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:45:48 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:45:58 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:46:08 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:46:18 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:46:28 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:46:38 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:46:48 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:46:58 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:47:08 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:47:18 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:47:28 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:47:38 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:47:48 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:47:58 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:48:08 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:48:18 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:48:28 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:48:38 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:48:48 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:48:58 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:49:08 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:49:18 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:49:28 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:49:38 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:49:48 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:49:58 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:50:08 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:50:18 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:50:28 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:50:38 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:50:48 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:50:58 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:51:08 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:51:18 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:51:28 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:51:38 [ERROR]: obfs4(209.250.251.53:33497) - outgoing connection failed: dial tcp 209.250.251.53:33497: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 07:42:50 [ERROR]: obfs4(45.131.46.103:443) - outgoing connection failed: handshake: ntor AUTH mismatch: Derived: 3083ffdda983c9e6db4a10c4266dc74935e3a3e0204011a847374ffd7ddc86ac Received:29571ed320e1f16aa2f42c924472f88ff49cec5721378820f25aca96e1aa1231.
2024/06/15 07:42:50 [ERROR]: obfs4(45.131.46.103:443) - outgoing connection failed: handshake: ntor AUTH mismatch: Derived: 6b48742b22e021ef47a8714ce34624529174a8c24463a5384c4d40c50495581c Received:36e382bb85e9cca5a76b62af308c5c23afb766fb6197f6b9cba3081eaebef130.
2024/06/15 07:42:49 [ERROR]: obfs4(45.131.46.103:443) - outgoing connection failed: handshake: ntor AUTH mismatch: Derived: 8c6cc2e41f447143afbb75523fbe61d6b99a61676f848346f2252f6da05a737d Received:c230039ed101ed057d77c34b7f231fcddbd8f57207a5e824e6cd0405306e125c.
2024/06/15 07:42:51 [ERROR]: obfs4(45.131.46.103:443) - outgoing connection failed: handshake: ntor AUTH mismatch: Derived: 9f05de5c1b220c355e635b1f613409e58c1ec7d272b02821d9c934b2e399f0c0 Received:81890bfb28086861f4c70273749b09f44aa7e4aba8c89b464cc6e036099b03ea.
2024/06/15 07:42:49 [ERROR]: obfs4(45.131.46.103:443) - outgoing connection failed: handshake: ntor AUTH mismatch: Derived: ddfc4189ec0ab600e271098530c8fbacdec1c0e83f0da3c1b87ca7d55595be08 Received:b9233cbd34916c2a0cfaf0a6bb261f510a017c51a9f09f5e688defd4bd017c8e.
2024/06/15 07:42:58 [ERROR]: obfs4(77.68.118.55:443) - outgoing connection failed: handshake: ntor AUTH mismatch: Derived: 1216c0141d45ecd30e67e9459c2008ee13b63919c28d8d590027b027fa4cb7f4 Received:ed50e9dd3d08fa60f5484781a7fae7166c9a24c8a07c30734cbf98c47cc3ab1b.
2024/06/15 07:43:01 [ERROR]: obfs4(77.68.118.55:443) - outgoing connection failed: handshake: ntor AUTH mismatch: Derived: 234b2891d9b10645b246cbfecc9cbdcf9acbe2a9fbbe9fbf1173e2d1f85d0bad Received:086bc0988a8ed6a5727a7e0056d0039d9837428d23cee5ba6adbc07bce9efbcb.
2024/06/15 07:42:58 [ERROR]: obfs4(77.68.118.55:443) - outgoing connection failed: handshake: ntor AUTH mismatch: Derived: 4722ed33c108c49330d9756b4a055cee925a4101a8b009df3abcf60f66a65fbf Received:2d6ba4298079368875d0d9888681577834ccdbae3aa4c0da0e6442685f7dbf1d.
2024/06/15 07:43:01 [ERROR]: obfs4(77.68.118.55:443) - outgoing connection failed: handshake: ntor AUTH mismatch: Derived: 9faab758b10b216e303defc0c08cae040303418fe6cc67edfb804a3d8c7c7736 Received:4c809eed7c639087e7b86cf57c8aae20b980583d12b0f705499f7b09b22f0265.
2024/06/15 07:42:57 [ERROR]: obfs4(77.68.118.55:443) - outgoing connection failed: handshake: ntor AUTH mismatch: Derived: b6dd31912f3b92af9a0736ba05b2aef1eac4cbb8e3333c841797e4baa55fe043 Received:2275604ac27f47014699aeb4b68d3c0ffdb92fd20b69b430722c60666acb5590.
2024/06/15 07:42:57 [ERROR]: obfs4(77.68.118.55:443) - outgoing connection failed: handshake: ntor AUTH mismatch: Derived: cea5f2e4dbae69fbb1a6b25f66aa4aad406ed8e143c8119aea867949e0fc25fb Received:9a5ef0a72f2cf3ef942066271da65eefd89cc733492a35f8ac5e3bc88af15528.
удалил часть мостов.
оставил на 10 минут.. теже тамже
два моста
причем уже было 10+ тикетов про "залипающие" мосты
скрытый текст
Код:
2024/06/15 08:02:19 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:02:29 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:02:41 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:02:51 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:03:12 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:03:22 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:04:15 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:04:48 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:05:01 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:05:13 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:05:36 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:05:53 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:06:12 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:06:22 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:06:41 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:06:51 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:07:14 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:07:26 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:07:55 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:08:07 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:08:23 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:08:44 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:09:09 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:09:21 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:09:31 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:09:41 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:09:51 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:10:01 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:10:11 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:11:16 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:01:48 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:01:50 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:01:53 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:01:56 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:02:20 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:02:42 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:02:48 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:02:50 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:03:13 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:03:16 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:03:21 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:03:23 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:03:33 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:03:35 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:03:39 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:03:41 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:03:45 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:03:47 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:03:51 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:03:53 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:04:07 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:04:11 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:04:14 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:04:20 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:04:22 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:04:27 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:04:40 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:04:52 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:05:05 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:05:07 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:05:11 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:05:13 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:05:28 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:05:44 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:05:48 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:05:50 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:06:14 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:06:16 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:06:19 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:06:42 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:06:47 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:06:49 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:06:53 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:07:05 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:07:17 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:07:20 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:07:25 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:07:27 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:07:34 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:07:46 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:07:59 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:08:01 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:08:15 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:08:19 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:08:22 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:08:28 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:08:31 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:08:35 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:08:48 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:09:00 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:03 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:06 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:09 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:12 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:15 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:18 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:20 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:24 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:27 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:30 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:33 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:37 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:39 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:44 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:46 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:50 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:52 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:11:07 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:11:26 [ERROR]: obfs4([2a01:440:108:11:82:149:227:122]:443) - outgoing connection failed: dial tcp [2a01:440:108:11:82:149:227:122]:443: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:02:15 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:02:46 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:02:56 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:03:09 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:03:51 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:04:06 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:04:27 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:05:40 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:06:04 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:06:31 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:06:41 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:06:54 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:07:48 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:08:09 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:08:32 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:08:50 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:09:48 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:09:58 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:10:38 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:11:06 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024/06/15 08:01:48 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:01:50 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:01:54 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:02:06 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:02:08 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:02:13 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:02:15 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:02:25 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:02:47 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:03:00 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:03:05 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:03:07 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:03:14 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:03:16 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:03:30 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:03:42 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:03:45 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:03:58 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:04:01 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:04:03 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:04:26 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:04:34 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:04:37 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:04:48 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:04:50 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:04:54 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:04:56 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:05:01 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:05:03 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:05:08 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:05:11 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:05:19 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:05:31 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:05:34 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:05:56 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:05:59 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:06:02 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:06:06 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:06:08 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:06:32 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:06:45 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:06:47 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:06:51 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:06:53 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:06:58 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:07:00 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:07:07 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:07:09 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:07:20 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:07:23 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:07:39 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:07:48 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:08:00 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:08:03 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:08:06 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:08:08 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:08:24 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:08:29 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:08:41 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:08:44 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:08:48 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:08:50 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:08:54 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:08:56 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:09:01 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:09:03 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:09:14 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:09:16 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:09:49 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:09:51 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:09:55 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:09:57 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:01 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:04 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:09 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:12 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:30 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:10:58 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:11:01 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:11:04 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:11:08 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:11:10 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:11:14 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:11:27 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
2024/06/15 08:11:29 [ERROR]: obfs4([2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831) - outgoing connection failed: dial tcp [2a03:4000:7:61b:6424:d1ff:feda:25c6]:62831: connectex: No connection could be made because the target machine actively refused it.
почистил и cache\ и state\
немного проверило разные мосты
но опять/снова только 2а моста "проверяет" 5+ минут
скрытый текст
Код:
08:13:17[ERROR]:obfs4(108.175.13.9:443)
08:13:16[ERROR]:obfs4(95.216.205.148:443)
08:13:18[ERROR]:obfs4([2001:8d8:1800:86a1::1]:443)
08:13:14[ERROR]:obfs4([2001:8d8:1800:86a1::1]:443)
08:13:21[ERROR]:obfs4([2001:8d8:1800:86a1::1]:443)
08:13:31[ERROR]:obfs4([2001:8d8:1800:86a1::1]:443)
08:13:13[ERROR]:obfs4([2001:8d8:1800:86a1::1]:443)
08:13:21[ERROR]:obfs4([2001:8d8:1800:86a1::1]:443)
08:13:31[ERROR]:obfs4([2001:8d8:1800:86a1::1]:443)
08:13:25[ERROR]:obfs4([2001:8d8:1800:86a1::1]:443)
08:13:18[ERROR]:obfs4([2001:8d8:1800:86a1::1]:443)
08:13:15[ERROR]:obfs4([2001:8d8:1800:86a1::1]:443)
08:13:15[ERROR]:obfs4([2001:8d8:1800:86a1::1]:443)
08:13:24[ERROR]:obfs4([2001:8d8:1800:86a1::1]:443)
08:13:41[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:13:51[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:14:01[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:14:11[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:14:21[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:14:31[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:14:41[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:14:51[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:15:01[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:15:11[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:15:21[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:15:31[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:15:41[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:15:51[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:16:01[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:16:11[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:16:21[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:16:31[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:16:41[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:16:51[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:17:01[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:17:11[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:17:21[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:17:31[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:17:41[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:17:51[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:18:01[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:18:11[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:18:21[ERROR]:obfs4([2a00:e67:200:ff43:44bc:c153:f34e:1746]:443)
08:13:57[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:14:07[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:14:17[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:14:27[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:14:37[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:14:47[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:14:57[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:15:07[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:15:17[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:15:27[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:15:37[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:15:47[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:15:57[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:16:07[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:16:17[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:16:27[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:16:37[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:16:47[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:16:57[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:17:07[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:17:17[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:17:27[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:17:37[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:17:47[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:17:57[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:18:07[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
08:18:17[ERROR]:obfs4([2a02:8010:6953:0:b7c9:e906:e4cb:74cf]:443)
|
|
|
|
LeonMskRu
Стаж: 17 лет 10 месяцев Сообщений: 88
|
LeonMskRu ·
15-Июн-24 08:50
(спустя 24 мин., ред. 15-Июн-24 08:50)
взял рабочие (проверил в tor/TCP) obfs4
вобщем ждем 2.0+ ?:)
скрытый текст
Код:
08:35:28[ERROR]:obfs4(87.106.193.253:443)
08:35:24[ERROR]:obfs4(87.106.193.253:443)
08:35:25[ERROR]:obfs4(87.106.193.253:443)
08:35:26[ERROR]:obfs4(87.106.193.253:443)
08:35:24[ERROR]:obfs4(87.106.193.253:443)
08:34:48[ERROR]:obfs4(87.106.193.253:443)
08:34:48[ERROR]:obfs4(87.106.193.253:443)
08:35:33[ERROR]:obfs4(87.106.193.253:443)
08:35:28[ERROR]:obfs4(87.106.193.253:443)
08:35:00[ERROR]:obfs4([2001:41d0:305:2100::48e8]:443)
08:34:54[ERROR]:obfs4([2001:41d0:305:2100::48e8]:443)
08:34:57[ERROR]:obfs4([2001:41d0:305:2100::48e8]:443)
08:34:54[ERROR]:obfs4([2001:41d0:305:2100::48e8]:443)
08:35:13[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:35:26[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:35:43[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:36:06[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:36:33[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:36:48[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:37:03[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:37:22[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:37:38[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:38:21[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:35:04[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:35:18[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:35:22[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:35:34[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:35:37[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:35:40[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:35:42[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:35:57[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:36:01[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:36:03[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:36:07[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:36:09[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:36:24[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:36:39[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:36:42[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:36:55[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:36:57[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:37:01[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:37:13[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:37:16[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:37:29[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:37:34[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:37:36[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:37:39[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:37:41[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:37:46[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:37:48[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:37:54[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:37:56[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:38:00[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:38:12[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:38:14[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:38:18[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:38:30[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
08:38:33[ERROR]:obfs4([2a01:440:108:11:82:149:227:122]:443)
да. иногда и у меня соединяется. но вот именно что ИНОГДА. ничего не меняешь а оно или не работает или криво работает ну или коннектится
http://imageshack.com/a/img923/41/HkI74m.png
http://imageshack.com/a/img924/9889/RvfEl7.png
|
|
|
|
artenax
Стаж: 2 года 11 месяцев Сообщений: 1714
|
artenax ·
15-Июн-24 14:21
(спустя 5 часов)
Я бы использовал пару гарантированно работающих obfs4. Похоже, arti не нравится, когда много вписано.
|
|
|
|
LeonMskRu
Стаж: 17 лет 10 месяцев Сообщений: 88
|
LeonMskRu ·
20-Июн-24 19:03
(спустя 5 дней, ред. 20-Июн-24 19:03)
ну 2а это вообще ниочем
на 4х заработало (2 IPv4 + 2 IPv6). так оно и при 10-20 иногда работает.
не говоря о том чтобы следить за всем этим когда очередной мост "умрет"...
на 10 IPv4 без чистки кэша "заработало" (тупо нашло 2а старых моста.)
на 10 IPv4 + удаленный кэш "работает" но ошибки лога как то нифига не радуют
2024-06-15T14:49:29Z INFO tor_dirmgr: Marked consensus usable.
2024-06-15T14:49:29Z INFO tor_dirmgr: We have enough information to build circuits.
2024-06-15T14:49:29Z INFO arti: Sufficiently bootstrapped; system SOCKS now functional.
2024-06-15T14:49:48Z INFO tor_guardmgr::guard: We have found that guard [ :443 via obfs4 ed25519:7v7zqZT+8+NR4FfPU53ePo0Cj+YUrx1NMokiW73Z3VE $cafdb3585f1675c07b8f9a2383bfcceb148a97d7] is usable.
2024-06-15T14:50:29Z WARN tor_circmgr::mgr: All circuit attempts failed due to timeout
2024-06-15T14:50:29Z WARN tor_circmgr::mgr: Request failed
2024-06-15T14:50:29Z WARN arti::socks: connection exited with error: error: tor operation timed out
нашел еще форк tor-relay-scanner на GO
https://github.com/juev/tor-relay-scanner-go
есть -4/-6 опции запуска
хотя с моими JSON что то глючит. может на обычном режиме проблем нет ...
здесь то ему что не нравитца
2024-06-16T07:55:03Z INFO tor_guardmgr::guard: We have found that guard [[2001: :99d8]:443 via webtunnel ed25519:zl7GX20RxwckZCqO+aXAGvatJWpSsMMwJr4ZDFArRWA $e4b91c347d685e929c1b7ce84cc27eb073127ea6] is usable.
2024-06-16T07:55:09Z INFO tor_guardmgr::guard: We have found that guard [[2001: :ecf9]:443 via webtunnel ed25519:zYBTkmyJfrBR5x3wQ6nJ1R628YuI6FAAbFdI3+Hhcgk $78f3fed4fc8d8111b6c1f18660d2a79fa65dd7a4] is usable.
скрытый текст
Код:
2024/06/16 10:55:47 copy loop ended
2024/06/16 10:55:47 Handler ended
2024/06/16 10:55:47 copying SOCKS to webtunnel resulted in error: read tcp 127.0.0.1:37913->127.0.0.1:37932: use of closed network connection 2024/06/16 10:55:47 copy loop ended
2024/06/16 10:55:47 Handler ended
2024/06/16 10:55:47 copying SOCKS to webtunnel resulted in error: read tcp 127.0.0.1:37913->127.0.0.1:37990: use of closed network connection 2024/06/16 10:55:49 copy loop ended
2024/06/16 10:55:49 Handler ended
2024/06/16 10:55:49 copying SOCKS to webtunnel resulted in error: read tcp 127.0.0.1:37913->127.0.0.1:38009: use of closed network connection 2024/06/16 10:55:49 copy loop ended
2024/06/16 10:55:49 Handler ended
2024/06/16 10:55:49 copying SOCKS to webtunnel resulted in error: read tcp 127.0.0.1:37913->127.0.0.1:37994: use of closed network connection 2024/06/16 10:55:50 copy loop ended
2024/06/16 10:55:50 Handler ended
2024/06/16 10:55:50 copying SOCKS to webtunnel resulted in error: read tcp 127.0.0.1:37913->127.0.0.1:38024: use of closed network connection 2024/06/16 10:55:51 copy loop ended
2024/06/16 10:55:51 Handler ended
2024/06/16 10:55:51 copying SOCKS to webtunnel resulted in error: read tcp 127.0.0.1:37913->127.0.0.1:38034: use of closed network connection 2024/06/16 10:55:51 copy loop ended
2024/06/16 10:55:51 Handler ended
2024/06/16 10:55:51 copying SOCKS to webtunnel resulted in error: read tcp 127.0.0.1:37913->127.0.0.1:38050: use of closed network connection 2024/06/16 10:55:52 copy loop ended
2024/06/16 10:55:52 Handler ended
2024/06/16 10:55:52 copying SOCKS to webtunnel resulted in error: read tcp 127.0.0.1:37913->127.0.0.1:38073: use of closed network connection 2024/06/16 10:55:52 copy loop ended
2024/06/16 10:55:52 Handler ended
2024/06/16 10:55:52 copying SOCKS to webtunnel resulted in error: read tcp 127.0.0.1:37913->127.0.0.1:38076: use of closed network connection 2024/06/16 10:55:54 copy loop ended
2024/06/16 10:55:54 Handler ended
2024/06/16 10:55:54 copying SOCKS to webtunnel resulted in error: read tcp 127.0.0.1:37913->127.0.0.1:38096: use of closed network connection 2024/06/16 10:55:55 copy loop ended
2024/06/16 10:55:55 Handler ended
2024/06/16 10:55:55 copying SOCKS to webtunnel resulted in error: read tcp 127.0.0.1:37913->127.0.0.1:38135: use of closed network connection 2024/06/16 10:55:56 copy loop ended
2024/06/16 10:55:56 Handler ended
2024/06/16 10:55:56 copying SOCKS to webtunnel resulted in error: read tcp 127.0.0.1:37913->127.0.0.1:38149: use of closed network connection 2024/06/16 10:55:56 copy loop ended
2024/06/16 10:55:56 Handler ended
2024/06/16 10:55:56 copying SOCKS to webtunnel resulted in error: read tcp 127.0.0.1:37913->127.0.0.1:38154: use of closed network connection 2024/06/16 10:55:57 copy loop ended
2024/06/16 10:55:57 Handler ended
2024/06/16 10:55:57 copying SOCKS to webtunnel resulted in error: read tcp 127.0.0.1:37913->127.0.0.1:38169: use of closed network connection 2024/06/16 10:55:57 copy loop ended
2024/06/16 10:55:57 Handler ended
2024/06/16 10:55:57 copying SOCKS to webtunnel resulted in error: read tcp 127.0.0.1:37913->127.0.0.1:38170: use of closed network connection 2024/06/16 10:55:59 copy loop ended
2024/06/16 10:55:59 Handler ended
2024/06/16 10:55:59 copying SOCKS to webtunnel resulted in error: read tcp 127.0.0.1:37913->127.0.0.1:38190: use of closed network connection 2024/06/16 10:59:06 copy loop ended
2024/06/16 10:59:06 Handler ended
2024/06/16 10:59:06 copying SOCKS to webtunnel resulted in error: read tcp 127.0.0.1:37913->127.0.0.1:37949: use of closed network connection 2024/06/16 11:00:22 copy loop ended
2024/06/16 11:00:22 Handler ended
2024/06/16 11:00:22 copying SOCKS to webtunnel resulted in error: read tcp 127.0.0.1:37913->127.0.0.1:38113: use of closed network connection
узнал что
и
это разное ;\
2024-06-19 что то сломал у себя в сборке. было наоборот. но сейчас не работает (куча ошибок самых разных)
M:\_Microsoft\_MSYS2\ucrt64\bin\gcc.exe
M:\_Microsoft\_MSYS2\mingw64\bin\gcc.exe
M:\_Microsoft\_MSYS2\mingw64\bin\x86_64-w64-mingw32-gcc.exe
M:\_Microsoft\_MSYS2\mingw32\bin\gcc.exe
M:\_Microsoft\_MSYS2\mingw32\bin\i686-w64-mingw32-gcc.exe
[target.x86_64-pc-windows-gnu]
rustflags = ["-C", "target-feature=+crt-static"]
linker = "x86_64-w64-mingw32-gcc.exe"
ar = "x86_64-w64-mingw32-gcc-ar.exe"
#linker = "M:\\_Microsoft\\_msys2\\ucrt64\\bin\\gcc.exe"
#ar = "M:\\_Microsoft\\_msys2\\ucrt64\\bin\\ar.exe"
[target.i686-pc-windows-gnu]
rustflags = ["-C", "target-feature=+crt-static"]
linker = "i686-w64-mingw32-gcc.exe"
ar = "i686-w64-mingw32-gcc-ar.exe"
#linker = "M:\\_Microsoft\\_msys2\\mingw32\\bin\\gcc.exe"
#ar = "M:\\_Microsoft\\_msys2\\mingw32\\bin\\ar.exe"
2024-06-20
https://github.com/LeonMskRu/arti_windows/releases/tag/1.2.4
|
|
|
|
artenax
Стаж: 2 года 11 месяцев Сообщений: 1714
|
artenax ·
21-Июн-24 08:22
(спустя 13 часов, ред. 21-Июн-24 08:44)
Скомпилировал Arti 1.2.4 + 11 утилит для Linux 32 и 64 бит. Полустатик. Будет работать даже на старых дистрах (Ubuntu 16.04+ / 2016+), на процессорах без SSE3/4/AVX.
Код:
Arti 1.2.4
Rust 1.79.0 (2024-06-10)
Ubuntu 16.04.7+ (2016+)
glibc (libc6) 2.23+
libstdc++6 / gcc 5.4.0+ (>=libstdc++.so.6.0.21)
OpenSSL 3.3.0 (internal), sqlite (internal)
x86_64-unknown-linux-gnu (x86-64-v1, without avx/sse4)
i686-unknown-linux-gnu (sse2 allowed, sse3 disabled)
+ 11 utilities: arti-bench, arti-testing, connection-checker, dns-resolver, download-manager, fixup-features, hyper-http-client-example, hyper-http-hs-example, keygen-openssh-test, obfs4-checker, pt-proxy
Зависимости
Код:
readelf -d arti
Динамический раздел со смещением 0x1809130 содержит 33 элемента:
Тег Тип Имя/Знач
0x0000000000000001 (NEEDED) Совм. исп. библиотека: [liblzma.so.5]
0x0000000000000001 (NEEDED) Совм. исп. библиотека: [libgcc_s.so.1]
0x0000000000000001 (NEEDED) Совм. исп. библиотека: [librt.so.1]
0x0000000000000001 (NEEDED) Совм. исп. библиотека: [libpthread.so.0]
0x0000000000000001 (NEEDED) Совм. исп. библиотека: [libm.so.6]
0x0000000000000001 (NEEDED) Совм. исп. библиотека: [libdl.so.2]
0x0000000000000001 (NEEDED) Совм. исп. библиотека: [libc.so.6]
Опции сборки
Код:
git clone --depth 1 --branch arti-v1.2.4 https://gitlab.torproject.org/tpo/core/arti.git
cd arti
git submodule update --init --recursive --depth=1
RUSTFLAGS="-C target-feature=-sse3" cargo build --release --jobs 1 --features static --target=i686-unknown-linux-gnu
strip --strip-unneeded *
git clone --depth 1 --branch arti-v1.2.4 https://gitlab.torproject.org/tpo/core/arti.git
cd arti
git submodule update --init --recursive --depth=1
cargo build --release --jobs 1 --features static
strip --strip-unneeded *
https://github.com/artenax/tor/releases/tag/arti
https://github.com/artenax/tor/releases/download/arti/arti-1.2.4-linux32-64.7z
LeonMskRu писал(а):
86297358obfs4-checker
сейчас попробую собрать несколько наборов
Finished release profile [optimized] target(s) in 22m 53s
это только один из 4х вариантов 
Так там же в каждую утилиту весь arti вшивается. Собирать лучше сразу всё (т.е. не дописывать -p arti).
Потестил только dns-resolver. Мне понравилось. Указываешь dns-resolver google.com. Он тебе в ответ IP. Правда долго, ведь arti вызывается каждый раз.
Upd: Для сборки поднял две Lubuntu 16.04 в виртуалке 32 и 64 бит. Эх, какой же легкий был LXDE GTK2, не то что сейчас дистры и DE
Хотел отключить sse2 для 32 бит для лучшей совместимости со старьем (мало ли), но компонент ring хочет sse2.
Кстати, совместимость с Win7 народу была бы полезна. Хотя, ее не получится вечно тянуть. Rust отказался от Win7.
|
|
|
|
