Any users have issues with Tor Bridge site not retrieving obfs4 bridges?
There is only one bridge address being returned, interestingly.
2 Likes
You are right there was a problem in our BridgeDB and it was handing only one bridge on each request. Thank you for finding the issue.
2 Likes
Has this issue been resolved?
1 Like
This issue still appears to be active last time I checked.
2 Likes
I checked a few times and while the bridges were different, only one at a time is being handed out, unlike it used to be last time I checked where it would hand out 3 at a time.
1 Like
It looks like BridgeDB is hitting a recurrent issue with this. We have ready a replacement for the HTTPS distributor as part of rdsys, I hope to deploy it soon so we don’t continue hitting this problem.
2 Likes
can you explain what is rdsys?
1 Like
rdsys:
Distribution system for circumvention proxies and related resources. BridgeDB’s successor.
1 Like
what is the current recommended way to connect to a bridge using a pluggable transport?
1 Like
Try the second option:
Otherwise, try the fourth option:
What is rdsys and what is the timeline for it’s deployment?
1 Like
I webtunnel the recommended pluggable transport?
1 Like
From the README.md:
Not sure about the timeline for deployment.
Use whichever pluggable transport required for censorship circumvention to access the Tor network.
rdsys is already deployed for some distributors (telegram & settings), but for the rest we are planning to deploy it over this current month.
1 Like
webtunnel is still under development, is really useful for us if people try it but if you are searching for something stable use obfs4 or snowflake depending on what works better on your location. TorBrowser should be able to pick the right PT for your location automatically.
1 Like
I appreciate your advice sir, obfs4 protocol is being blocked by ISP. For you information. The ISP is able to fingerprint and block the initial connection. This is Chinese mainland.