Orbot error when using obfs4 bridges
Orbot is starting… Orbot is starting… Waiting for control port... Connecting to control port: 38088 Connecting to control port: 38088 Connecting to control port: 38088 tor: PRE: Is binary exec? true polipo: PRE: Is binary exec? true obfsclient: PRE: Is binary exec? true xtables: PRE: Is binary exec? true Orbot is starting… Orbot is starting… updating torrc custom configuration... success. Orbot is starting… Waiting for control port... Connecting to control port: 34458 SUCCESS connected to Tor control port. SUCCESS - authenticated to control port. Starting Tor client… complete. adding control port event handler SUCCESS added control port event handler NOTICE: Opening Socks listener on 127.0.0.1:9050 Local SOCKS port: 9050 NOTICE: Opening Transparent pf/netfilter listener on 127.0.0.1:9040 NOTICE: Closing no-longer-configured Transparent pf/netfilter listener on 127.0.0.1:59904 NOTICE: Closing old Transparent pf/netfilter listener on 127.0.0.1:59904 Local TransProxy port: 9040 NOTICE: Opening DNS listener on 127.0.0.1:5400 NOTICE: Closing no-longer-configured DNS listener on 127.0.0.1:55750 NOTICE: Closing old DNS listener on 127.0.0.1:55750 Local DNSPort port: 9040 Tor started; process id=7660 updating settings in Tor service Set background service to FOREGROUND Starting polipo process WARN: We were supposed to connect to bridge 'Address' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. NOTICE: Delaying directory fetches: No running bridges Polipo is running on port:8118 Polipo process id=7680
Trac:
Username: ProGamerGuy