[tor-dev] Failure to connect to a bridge--downgrading to fixes it

David Fifield david at bamsoftware.com
Fri Dec 7 05:19:09 UTC 2018

Here, a user reported a failure to connect to their own bridge, stopping
at 25% bootstrapped. teor and I went through the basic troubleshooting
steps of checking the bridge syntax, system time, and firewall settings.
With or without obfs4 didn't make a difference. The user eventually
tried downgrading the bridge from to that fixed
it. Their client version was

They also tried with two bridges from BridgeDB. The one running
didn't work, and the one running did.

A possible lead are these client log messages:
[info] handle_response_fetch_desc(): Received server info (body size 0) from server 'X.X.X.X:YYYY'
[info] handle_response_fetch_desc(): Received http status code 404 ("Servers unavailable") from server 'X.X.X.X:YYYY' while fetching "/tor/server/authority.z". I'll try again soon.

More information about the tor-dev mailing list