[tor-bugs] #25527 [Obfuscation/meek]: Tor (with bridges) keeps giving “connections have failed” in command line (while working ok through Tor Browser)?

[Tor Bug Tracker & Wiki]

#25527: Tor (with bridges) keeps giving “connections have failed” in command line
(while working ok through Tor Browser)?
-------------------------------------------------+-------------------------
 Reporter:  omareg94                             |          Owner:  dcf
     Type:  defect                               |         Status:  new
 Priority:  Medium                               |      Milestone:
Component:  Obfuscation/meek                     |        Version:  Tor:
                                                 |  0.3.2.10
 Severity:  Normal                               |     Resolution:
 Keywords:  tor-browser-bundle configuration     |  Actual Points:
  bridge pluggable-transports connection         |
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by dcf):

 There is not only torrc in Tor Browser, but also torrc-defaults. Look at
 the torrc file; it doesn't say anything about pluggable transports. That
 information is in torrc-defaults.

 Additionally, Tor Browser configures bridges through the control port, not
 by writing them to a torrc file. (I think.) So the files on disk won't
 have the bridges you need, even with torrc-defaults.

 In any case, you will have to be in the correct working directory (C:\Tor
 Browser\Browser\), because torrc-defaults uses relative paths.

 I don't think this is really a meek problem. I'm sure it will happen even
 if you configure Tor Browser to connect without a bridge. I don't know an
 easy way to accomplish what you're trying to accomplish.

 You may find it easier just to write your own minimal torrc file, like
 https://gitweb.torproject.org/pluggable-transports/meek.git/tree/meek-
 client/torrc

 It is maybe a bug in tor that it is apparently trying to connect to the
 fake IP address 0.0.2.0, even though it should only be trying to connect
 to that address through a pluggable transport bridge. I'm guessing it's
 caused by tor caching the address in its state file, then being restarted
 without a pluggable transport configuration.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25527#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online