Re: [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            |     Resolution:
 Keywords:                    |  Actual Points:
Parent ID:                    |         Points:
 Reviewer:                    |        Sponsor:
------------------------------+---------------------

Comment (by dcf):

 Replying to [comment:4 tagener-noisu]:
 > Everything is ok, I've got this:
 > And a log file here:

 Hm, I don't know what to suggest. You can try increasing the tor log
 verbosity from "notice" to "info":
 {{{
 Log info syslog
 }}}
 That should give you some more information about it starting its
 subprocesses.

 Is it possible you have some kind of hardening like seccomp or apparmor
 that applies to tor? That might be restricting what it can do with its
 child processes. Are you able to use an obfs4 bridge with obfs4proxy?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20451#comment:5>
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