On Thu, Dec 06, 2018 at 10:19:09PM -0700, David Fifield wrote:

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 0.3.4.9 to 0.2.9.17--and that fixed it. Their client version was 0.3.4.9. https://bugs.torproject.org/28717#comment:18

They also tried with two bridges from BridgeDB. The one running 0.3.4.9 didn't work, and the one running 0.2.9.17 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.

The problem started in 0.3.4.1-alpha, according to the user's tests of multiple versions on the bridge. https://bugs.torproject.org/28717#comment:20 working 0.2.9.17 working 0.3.2.10 (git-31cc63deb69db819) working 0.3.3.10 (git-2e94df92caee0fca) working 0.3.3.6 (git-7dd0813e783ae16e) working 0.3.3.7 (git-035a35178c92da94) working 0.3.3.9 (git-45028085ea188baf) not working 0.3.4.1-alpha (git-deb8970a29ef7427) not working 0.3.4.2-alpha (git-bc951e83aac770d1) not working 0.3.4.6-rc (git-6045c26d8442913e) not working 0.3.4.7-rc (git-8465a8d84647c349) not working 0.3.4.8 (git-da95b91355248ad8) not working 0.3.4.9 (git-4ac3ccf2863b86e7)