[tor-bugs] #20451 [Obfuscation/meek]: The communication stream of managed proxy '/usr/bin/meek-client' is 'closed'

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#20451: The communication stream of managed proxy '/usr/bin/meek-client' is
'closed'
----------------------------------+-----------------
     Reporter:  tagener-noisu     |      Owner:  dcf
         Type:  defect            |     Status:  new
     Priority:  Medium            |  Milestone:
    Component:  Obfuscation/meek  |    Version:
     Severity:  Normal            |   Keywords:
Actual Points:                    |  Parent ID:
       Points:                    |   Reviewer:
      Sponsor:                    |
----------------------------------+-----------------
 Tested on archlinux, using this package
 https://aur.archlinux.org/packages/meek/. PKGBUILD seems ok, meek-client
 is working (tested with {{{meek-client --help}}})
 torrc file:
 {{{
 Log notice syslog
 DataDirectory /var/lib/tor
 UseBridges 1
 ClientTransportPlugin meek exec /usr/bin/meek-client --log meek-client.log
 Bridge meek 0.0.2.0:3 url=https://az668014.vo.msecnd.net/
 front=ajax.aspnetcdn.com
 Bridge meek 0.0.2.0:2 url=https://d2zfqthxsdq309.cloudfront.net/
 front=a0.awsstatic.com
 }}}
 Tor service status:
 {{{
 ● tor.service - Anonymizing Overlay Network
    Loaded: loaded (/usr/lib/systemd/system/tor.service; disabled; vendor
 preset: disabled)
    Active: inactive (dead)

 Oct 25 05:20:07 laptop Tor[26070]: Delaying directory fetches: No running
 bridges
 Oct 25 05:20:08 laptop Tor[26070]: The communication stream of managed
 proxy '/usr/bin/meek-client' is 'closed'. Most probably the managed proxy
 stopped running. This might be a bug of the managed proxy, a bug of Tor,
 or a misconfiguration. Please enable logging on your managed proxy and
 check the logs for errors.
 Oct 25 05:20:09 laptop Tor[26070]: Bootstrapped 5%: Connecting to
 directory server
 Oct 25 05:20:09 laptop Tor[26070]: We were supposed to connect to bridge
 '0.0.2.0:3' using pluggable transport 'meek', but we can't find a
 pluggable transport proxy supporting 'meek'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 Oct 25 05:20:09 laptop Tor[26070]: Problem bootstrapping. Stuck at 5%:
 Connecting to directory server. (Can't connect to bridge; PT_MISSING;
 count 1; recommendation warn; host
 0000000000000000000000000000000000000000 at 0.0.2.0:3)
 Oct 25 05:20:09 laptop Tor[26070]: We were supposed to connect to bridge
 '0.0.2.0:2' using pluggable transport 'meek', but we can't find a
 pluggable transport proxy supporting 'meek'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 Oct 25 05:20:09 laptop Tor[26070]: Problem bootstrapping. Stuck at 5%:
 Connecting to directory server. (Can't connect to bridge; PT_MISSING;
 count 2; recommendation warn; host
 0000000000000000000000000000000000000000 at 0.0.2.0:2)
 Oct 25 05:21:31 laptop systemd[1]: Stopping Anonymizing Overlay Network...
 Oct 25 05:21:31 laptop Tor[26070]: Interrupt: exiting cleanly.
 Oct 25 05:21:31 laptop systemd[1]: Stopped Anonymizing Overlay Network.
 }}}
 Meek doesn't create any log files.

--
Ticket URL: <https://troodi.torproject.org/projects/tor/ticket/20451>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs