Core Apps » Orbot

Orbot is starting…
Orbot is starting…
Waiting for control port...
Connecting to control port: 55399
Connecting to control port: 55399
Connecting to control port: 55399
tor: PRE: Is binary exec? true
polipo: PRE: Is binary exec? true
obfsclient: PRE: Is binary exec? true
meek-client: PRE: Is binary exec? false
(re)Setting permission on binary: /data/data/org.torproject.android/app_bin/meek-client
meek-client: POST: Is binary exec? false
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: 47719
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:60128
NOTICE: Closing old Transparent pf/netfilter listener on 127.0.0.1:60128
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:55775
NOTICE: Closing old DNS listener on 127.0.0.1:55775
Local DNSPort port: 9040
Tor started; process id=7575
updating settings in Tor service
WARN: Option 'StrictNodes' used more than once; all but the last value will be ignored.
WARN: Option 'UseBridges' used more than once; all but the last value will be ignored.
Starting polipo process
NOTICE: Delaying directory fetches: No running bridges
WARN: Could not launch managed proxy executable at '/data/data/org.torproject.android/app_bin/meek-client' ('No such file or directory').
Polipo is running on port:8118
Polipo process id=8041
WARN: We were supposed to connect to bridge 'Address' 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.