Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2013-12-09T22:17:11Zhttps://gitlab.torproject.org/legacy/trac/-/issues/8600Orbot crashes when the app is reopened2013-12-09T22:17:11ZTracOrbot crashes when the app is reopenedI cannot test this myself because I do not have Android, but here is a quote from the help desk, ticket #8615:
> I installed Orbot in my Nexus 7, and while it works, whenever I go back to
> it (that is, I use another application, and th...I cannot test this myself because I do not have Android, but here is a quote from the help desk, ticket #8615:
> I installed Orbot in my Nexus 7, and while it works, whenever I go back to
> it (that is, I use another application, and then return to Orbot) the
> application starts flickering, and I cannot stop or reconfigure it. It
> won't answer to any clicks (touchs?) and the only way out is killing it
> through another app. What's the problem?
Help desk ticket #8617 describes comments on Google Market from users experiencing similar issues.
> > *Ivan Thomson* <!https://plus.google.com/103553384422095535404> - February
> > 3, 2013 - Samsung Galaxy Nexus with version 0.2.3.23-rc-1.0.11-RC6
> > Kind of works, but crashes.
> > Works, but freaks out if I reopen the app. At that point it crashes and Jay
> > flashes between the main screen and a black/blank screen non stop. I'm
> > forced to open apps from settings and force quit the app once it goes
> > spastic. Running 4.2.1 Jb on galaxy nexus.
> and also
> > *anthony carb* <!https://plus.google.com/115129417378559346384> - December
> > 9, 2012 - Version 0.2.3.23-rc-1.0.11-RC6
> > Poor for the HTC droid DNA
> > Looks to be a display problem screen flickers from start of setup so can't
> > configure
> and
> > *A Google User* - October 24, 2012 - Version 0.2.4.4-alpha-1.0.11-RC4
> > Broken since last update
> > UI flashing and flickering all over the place. No longer connecting. Gone
> > from perfectly fine to unusable
**Trac**:
**Username**: mattNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/8796500 Internal Privoxity error2014-09-01T20:07:06ZTrac500 Internal Privoxity errori've recently installed Orbot on my android galaxy S4, and it works on some websites but randomly when i try to access another page or website it comes up with
500 Internal Privoxy Error
privoxy encountered an error while processing you...i've recently installed Orbot on my android galaxy S4, and it works on some websites but randomly when i try to access another page or website it comes up with
500 Internal Privoxy Error
privoxy encountered an error while processing your request:
could not load template file forwarding - failed or one of its included components
**Trac**:
**Username**: ae86Tor: unspecifiedNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/8852Orbot + Firefox 10.0.4 + Proxymob 0.0.82016-07-08T12:52:14ZTracOrbot + Firefox 10.0.4 + Proxymob 0.0.8I installed Orbot and firefox 10.0.4 + proxymob 0.0.8 and I’ve been able to browse the deepweb for a few hours without any pb.
But maybe 2 days ago I suddenly couldn’t access tor anymore. I didn’t make any changes in between.
Orbot start...I installed Orbot and firefox 10.0.4 + proxymob 0.0.8 and I’ve been able to browse the deepweb for a few hours without any pb.
But maybe 2 days ago I suddenly couldn’t access tor anymore. I didn’t make any changes in between.
Orbot starts normally and is connected. If I go to
https://check.torproject.org
with firefox+proxymob I’ve got a nice
“Congratulations. Your browser is configured to use tor”.
But I can’t load any .onion page anymore.
I tried to reinstall everything, I restored the factory settings of my phone, I tried to define proxies manually, I tried under Wifi and 3G, I tried older versions of firefox and even proxymob, etc, etc. But it just don’t work anymore even if I see “congratulations, your Browser is configured to use Tor”
Any idea would be welcome !!
Samsung S GT-i9000
(I don’t want to root my device as I saw firefox running deepweb perfectly)
Android GingerBread 2.3.6 unrooted
firefox 10.0.4
proxymob 0.0.8
SOCKS Proxy Host 127.0.0.1
SOCKS Proxy Port 9050
SOCKS Remote DNS True
**Trac**:
**Username**: hokanekoNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/8882Include Arabic translation for Orbot strings.xml2014-04-16T06:06:25ZSheriefInclude Arabic translation for Orbot strings.xmlArabic Translation for Orbot strings.xml was revised (twice) and completed, Please include it.Arabic Translation for Orbot strings.xml was revised (twice) and completed, Please include it.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/9720Orbot Android Force Close loop on weird bridge lines2016-04-07T11:38:41ZTracOrbot Android Force Close loop on weird bridge linesBasically it seems that one or both of the following are true:
Orbot Force Closes every time you try to interact with the Orbot app if:
1. You have something weird in your bridge line like a missing comma, or commas, or a FQDN instead...Basically it seems that one or both of the following are true:
Orbot Force Closes every time you try to interact with the Orbot app if:
1. You have something weird in your bridge line like a missing comma, or commas, or a FQDN instead of an IP, or or or or or or or. Please robustify.
2. You have a bridge string that is too long for Orbot's tastes, I think it may also set off a similar Force Close loop, but I haven't rigorously tested this.
**Trac**:
**Username**: gmorehouseNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/9725'About' section has outdated information2020-06-13T02:30:59ZMatt Pagan'About' section has outdated informationAccording to a user, the 'About' section in Orbot still says it uses Tor 0.2.3.According to a user, the 'About' section in Orbot still says it uses Tor 0.2.3.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/9805Orbot needs updating on F-Droid/Guardian Project Repo2016-04-07T11:33:47ZcypherpunksOrbot needs updating on F-Droid/Guardian Project RepoThe lastest version shown at https://guardianproject.info/repo/ is 12.0.3, while the Play Store and https://guardianproject.info/releases/ have 12.0.5.
The default FDroid repo lists an even older version.
Please update... Thanks.The lastest version shown at https://guardianproject.info/repo/ is 12.0.3, while the Play Store and https://guardianproject.info/releases/ have 12.0.5.
The default FDroid repo lists an even older version.
Please update... Thanks.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/9861Orbot: enter multiple bridges, but it only uses one2020-06-13T02:34:00ZTracOrbot: enter multiple bridges, but it only uses oneThis is Orbot 12.0.5 on Android 2.3.x.
* use bridges is checked
* obfuscated bridges is checked
* bridge addresses are 1 per line, IP:port
* I know >1 of these work as I operate some of them for testing
I see a LAUNCHED for every bridg...This is Orbot 12.0.5 on Android 2.3.x.
* use bridges is checked
* obfuscated bridges is checked
* bridge addresses are 1 per line, IP:port
* I know >1 of these work as I operate some of them for testing
I see a LAUNCHED for every bridge when I start up Orbot connecting, but, circuits are only ever built through the second bridge on the list, for whatever reason. I never see log messages about the others other than LAUNCHED at startup.
Please let me know if there is a better place to submit this bug - I can't find it with The Guardian Project.
**Trac**:
**Username**: gmorehouseNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/9961Orbot contact information cannot be configured2020-06-13T02:36:07ZTracOrbot contact information cannot be configuredOrbot contact information cannot be configured in the settings menu and that leads to an INFO complaint about not set contact information in the log if Orbot is set up as a relay.
**Trac**:
**Username**: mattiOrbot contact information cannot be configured in the settings menu and that leads to an INFO complaint about not set contact information in the log if Orbot is set up as a relay.
**Trac**:
**Username**: mattiNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/9989Orbot stucks on 25%2016-04-07T10:57:53ZTracOrbot stucks on 25%Im trying to start orbot on my samsung galaxy note 2 but it stucks on 25%
im using android 4.1.1, here are logs
Orbot is starting…
Orbot is starting…
(re)Setting permission on Tor binary
(re)Setting permission on Privoxy binary
(re)Set...Im trying to start orbot on my samsung galaxy note 2 but it stucks on 25%
im using android 4.1.1, here are logs
Orbot is starting…
Orbot is starting…
(re)Setting permission on Tor binary
(re)Setting permission on Privoxy binary
(re)Setting permission on Obfsproxy binary
Orbot is starting…
got tor proc id: 3317
Tor process id=3317
Connecting to control port: 9051
SUCCESS connected to control port
SUCCESS authenticated to control port
Starting Tor client… complete.
adding control port event handler
SUCCESS added control port event handler
NOTICE: Bootstrapped 10%: Finishing handshake with directory server.
NOTICE: We weren't able to find support for all of the TLS ciphersuites that we wanted to advertise. This won't hurt security, but it might make your Tor (if run as a client) more easy for censors to block.
NOTICE: To correct this, use a more recent OpenSSL, built without disabling any secure ciphers or features.
Starting privoxy process
/data/data/org.torproject.android/app_bin/privoxy /data/data/org.torproject.android/app_bin/privoxy.config &
Privoxy is running on port:8118
Privoxy process id=3370
NOTICE: Bootstrapped 15%: Establishing an encrypted directory connection.
orConnStatus (wau): CONNECTED
NOTICE: Bootstrapped 20%: Asking for networkstatus consensus.
Circuit (1) BUILT: wau
NOTICE: Bootstrapped 25%: Loading networkstatus consensus.
**Trac**:
**Username**: BennyNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/10337I'm not sure what the error is here2020-06-13T02:43:32ZTracI'm not sure what the error is here```
Orbot is starting?
Orbot is starting?
(re)Setting permission on Tor binary
(re)Setting permission on Privoxy binary
(re)Setting permission on Obfsproxy binary
Orbot is starting?
got tor proc id: 18511
Tor process id=18511
Con...```
Orbot is starting?
Orbot is starting?
(re)Setting permission on Tor binary
(re)Setting permission on Privoxy binary
(re)Setting permission on Obfsproxy binary
Orbot is starting?
got tor proc id: 18511
Tor process id=18511
Connecting to control port: 9051
SUCCESS connected to control port
SUCCESS authenticated to control port
Starting Tor client? complete.
adding control port event handler
SUCCESS added control port event handler
Starting privoxy process
/data/data/org.torproject.android/app_bin/privoxy /data/data/org.torproject.android/app_bin/privoxy.config &
orConnStatus (CaptainPicard2): LAUNCHED
NOTICE: Bootstrapped 85%: Finishing handshake with first hop.
NOTICE: We weren't able to find support for all of the TLS ciphersuites that we wanted to advertise. This won't hurt security, but it might make your Tor (if run as a client) more easy for censors to block.
NOTICE: To correct this, use a more recent OpenSSL, built without disabling any secure ciphers or features.
Privoxy is running on port:8118
Privoxy process id=18521
Transparent Proxying: enabling...
enabling transproxy for app: com.forshared(10142)
enabling transproxy for app: mgeek.dolphin.[10114(10114)](10114(10114))
enabling transproxy for app: com.humblebundle.library(10107)
enabling transproxy for app: com.opera.browser(10138)
enabling transproxy for app: com.silvermoon.client(10099)
enabling transproxy for app: com.cloudmosa.puffin(10116)
enabling transproxy for app: com.valvesoftware.android.steam.community(10102)
enabling transproxy for app: com.google.android.youtube(10091)
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p tcp ! -d 127.0.0.1 -m owner --uid-owner 10142 -m tcp --syn -j REDIRECT --to-ports 9040 || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p udp -m owner --uid-owner 10142 -m udp --dport 53 -j REDIRECT --to-ports 5400 || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10142 -p tcp -d 127.0.0.1 --dport 5400 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10142 -p tcp -d 127.0.0.1 --dport 9040 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10142 -p tcp -d 127.0.0.1 --dport 9050 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10142 -p tcp -d 127.0.0.1 --dport 8118 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10142 -p tcp -o lo -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10142 -p tcp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10142 -p udp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p tcp ! -d 127.0.0.1 -m owner --uid-owner 10067 -m tcp --syn -j REDIRECT --to-ports 9040 || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p udp -m owner --uid-owner 10067 -m udp --dport 53 -j REDIRECT --to-ports 5400 || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10067 -p tcp -d 127.0.0.1 --dport 5400 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10067 -p tcp -d 127.0.0.1 --dport 9040 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10067 -p tcp -d 127.0.0.1 --dport 9050 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10067 -p tcp -d 127.0.0.1 --dport 8118 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10067 -p tcp -o lo -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10067 -p tcp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10067 -p udp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p tcp ! -d 127.0.0.1 -m owner --uid-owner 10114 -m tcp --syn -j REDIRECT --to-ports 9040 || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p udp -m owner --uid-owner 10114 -m udp --dport 53 -j REDIRECT --to-ports 5400 || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10114 -p tcp -d 127.0.0.1 --dport 5400 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10114 -p tcp -d 127.0.0.1 --dport 9040 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10114 -p tcp -d 127.0.0.1 --dport 9050 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10114 -p tcp -d 127.0.0.1 --dport 8118 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10114 -p tcp -o lo -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10114 -p tcp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10114 -p udp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p tcp ! -d 127.0.0.1 -m owner --uid-owner 10107 -m tcp --syn -j REDIRECT --to-ports 9040 || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p udp -m owner --uid-owner 10107 -m udp --dport 53 -j REDIRECT --to-ports 5400 || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10107 -p tcp -d 127.0.0.1 --dport 5400 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10107 -p tcp -d 127.0.0.1 --dport 9040 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10107 -p tcp -d 127.0.0.1 --dport 9050 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10107 -p tcp -d 127.0.0.1 --dport 8118 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10107 -p tcp -o lo -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10107 -p tcp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10107 -p udp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p tcp ! -d 127.0.0.1 -m owner --uid-owner 10138 -m tcp --syn -j REDIRECT --to-ports 9040 || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p udp -m owner --uid-owner 10138 -m udp --dport 53 -j REDIRECT --to-ports 5400 || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10138 -p tcp -d 127.0.0.1 --dport 5400 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10138 -p tcp -d 127.0.0.1 --dport 9040 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10138 -p tcp -d 127.0.0.1 --dport 9050 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10138 -p tcp -d 127.0.0.1 --dport 8118 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10138 -p tcp -o lo -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10138 -p tcp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10138 -p udp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p tcp ! -d 127.0.0.1 -m owner --uid-owner 10099 -m tcp --syn -j REDIRECT --to-ports 9040 || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p udp -m owner --uid-owner 10099 -m udp --dport 53 -j REDIRECT --to-ports 5400 || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10099 -p tcp -d 127.0.0.1 --dport 5400 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10099 -p tcp -d 127.0.0.1 --dport 9040 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10099 -p tcp -d 127.0.0.1 --dport 9050 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10099 -p tcp -d 127.0.0.1 --dport 8118 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10099 -p tcp -o lo -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10099 -p tcp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10099 -p udp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p tcp ! -d 127.0.0.1 -m owner --uid-owner 10116 -m tcp --syn -j REDIRECT --to-ports 9040 || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p udp -m owner --uid-owner 10116 -m udp --dport 53 -j REDIRECT --to-ports 5400 || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10116 -p tcp -d 127.0.0.1 --dport 5400 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10116 -p tcp -d 127.0.0.1 --dport 9040 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10116 -p tcp -d 127.0.0.1 --dport 9050 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10116 -p tcp -d 127.0.0.1 --dport 8118 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10116 -p tcp -o lo -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10116 -p tcp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10116 -p udp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p tcp ! -d 127.0.0.1 -m owner --uid-owner 10102 -m tcp --syn -j REDIRECT --to-ports 9040 || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p udp -m owner --uid-owner 10102 -m udp --dport 53 -j REDIRECT --to-ports 5400 || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10102 -p tcp -d 127.0.0.1 --dport 5400 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10102 -p tcp -d 127.0.0.1 --dport 9040 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10102 -p tcp -d 127.0.0.1 --dport 9050 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10102 -p tcp -d 127.0.0.1 --dport 8118 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10102 -p tcp -o lo -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10102 -p tcp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10102 -p udp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p tcp ! -d 127.0.0.1 -m owner --uid-owner 10091 -m tcp --syn -j REDIRECT --to-ports 9040 || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p udp -m owner --uid-owner 10091 -m udp --dport 53 -j REDIRECT --to-ports 5400 || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10091 -p tcp -d 127.0.0.1 --dport 5400 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10091 -p tcp -d 127.0.0.1 --dport 9040 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10091 -p tcp -d 127.0.0.1 --dport 9050 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10091 -p tcp -d 127.0.0.1 --dport 8118 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10091 -p tcp -o lo -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10091 -p tcp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10091 -p udp ! -d 127.0.0.1 -j REJECT || exit
;errCode=0;resp=FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
TorTransProxy resp code: 0
```
It stops at 85% and it doesnt go on to a green onion.
**Trac**:
**Username**: BubblesNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/10506Unable to start Tor: Unable to start Tor2018-08-16T00:28:59ZTracUnable to start Tor: Unable to start TorI used Orbot for a couple of weeks without any problems, now it has suddenly stopped to start without any apparent reason.
My phone is a Galaxy S4 i9505 with Android 4.3 with root rights.
Thank you for your help.
```
[ 12-28 16:10:34....I used Orbot for a couple of weeks without any problems, now it has suddenly stopped to start without any apparent reason.
My phone is a Galaxy S4 i9505 with Android 4.3 with root rights.
Thank you for your help.
```
[ 12-28 16:10:34.812 18135:20310 D/Orbot ]
Orbot è in esecuzione...
[ 12-28 16:10:35.052 18135:20310 D/Orbot ]
(re)Setting permission on Tor binary
[ 12-28 16:10:35.072 18135:20310 D/Orbot ]
executing shell cmd: chmod 700 /data/data/org.torproject.android/app_bin/tor; runAsRoot=false;waitFor=true
[ 12-28 16:10:35.082 18135:20310 D/Orbot ]
(re)Setting permission on Privoxy binary
[ 12-28 16:10:35.102 18135:20310 D/Orbot ]
executing shell cmd: chmod 700 /data/data/org.torproject.android/app_bin/privoxy; runAsRoot=false;waitFor=true
[ 12-28 16:10:35.122 18135:20310 D/Orbot ]
(re)Setting permission on Obfsproxy binary
[ 12-28 16:10:35.142 18135:20310 D/Orbot ]
executing shell cmd: chmod 700 /data/data/org.torproject.android/app_bin/obfsproxy; runAsRoot=false;waitFor=true
[ 12-28 16:10:35.192 18135:20310 D/Orbot ]
executing shell cmd: export HOME=/data/data/org.torproject.android/app_bin; runAsRoot=false;waitFor=false
[ 12-28 16:10:35.192 18135:20310 D/Orbot ]
executing shell cmd: /data/data/org.torproject.android/app_bin/tor DataDirectory /data/data/org.torproject.android/app_data -f /data/data/org.torproject.android/app_bin/torrc || exit
; runAsRoot=false;waitFor=false
[ 12-28 16:10:39.497 18135:20310 D/Orbot ]
executing shell cmd: export HOME=/data/data/org.torproject.android/app_bin; runAsRoot=false;waitFor=false
[ 12-28 16:10:39.497 18135:20310 D/Orbot ]
executing shell cmd: /data/data/org.torproject.android/app_bin/tor DataDirectory /data/data/org.torproject.android/app_data -f /data/data/org.torproject.android/app_bin/torrc || exit
; runAsRoot=false;waitFor=false
[ 12-28 16:10:44.051 18135:20310 D/Orbot ]
executing shell cmd: export HOME=/data/data/org.torproject.android/app_bin; runAsRoot=false;waitFor=false
[ 12-28 16:10:44.051 18135:20310 D/Orbot ]
executing shell cmd: /data/data/org.torproject.android/app_bin/tor DataDirectory /data/data/org.torproject.android/app_data -f /data/data/org.torproject.android/app_bin/torrc || exit
; runAsRoot=false;waitFor=false
[ 12-28 16:10:48.545 18135:20310 E/Orbot ]
Unable to start Tor: Unable to start Tor
java.lang.Exception: Unable to start Tor
at org.torproject.android.service.TorService.runTorShellCmd(TorService.java:828)
at org.torproject.android.service.TorService.initTor(TorService.java:676)
at org.torproject.android.service.TorService.run(TorService.java:312)
at java.lang.Thread.run(Thread.java:841)
```
**Trac**:
**Username**: jack80Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/10584Let advance user to edit Orbot's torrc file2016-04-07T11:48:03ZTracLet advance user to edit Orbot's torrc fileI want to make my Orbot to use "HidServAuth", because some hidden website
requires to add this. So, please let advanced user to add something like
"HidServAuth" into their config file(using GUI/CLI).
**Trac**:
**Username**: ikurua22I want to make my Orbot to use "HidServAuth", because some hidden website
requires to add this. So, please let advanced user to add something like
"HidServAuth" into their config file(using GUI/CLI).
**Trac**:
**Username**: ikurua22Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/10639Orbot stops when wifi is drops and reconnects (my ip was shown)2014-08-25T12:14:19ZTracOrbot stops when wifi is drops and reconnects (my ip was shown)Orbot is tor for phones, they only made one design issue...
When orbot is active then I am safe, but when wifi drops and reconnects my normal IP is visible. The worst is that orbot still shows the green "I am connected" light.
PS: pleas...Orbot is tor for phones, they only made one design issue...
When orbot is active then I am safe, but when wifi drops and reconnects my normal IP is visible. The worst is that orbot still shows the green "I am connected" light.
PS: please forward this to orbot devs, I was unable to find their project fast enough so I put the bug here.
**Trac**:
**Username**: tijs14tijsTor: unspecifiedNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/10643orweb on android 4.2.2 build 51.2c2016-04-07T11:31:52ZTracorweb on android 4.2.2 build 51.2casus memopad 10 me302c
android 4.2.2 build 51.2c
cannot use orbot orweb or tor. orbot and orweb fail to start tor with log as below. Has been going on for months now,although it used to work fine. Not aware of any updates to android. I b...asus memopad 10 me302c
android 4.2.2 build 51.2c
cannot use orbot orweb or tor. orbot and orweb fail to start tor with log as below. Has been going on for months now,although it used to work fine. Not aware of any updates to android. I blame Google for doing some auto update to some lib which broke it.
Orbot is starting...
Orbot is starting...
checking Tor binaries
(re)Setting permission on Tor binary
(re)Setting permission on Privoxy binary
(re)Setting permission on Obfsproxy binary
checking Tor binaries
(re)Setting permission on Tor binary
(re)Setting permission on Privoxy binary
(re)Setting permission on Obfsproxy binary
Orbot is starting...
Couldn't start Tor process:
Unable to start Tor: Unable to start Tor
Network connectivity is good. Waking Tor up...
Orbot is starting...
Orbot is starting...
checking Tor binaries
(re)Setting permission on Tor binary
(re)Setting permission on Privoxy binary
(re)Setting permission on Obfsproxy binary
checking Tor binaries
(re)Setting permission on Tor binary
(re)Setting permission on Privoxy binary
(re)Setting permission on Obfsproxy binary
Orbot is starting...
Couldn't start Tor process:
Unable to start Tor: Unable to start Tor
Network connectivity is good. Waking Tor up...
**Trac**:
**Username**: javadevNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/10647Orbot completely broken Android 4.1.22020-06-13T02:50:06ZTracOrbot completely broken Android 4.1.2I’ve used Orbot in the past on Android with success with different browsers, but the latest version seems to be completely broken as far as I could tell.
1. No matter what you do no application can see Tor running, so checking the Tor s...I’ve used Orbot in the past on Android with success with different browsers, but the latest version seems to be completely broken as far as I could tell.
1. No matter what you do no application can see Tor running, so checking the Tor status page shows that Tor is inactive even when it’s running.
The phone is rooted and I set “Transparent proxying to ON”
But not “Tor everything”
I then manually added different browsers in the add app section.
I tried in several different browsers including Orweb (marked as ‘latest’).
One browser seemed to realize it was connected to something but returned the message “There is a problem with the proxy server” and could not connect to anything.
All other browsers I tried simply ignore that Tor is running and connect directly (as seen on inspection of an IP checking site (or in Orweb that Check Tor page))
Currently this implementation of Tor on Android is completely unusable, which is a shame as it used to work great.
**Trac**:
**Username**: margoliaNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/10786orbot (13.0.4a) on android 4.3 didn't start - asus me302c tablet2020-06-13T02:52:25ZTracorbot (13.0.4a) on android 4.3 didn't start - asus me302c tabletIn the orbot start window I get the following information:
Orbot is starting…
Tor binary exists: /data/app-lib/org.torproject.android-2/libtor.so
Privoxy binary exists: /data/app-lib/org.torproject.android-2/libprivoxy.so
Obfsproxy bina...In the orbot start window I get the following information:
Orbot is starting…
Tor binary exists: /data/app-lib/org.torproject.android-2/libtor.so
Privoxy binary exists: /data/app-lib/org.torproject.android-2/libprivoxy.so
Obfsproxy binary exists: /data/app-lib/org.torproject.android-2/libobfsproxy.so
Xtables binary exists: /data/app-lib/org.torproject.android-2/libxtables.so
link RM err=0 out:
link LN err=0 out:
libtor.so: PRE: Is binary exec? true
(re)Setting permission on binary: /data/app-lib/org.torproject.android-2/libtor.so
libtor.so: POST: Is binary exec? true
tor: PRE: Is binary exec? true
(re)Setting permission on binary: /data/data/org.torproject.android/app_bin/tor
tor: POST: Is binary exec? true
libprivoxy.so: PRE: Is binary exec? true
(re)Setting permission on binary: /data/app-lib/org.torproject.android-2/libprivoxy.so
Orbot is starting…
libprivoxy.so: POST: Is binary exec? true
libobfsproxy.so: PRE: Is binary exec? true
(re)Setting permission on binary: /data/app-lib/org.torproject.android-2/libobfsproxy.so
libobfsproxy.so: POST: Is binary exec? true
libxtables.so: PRE: Is binary exec? true
(re)Setting permission on binary: /data/app-lib/org.torproject.android-2/libxtables.so
libxtables.so: POST: Is binary exec? true
Orbot is starting…
Couldn't start Tor process:
The tablet is unrooted. Tor version v0.2.4.20
**Trac**:
**Username**: wuzi8642Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/10794Orbot on Fairphone2014-04-06T16:34:12ZTracOrbot on FairphoneHi,
Orbot on Fairphone behaves weird which blocks using it.
When installed (with root access) and started, the default screen just flashes all the time, not/barely interacting with user input. Anyway, one can not start the functionalit...Hi,
Orbot on Fairphone behaves weird which blocks using it.
When installed (with root access) and started, the default screen just flashes all the time, not/barely interacting with user input. Anyway, one can not start the functionality.
**Versions:**
**Orbot** ... 0.2.3.23-rc.1.0.11-RC5-test2 from F-Droid
**F-Droid** ... 0.58
**Fairphone** ... Front end 1.1 "Caju"
**Android** ... 4.2.2 based on kernel 3.4.5
**Trac**:
**Username**: ax3lNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/10798Unable to start Tor if Orbot integrated as system apps2016-04-07T11:34:30ZTracUnable to start Tor if Orbot integrated as system appsI can`t integrate the Orbot as system apps (/system/app/Orbot.apk) becouse not recognize and install the Tor binary from /sysstem/lib/libtor.so
**Trac**:
**Username**: luckasfbI can`t integrate the Orbot as system apps (/system/app/Orbot.apk) becouse not recognize and install the Tor binary from /sysstem/lib/libtor.so
**Trac**:
**Username**: luckasfbNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/11022Orbot doesn't start on GT-N7100 (4.3)2016-04-07T11:49:02ZTracOrbot doesn't start on GT-N7100 (4.3)Orbot won't start on unrooted galaxy note 2 with 4.3
Log:
Orbot is starting…
Tor binary exists: /data/app-lib/org.torproject.android-1/libtor.so
Privoxy binary exists: /data/app-lib/org.torproject.android-1/libprivoxy.so
Obfsproxy bina...Orbot won't start on unrooted galaxy note 2 with 4.3
Log:
Orbot is starting…
Tor binary exists: /data/app-lib/org.torproject.android-1/libtor.so
Privoxy binary exists: /data/app-lib/org.torproject.android-1/libprivoxy.so
Obfsproxy binary exists: /data/app-lib/org.torproject.android-1/libobfsproxy.so
Xtables binary exists: /data/app-lib/org.torproject.android-1/libxtables.so
link RM err=0 out:
link LN err=0 out:
libtor.so: PRE: Is binary exec? true
(re)Setting permission on binary: /data/app-lib/org.torproject.android-1/libtor.so
libtor.so: POST: Is binary exec? true
tor: PRE: Is binary exec? true
(re)Setting permission on binary: /data/data/org.torproject.android/app_bin/tor
tor: POST: Is binary exec? true
libprivoxy.so: PRE: Is binary exec? true
(re)Setting permission on binary: /data/app-lib/org.torproject.android-1/libprivoxy.so
Orbot is starting…
libprivoxy.so: POST: Is binary exec? true
libobfsproxy.so: PRE: Is binary exec? true
(re)Setting permission on binary: /data/app-lib/org.torproject.android-1/libobfsproxy.so
libobfsproxy.so: POST: Is binary exec? true
libxtables.so: PRE: Is binary exec? true
(re)Setting permission on binary: /data/app-lib/org.torproject.android-1/libxtables.so
libxtables.so: POST: Is binary exec? true
Orbot is starting…
Couldn't start Tor process:
**Trac**:
**Username**: graber77Nathan FreitasNathan Freitas