<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
Alright, problem solved although I don't understand why. Hope someone can educate me:<br /><br />What I did.<br />(1) Turned on Log debug stderr in torrc, and I could see obfs4 loading correctly.<br />(2) Then I realized obfs4 writes to a file to help people construct the bridgeline for tow browser in pt_state/obfs4_bridgeline.txt<br /><br />The format is like:<br />Bridge obfs4 <IP ADDRESS>:<PORT> <FINGERPRINT> cert=[scrubbed] iat-mode=[scrubbed]<br /><br />Which is different from the bridge line I used by hand, i.e. has FINGERPRINT, has cert=? and iat-mode=?. <br />These extra bits made all the difference, but why?<br /><br />Jack<br /><br />30. Mar 2018 15:02 by <a href="mailto:jackoreamnos@tutanota.com" target="_blank" rel="noopener noreferrer">jackoreamnos@tutanota.com</a>:<br /><br /><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;">Am a novice compiling Tor (0.3.2.9) and been successful using this from a Tor Browser as a private bridge by entering "a.b.c.d:9001" into Tor Browser. However, pointing my Tor Browser to the obfs4 on the same machine fails with something like General SOCKS failure in the log. Below is my torrc:<br /><br />SOCKSPort 0<br />CookieAuthentication 1<br />ControlPort 9051<br />ORPort 9001<br />ExtORPort auto<br />ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy<br /># ServerTransportListenAddr obfs4 [::]:60443<br />ServerTransportListenAddr obfs4 0.0.0.0:60443<br />ExitRelay 0<br />BridgeRelay 1<br />PublishServerDescriptor 0<br /><br />Tests I have done:<br />(1) using obfs4 compiled from git repository, as well as the OS package.<br />(2) opening port 60443, as well as dropping all firewalls - does not make a difference; meanwhile, pointing telnet at a.b.c.d 60443 connects successfully<br />(3) using Tor Browser with default supplied obfs4 bridges works well (log shows I was able to download a list of bridges and their fingerprints).<br /><br />So I think I have ruled out problems with my Tor client (Tor Browser), and I have ruled out firewall configurations on the server, and ruled out obfs4 being blocked on my ISP. Since Tor itself works, and I have tried obfs4 from source as well as from the OS package, the only thing I can think of is something wrong with the config above.<br /><br />Any hints would be appreciated, as well as any steps I can do to further diagnose would be helpful.<br /><br />Thanks,<br />Jack<br /></blockquote> </body>
</html>