Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

orbot stops whenever I try to enable remote access #175

Closed
twoprops opened this issue Jan 1, 2018 · 9 comments
Closed

orbot stops whenever I try to enable remote access #175

twoprops opened this issue Jan 1, 2018 · 9 comments

Comments

@twoprops
Copy link

twoprops commented Jan 1, 2018

Whenever I try to check the "Enable remote access via Tor Onion Service" box, Orbot opens, I get the "An app wants to open hidden server port 8888 to the Tor network. This is safe if you trust the app." message. When I click allow, I get the "Orbot has stopped" system message. Every. Time.

It doesn't matter if Orbot was running or not before attempting to open the hidden service.

This is on a Nexus 6 that I got directly from Google, running dead-stock Android 7.1.1. Orbot is up-to-date (15.5.0-RC-1-multi-SDK23) and Haven is the latest (29December2017) beta in the Google store. I've tried uninstalling and re-installing Haven and, of course, turnin'-it-off-and-back-on-again. Repeated tries just repeatedly crash Orbot.

Oddly, nobody else seems to have reported even a vaguely similar problem, yet it renders Haven useless and it's hard to conceive of a more standard Android environment.

Any ideas?

@christopher-owen
Copy link

Exact same issue here running on a Samsung Note GT-N7000 with Android 4.1.2.
Haven 0.1.0-beta-3
Orbot 15.5.0-RC-1-multi-SDK16

@MTRNord
Copy link

MTRNord commented Jan 1, 2018

Happens with one plus one too. Orbot is installed from The play store

@kushaldas
Copy link
Contributor

Same problem if I install Orbot form the play store. I had to install Orbot 15.5.1-RC-2-multi-SDK23 from the F-Droid store. That worked. My Haven is also a nightly build.

@christopher-owen
Copy link

Removed the Playstore version of Orbot and installed the Fdroid version and it works fine.

@n8fr8
Copy link
Member

n8fr8 commented Jan 2, 2018

Hmmm.... thanks for the reports. I thought the F-Droid and Play Store versions where the same, but maybe we forgot to push RC2 to Google Play? Or maybe not everyone is receiving it. Will double check today.

@twoprops
Copy link
Author

twoprops commented Jan 2, 2018

I don't know much about the internal workings of the Play Store. It wasn't telling me that there was an update to Orfox, but I tried uninstalling it a re-downloading it just because. It's still reporting that it's at RC-1.

@lukeswitz
Copy link
Collaborator

lukeswitz commented Jan 2, 2018

RESOLVED

  • Fixed by a later commit
  • Resolved Issue:
  • Confirmed same bug on Nexus 4. Play Store Orbot version remains at RC1. F-Droid serves up RC2 properly and fixes this onboarding issue.

@n8fr8 n8fr8 added this to the 0.1.0 beta 9 milestone Jan 12, 2018
@n8fr8
Copy link
Member

n8fr8 commented Jan 19, 2018

Orbot v16 should address this, and is out/available everywhere

@twoprops
Copy link
Author

Working great! Thanks for what you've done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants