Opened 3 years ago

Closed 2 years ago

#21025 closed defect (fixed)

Orbot Problem on Nexus 6P

Reported by: Orbot Problems Owned by: n8fr8
Priority: Medium Milestone:
Component: Applications/Orbot Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

So when I try to connect to any of the prebuilt bridges in Orbot, for example meek amazon, I get this error:

Set background service to FOREGROUND
Orbot is starting…
Orbot is starting…
updating settings in Tor service
Using meek bridges updating torrc custom configuration...
torrc.custom=ControlPortWriteToFile /data/data/org.torproject.android/app_bin/control.txt SOCKSPort 9050
SafeSocks 0
TestSocks 0
WarnUnsafeSocks 1
TransPort 9040
DNSPort 5400
VirtualAddrNetwork 10.192.0.0/10
AutomapHostsOnResolve 1
DisableNetwork 0
Log debug syslog
Log info syslog
SafeLogging 0
UseBridges 1
ClientTransportPlugin meek_lite exec /data/data/org.torproject.android/app_bin/obfs4proxy
Bridge meek_lite 0.0.2.0:2 url=https://d2zfqthxsdq309.cloudfront.net/ front=a0.awsstatic.com
GeoIPFile /data/data/org.torproject.android/app_bin/geoip
GeoIPv6File /data/data/org.torproject.android/app_bin/geoip6
StrictNodes 0

success.
Orbot is starting…
/data/data/org.torproject.android/app_bin/tor DataDirectory
/data/data/org.torproject.android/app_data --defaults-torrc
/data/data/org.torproject.android/app_bin/torrc -f /data/data/org.torproject.android/app_bin/torrc.custom
Waiting for control port...
Reading control port config file: /data/data/org.torproject.android/app_bin/control.txt
Connecting to control port: 47318
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=14203
Starting polipo process
Polipo is running on port:8118
Polipo is running
WARN: The communication stream of managed proxy '/data/data/org.torproject.android/app_bin/obfs4proxy' is 'closed'. Most probably the managed proxy stopped running. This might be a bug of the managed proxy, a bug of Tor, or a misconfiguration. Please enable logging on your managed proxy and check the logs for errors.
Circuit (1) LAUNCHED: NOTICE:
Bootstrapped 5%: Connecting to directory server orConnStatus (0.0.2.0:2): LAUNCHED
WARN: We were supposed to connect to bridge '0.0.2.0:2' using pluggable transport 'meek_lite', but we can't find a pluggable transport proxy supporting 'meek_lite'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
WARN: Problem bootstrapping.
Stuck at 5%: Connecting to directory server. (Can't connect to bridge; PT_MISSING; count 1; recommendation warn; host 0000000000000000000000000000000000000000 at 0.0.2.0:2)
Circuit (1) FAILED: ONEHOP_TUNNEL > S_INTERNAL > EED_CAPACITY

I am currently using a Nexus 6p on android 7.1 and I can use the bridges given by bridges.torproject.org but still can't use the prebuilt meek, obfs4, or scramblesuit ones..

Child Tickets

Change History (2)

comment:1 Changed 3 years ago by cypherpunks

Component: - Select a componentApplications/Orbot
Owner: set to n8fr8

comment:2 Changed 2 years ago by cypherpunks

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.