0

Here's the log descriptions:

checking binary version: 0.3.4.9-openssl1.0.2p
Set background service to FOREGROUND
updating settings in Tor service
updating torrc custom configuration...
success.
Waiting for control port...
checking binary version: 0.3.4.9-openssl1.0.2p
Orbot is starting…
Orbot is starting…
updating settings in Tor service
updating torrc custom configuration...
success.
Orbot is starting…
Waiting for control port...
Connecting to control port: 59689
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
Tor started; process id=12309
NOTICE: Bootstrapped 5%: Connecting to directory server 
NOTICE: Bootstrapped 10%: Finishing handshake with directory server 
WARN: Proxy Client: unable to connect to 107.160.7.24:443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 107.160.7.24:443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 107.160.7.24:443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 107.160.7.24:443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 107.160.7.24:443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 107.160.7.24:443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 107.160.7.24:443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 107.160.7.24:443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 107.160.7.24:443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 107.160.7.24:443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 188.166.252.228:9443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 35.203.134.33:2224 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 107.160.7.24:443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 107.160.7.24:443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 107.160.7.24:443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 107.160.7.24:443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 107.160.7.24:443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 188.166.252.228:9443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 35.203.134.33:2224 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 107.160.7.24:443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 107.160.7.24:443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 107.160.7.24:443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 188.166.252.228:9443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 35.203.134.33:2224 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 107.160.7.24:443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 35.203.134.33:2224 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 188.166.252.228:9443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 107.160.7.24:443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 188.166.252.228:9443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 35.203.134.33:2224 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 188.166.252.228:9443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 35.203.134.33:2224 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 188.166.252.228:9443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 107.160.7.24:443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 188.166.252.228:9443 ("general SOCKS server failure") 
WARN: Proxy Client: unable to connect to 35.203.134.33:2224 ("general SOCKS server failure") 
TorService is shutting down
Using control port to shutdown Tor
sending HALT signal to Tor process
Orbot is deactivated
checking binary version: 0.3.4.9-openssl1.0.2p
Set background service to FOREGROUND
updating settings in Tor service
updating torrc custom configuration...
success.
Waiting for control port...

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.