Semi-broken connection to one of three bridges leads to poor performance and bugs
Tor Browser 13.0.13. Tor tries to connect to all bridges at once and slows down to the lowest performance with:
2024-04-01 01:47:56.444 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with 185.11.136.232:9003 ID=ZvxQhFudo2hIwCfqzQAhuJJUOoDetKpgIaZEx8YdOts RSA_ID=93B2F5EEB126C38D080621B3C7F8BA03C9533D72 ("general SOCKS server failure")
2024-04-01 01:47:57.730 [NOTICE] Failed to find node for hop #1 of our path. Discarding this circuit.
2024-04-01 01:47:57.730 [NOTICE] Our circuit 0 (id: 1033) died due to an invalid selected path, purpose Unlinked conflux circuit. This may be a torrc configuration issue, or a bug. [1 similar message(s) suppressed in last 31080 seconds]
2024-04-01 01:47:57.732 [WARN] Proxy Client: unable to connect OR connection (handshaking (proxy)) with 185.11.136.232:9003 ID=ZvxQhFudo2hIwCfqzQAhuJJUOoDetKpgIaZEx8YdOts RSA_ID=93B2F5EEB126C38D080621B3C7F8BA03C9533D72 ("general SOCKS server failure")
2024-04-01 01:53:57.542 [NOTICE] new bridge descriptor 'uierhgerogrehjgte' (fresh): $93B2F5EEB126C38D080621B3C7F8BA03C9533D72~uierhgerogrehjgte [ZvxQhFudo2hIwCfqzQAhuJJUOoDetKpgIaZEx8YdOts] at 185.11.136.232 and [2a00:17d8:100:1::fc1]