F-Droid build gave me unusable orbot about orbot HOT 11 CLOSED

Sorry that I fell with the door in the house, but I was a bit caught on the wrong foot when suddenly nothing works and even after trying around, no connection could be established
But first to the information,.rooted NE2213 Oxygen 13.1 last Version, with AF+ I direct the data streams, I did an update with f-droid over my good old version, normally I let messenger, email and other apps through Tor.
For the mail provider is a mapping of the onion address entered in torrc
Furthermore, I have about 100 exit nodes set by fingerprint and guard nodes by country code.
The first error that Orbot did not want to start with the configuration I could see in the debug log, the entries were simply entered one after the other, so that you had to start a new line after the last entry in the options, so the entries were noted correctly and Orbot starts.
Unfortunately it does not connect, I get the notification that a VPN is active, but then nothing happens. For this reason, no IP is displayed.
I also tried to delete all data and start clean Orbot, but same result.
Back on the old version everything works as usual.
If I can provide any other information, tell me which ones and where I can find them.

from orbot.

Sorry for the trouble you encountered, happy to help, as long as you leave the snark at the door.

1. We look into parsing/verification of torrc settings, but not sure we actually changed any code there.
2. Can you provide more detail on your OS version and device? This isn't the experience that most of our users are having. App routing through the VPN is working as always.
3. Again, the exit IP display in notifications has not changed.
4. The proxies are still there as always, shown under the "more" tab. You can enable "Power User Mode" in settings, and disable all VPN features.

Please make sure you are using the latest v17 RC1 release: https://github.com/guardianproject/orbot/releases/tag/17.0.0-RC-1-tor.0.4.7.11

from orbot.

P.s. - I appreciate your feedback, but assuming our code is 100% failure and your device and network are 100% perfect is not helpful. More information about your network, device, OS, custom ROMs, custom torrc settings, is helpful.

Clearly you are an advanced user with advanced expectations, and we will do our best to help figure this out, but if you are changing things in torrc, it might be good to tell us what you are doing, for instance.

from orbot.

Is AF+ acting as a firewall through the VPN, or just through iptables/root?

from orbot.

acting as root/iptables

I open ways for LAN/WLAN/Mobile/VPN

the Apps for Orbot get only VPN and Orbot itself gets all four ways

from orbot.

I started a new attempt, this time not with the F-Droid version, but with the download here at github... this time it connects directly with the old settings.
The only thing that doesn't work is the IP display in the notification. It is only shown when I enable the debug log.

from orbot.

-Second afters starting Tor with VPN, no choosen App can go through tor, all are without of internet connection, so orbot has no function anymore.

I can confirm this, Orbot 17.0.0-RC-1-tor.0.4.7.11 upgraded via F-Droid says it's connected but no apps set to use it have network access. This was my first time trying the new remake of Orbot. This is on Graphene OS.

I downgraded and things work again.

from orbot.

@scallyob Try the version here from github, it worked for me.

from orbot.

At the moment no connection but VPN icon is on.

I get this error :

Snowflake proxy mode enabled
updating settings in Tor service
Updating torrc custom configuration…
Orbot is starting…
Connected to tor control port
Added control port event handler
NOTICE: Bootstrapped 100% (done): Done
Message (ADDRMAP): 10.243.33.202 imap.mailbox.org.85D4088148B1A6954C9BFFFCA010E85E0AA88FF0.exit NEVER CACHED="YES"
WARN: Stale automapped address for '[scrubbed].exit'. Refusing.
WARN: tor_bug_occurred_: Bug: src/core/or/connection_edge.c:2171: connection_ap_handshake_rewrite_and_attach: This line should not have been reached. (on Tor 0.4.7.11 f8c4772b01f22858)
WARN: Bug: Tor 0.4.7.11 (git-f8c4772b01f22858): Line unexpectedly reached at connection_ap_handshake_rewrite_and_attach at src/core/or/connection_edge.c:2171. (Stack trace not available) (on Tor 0.4.7.11 f8c4772b01f22858)
WARN: Stale automapped address for '[scrubbed].exit'. Refusing.
WARN: tor_bug_occurred_: Bug: src/core/or/connection_edge.c:2171: connection_ap_handshake_rewrite_and_attach: This line should not have been reached. (on Tor 0.4.7.11 f8c4772b01f22858)
WARN: Bug: Tor 0.4.7.11 (git-f8c4772b01f22858): Line unexpectedly reached at connection_ap_handshake_rewrite_and_attach at src/core/or/connection_edge.c:2171. (Stack trace not available) (on Tor 0.4.7.11 f8c4772b01f22858)
WARN: Stale automapped address for '[scrubbed].exit'. Refusing.
WARN: tor_bug_occurred_: Bug: src/core/or/connection_edge.c:2171: connection_ap_handshake_rewrite_and_attach: This line should not have been reached. (on Tor 0.4.7.11 f8c4772b01f22858)
WARN: Bug: Tor 0.4.7.11 (git-f8c4772b01f22858): Line unexpectedly reached at connection_ap_handshake_rewrite_and_attach at src/core/or/connection_edge.c:2171. (Stack trace not available) (on Tor 0.4.7.11 f8c4772b01f22858)
WARN: Stale automapped address for '[scrubbed].exit'. Refusing.
WARN: tor_bug_occurred_: Bug: src/core/or/connection_edge.c:2171: connection_ap_handshake_rewrite_and_attach: This line should not have been reached. (on Tor 0.4.7.11 f8c4772b01f22858)
WARN: Bug: Tor 0.4.7.11 (git-f8c4772b01f22858): Line unexpectedly reached at connection_ap_handshake_rewrite_and_attach at src/core/or/connection_edge.c:2171. (Stack trace not available) (on Tor 0.4.7.11 f8c4772b01f22858)
WARN: Stale automapped address for '[scrubbed].exit'. Refusing.
WARN: tor_bug_occurred_: Bug: src/core/or/connection_edge.c:2171: connection_ap_handshake_rewrite_and_attach: This line should not have been reached. (on Tor 0.4.7.11 f8c4772b01f22858)
WARN: Bug: Tor 0.4.7.11 (git-f8c4772b01f22858): Line unexpectedly reached at connection_ap_handshake_rewrite_and_attach at src/core/or/connection_edge.c:2171. (Stack trace not available) (on Tor 0.4.7.11 f8c4772b01f22858)

Could someone explain these warnings?

from orbot.

I also have the described problems. I'm by no means a technical user, feel free to correct me or ask for more information.
Any app that should get its traffic routed through the Tor network just tells me it has no internet connection. I'll try rolling back to a previous version.

from orbot.

So nobody is willing to help with this issue and problems can be solved with complete reinstall of the orbot app I will close it for now!

from orbot.