Tor starts PTs before creating the extended_orport_auth_cookie file they need
I'm using 0.2.5.10-1~d70.wheezy+1 from Debian and obfs4proxy 0.0.4-1 to set up a some bridges. My torrc looks like:
Address 192.0.2.23
OutboundBindAddress 192.0.2.23
OutboundBindAddress 2001:db8::94de
ORPort 56527
ExtORPort 55009
ORListenAddress 192.0.2.23:56527
ORListenAddress [2001:db8::94de]:56527
DataDirectory /var/lib/tor
PidFile /var/run/tor/tor.pid
Log notice file /var/log/tor/notices.log
ServerTransportPlugin scramblesuit exec /usr/bin/obfsproxy managed
ServerTransportPlugin obfs3,obfs4 exec /usr/bin/obfs4proxy -enableLogging -logLevel=INFO
ServerTransportListenAddr obfs3 192.0.2.23:33027
ServerTransportListenAddr obfs3 [2001:db8::94de]:33027
ServerTransportListenAddr obfs4 192.0.2.23:47131
ServerTransportListenAddr obfs4 [2001:db8::94de]:47131
ServerTransportListenAddr scramblesuit 192.0.2.23:16428
ServerTransportListenAddr scramblesuit [2001:db8::94de]:16428
ContactInfo me@example.org
User debian-tor
RunAsDaemon 1
NumCPUs 1
PublishServerDescriptor 1
SocksPort 0
BridgeRelay 1
Exitpolicy reject *:*
Exitpolicy reject6 *:*
BridgeRecordUsageByCountry 1
ConnDirectionStatistics 1
EntryStatistics 1
ExtraInfoStatistics 1
DynamicDHGroups 1
HardwareAccel 1
When I enter the bridge line in TBB 4.5a4, I can't get a connection. Looking at the obfs4proxy.log, I see the message:
2015/03/11 22:19:25 [ERROR]: obfs4([scrubbed]:58915) - failed to connect to ORPort: mismatch in server hash
When I comment out the ExtORPort
line and restart Tor, I can connect to the bridge. If I set ExtORPort auto
I can't get a connection. Later I'll provide a more detailed log.