Bridges requested in TB do not work, only the ones built in

Support Censorship Circumvention
1

Hello!
For quite a while now bridges requested from within Tor Browser do not connect while the ones built in work fine. Also copying these obfs4 addresses into tails leads to the same result. No connection, log says “general SOCKS server failure”. Requesting bridges from bridges.torproject.org yields working ones.

I tried re-installing TorBrowser but same result on several machines running Ubuntu LTS. I do not live in a country that blocks Tor.

1 Like
2

Hi, @Bernd_Lauert, could you share the bridges that you’ve tried? Please avoid posting the bridge line here. Instead, follow these steps and share the link of Tor Metrics:

  1. Get the fingerprint of the bridge.
  2. Enter the bridge fingerprint here: Relay Search
  3. Then, share the link with us.
2 Likes
3

Hello @gus
Relay search returns ‘no results found’ for the non-working bridges received via moat.

https://metrics.torproject.org/rs.html#search/CD98896007D51B55D866E4D0404084C35418D3E2

https://metrics.torproject.org/rs.html#search/A735952E93D558A671F7DAD65E4D7FD8C9CC3472

1 Like
4

Only allowed to post 2 links, here’s the 3rd relay:
https://metrics.torproject.org/rs.html#search/EF90E8915F13FCBC053EE7CF3ABB71F0DFB7D0C9

1 Like
5

Thanks for reporting this issue. I tested locally and saw the same behavior.
I filled up a ticket for the AC-Team:

3 Likes
6

It looks like we made a mistake and were distributing bad bridges, the situation is reversed now and we should be providing better bridges now.

Sorry for the problem.

3 Likes