![]() etc.Ĭan you provide an example? Upcoming Events (Can't connect to bridge PT_MISSING count 1 recommendation warn host )Ģ/10/21, 21:19:23.700 We were supposed to connect to bridge ''. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.Ģ/10/21, 21:19:23.540 Problem bootstrapping. ![]() Shutting down all existing connections.Ģ/10/21, 21:19:22.790 Opening Socks listener on 127.0.0.1:9150Ģ/10/21, 21:19:22.790 Opened Socks listener on 127.0.0.1:9150Ģ/10/21, 21:19:22.790 CreateProcessA() failed: The system cannot find the file specified.Ģ/10/21, 21:19:22.791 Pluggable Transport process terminated with status code 0Ģ/10/21, 21:19:22.791 Failed to start process: (null)Ģ/10/21, 21:19:22.791 Managed proxy at 'TorBrowser\Tor\PluggableTransports\obfs4proxy.exe' failed at launch.Ģ/10/21, 21:19:23.540 We were supposed to connect to bridge '' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. Tor will not make or accept non-control network connections. Shutting down all existing connections.Ģ/10/21, 21:19:22.790 DisableNetwork is set. NET security update (KB4601056) - removing these through system restore didn't improve the situation though (SSU's cannot generally be uninstalled though, so I have a hunch saying that SSU KB4592449 can be the cause).Īre the pluggable transports malfunctioning in v10.0.11 (starting today?), under general attack today or are we seeing or are we seeing an unwanted impact from Microsoft Updates?Ģ/10/21, 21:19:22.789 DisableNetwork is set. ![]() ![]() The only thing these installations had in common was the latest Windows Update SSU (KB4592449) and. Only direct connection to Tor through entry guard works (partially - not all the time). As of today (Feb.11) pluggable transport (obfs4) ceases to function on multiple (win10 圆4 and x86) installations.
0 Comments
Leave a Reply. |