-
-
Notifications
You must be signed in to change notification settings - Fork 347
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
[BUG]Faulty Webtunnel #1193
Comments
Note:Bridges work perfectly with the Tor browser, which is said to have used Orbot as proxy. Is the Orbot app incomplete? |
Tor Browser does not use Orbot in any way. Also, webtunnel support has not been officially added to Orbot yet. |
Working on it... the capability is there, we just need to support the bridge lines properly. |
tladesignz
added a commit
to tladesignz/orbot
that referenced
this issue
Jan 23, 2025
…h custom bridges: Meek, Obfs4 and Webtunnel can now be used all in parallel.
syphyr
pushed a commit
to syphyr/orbot
that referenced
this issue
Jan 24, 2025
…h custom bridges: Meek, Obfs4 and Webtunnel can now be used all in parallel.
syphyr
pushed a commit
to syphyr/orbot
that referenced
this issue
Jan 24, 2025
…h custom bridges Meek, Obfs4 and Webtunnel can now be used all in parallel.
This was referenced Jan 24, 2025
Closed
syphyr
pushed a commit
to syphyr/orbot
that referenced
this issue
Jan 24, 2025
…h custom bridges Meek, Obfs4 and Webtunnel can now be used all in parallel.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the Bug
Impossible to connect to WT even in latest version.
Always shows warning . Sign of non-existant, misconfigured or buggy Lyrebird.
To Reproduce
Simply enter some WT bridges and connect. Either no effect or shows the warning and fails.
Expected Behavior
Connect normally.
What Custom Configuration Do You Use?
None, just the WT bridges
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):
Crash Logs (Advanced)
If applicable, add crash logs collected using ADB Logcat.
Additional Context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: