orbot can't connect to a socket


2 years ago
Hi,
I'm using Orbot v Apr 18 on Android 4.4.2 running on a Samsung Note 3. The previous version used to run OK but this version now gives an error that it can't connect to a socket.

Here is a log:

Orbot is starting…
checking local port is available: 9050
Tor socket 9050 is not available
checking binary version: 0.2.4.21-openssl1.0.1g-if8
tor: PRE: Is binary exec? false
(re)Setting permission on binary: /data/data/org.torproject.android/app_bin/tor
tor: POST: Is binary exec? true
privoxy: PRE: Is binary exec? false
(re)Setting permission on binary: /data/data/org.torproject.android/app_bin/privoxy
Orbot is starting…
privoxy: POST: Is binary exec? true
obfsproxy: PRE: Is binary exec? false
(re)Setting permission on binary: /data/data/org.torproject.android/app_bin/obfsproxy
obfsproxy: POST: Is binary exec? true
xtables: PRE: Is binary exec? false
(re)Setting permission on binary: /data/data/org.torproject.android/app_bin/xtables
xtables: POST: Is binary exec? true
Orbot is starting…
Connecting to control port: 9051
Error connecting to Tor local control port: failed to connect to /127.0.0.1 (port 9051): connect failed: ECONNREFUSED (Connection refused)
waiting.
Connecting to control port: 9051
Error connecting to Tor local control port: failed to connect to /127.0.0.1 (port 9051): connect failed: ECONNREFUSED (Connection refused)
waiting.
Connecting to control port: 9051
Error connecting to Tor local control port: failed to connect to /127.0.0.1 (port 9051): connect failed: ECONNREFUSED (Connection refused)
waiting.


Any one experiencing similar problem?
Any idea how to fix this?

Cheers,
Da Man

2 years ago
I have a Samsung S5 Model SM-G900T running Android Version 4.4.2. Baseband version G900TUVU1ANCH. Kernel Version 3.4.0-964333 Build Number KOT49H.G900TUVU1ANCH. Enforcing SEPF_SM-900T_4.4.2_0011.

I am also getting no joy. It is not able to use the local loop back port to connect as your error message indicates that is the same error that I get as well.

Would love to know when or if there will be a fix for this in the near future.

2 years ago
Hi, same problem here ! I have note 3 N9005 with kitkat 4.4.2 and root. . Orbot last version doesn't start and say connection refused . Can't connect to 127.0.01 port 9051.
The same version of orbot run like a charm in my tablet n8000 with jb 4.2.1.
How can I solve this error ?

2 years ago
Still have this issue on my Galaxy S5, verizon. Says econnrefused, couldn't connect to a socket.

Orbot is starting…
tor: PRE: Is binary exec? false
(re)Setting permission on binary: /data/data/org.torproject.android/app_bin/tor
tor: POST: Is binary exec? true
polipo: PRE: Is binary exec? false
(re)Setting permission on binary: /data/data/org.torproject.android/app_bin/polipo
polipo: POST: Is binary exec? true
obfsclient: PRE: Is binary exec? false
(re)Setting permission on binary: /data/data/org.torproject.android/app_bin/obfsclient
obfsclient: POST: Is binary exec? true
xtables: PRE: Is binary exec? false
(re)Setting permission on binary: /data/data/org.torproject.android/app_bin/xtables
xtables: POST: Is binary exec? true
updating torrc custom configuration...
success.
Orbot is starting…
Control Port config file does not yet exist (waiting for tor): /data/data/org.torproject.android/app_bin/control.txt
waiting...
Control Port config file does not yet exist (waiting for tor): /data/data/org.torproject.android/app_bin/control.txt
waiting...
Control Port config file does not yet exist (waiting for tor): /data/data/org.torproject.android/app_bin/control.txt
Connecting to control port: 9051
Error connecting to Tor local control port: failed to connect to /127.0.0.1 (port 9051): connect failed: ECONNREFUSED (Connection refused)
waiting...
Couldn't start Tor process:; exit=0:
Tor exit code: 0
Couldn't start Tor process:


SOS

J

2 years ago
4.4.2

2 years ago
After update to Orbot on my android today I now get
Orbot is starting…
Control Port config file does not yet exist (waiting for tor): /data/data/org.torproject.android/app_bin/control.txt
waiting...
tor: PRE: Is binary exec? true
polipo: PRE: Is binary exec? true
obfsclient: PRE: Is binary exec? true
xtables: PRE: Is binary exec? true
updating torrc custom configuration...
success.
Orbot is starting…
Control Port config file does not yet exist (waiting for tor): /data/data/org.torproject.android/app_bin/control.txt
waiting...
Control Port config file does not yet exist (waiting for tor): /data/data/org.torproject.android/app_bin/control.txt
waiting...
Control Port config file does not yet exist (waiting for tor): /data/data/org.torproject.android/app_bin/control.txt
waiting...
Control Port config file does not yet exist (waiting for tor): /data/data/org.torproject.android/app_bin/control.txt
waiting...
Control Port config file does not yet exist (waiting for tor): /data/data/org.torproject.android/app_bin/control.txt
waiting...
Control Port config file does not yet exist (waiting for tor): /data/data/org.torproject.android/app_bin/control.txt
waiting...
Control Port config file does not yet exist (waiting for tor): /data/data/org.torproject.android/app_bin/control.txt
waiting...
Control Port config file does not yet exist (waiting for tor): /data/data/org.torproject.android/app_bin/control.txt
waiting...



Still failing. Phone is up to date also.

2 years ago
Same problem here. Same error and only started after a recent Verizon update. Running android 4.4.2 on an SM-G900V.

2 years ago
I just recently upgrade to KitKat and am having the same problem on my Galaxy S4. Anyone solve this?

Reply

You are not logged in. Login or register to reply on this thread.