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

Tor connection failed using meek-azure bridge #25535

Open
stephendonner opened this issue Sep 21, 2022 · 3 comments
Open

Tor connection failed using meek-azure bridge #25535

stephendonner opened this issue Sep 21, 2022 · 3 comments

Comments

@stephendonner
Copy link

stephendonner commented Sep 21, 2022

Description

Tor connection failed using meek-azure bridge

Steps to Reproduce

  1. install 1.44.95
  2. launch Brave
  3. open brave://settings/privacy
  4. toggle Use Bridges to Enabled
  5. switch Select a built-in bridge to meek-azure
  6. click Apply changes
  7. click File -> New Private Window with Tor
  8. wait

Actual result:

Tor connection failed message tor-internals tor-internals tor-internals
Screen Shot 2022-09-21 at 12 53 21 PM Screen Shot 2022-09-21 at 12 55 08 PM Screen Shot 2022-09-21 at 12 55 16 PM Screen Shot 2022-09-21 at 12 55 20 PM

Logs:

WARN: Cannot find maximum file descriptor, assuming: 256
NOTICE: Switching to guard context "bridges" (was using "default")
NOTICE: Bootstrapped 10% (conn_done): Connected to a relay
NOTICE: Delaying directory fetches: No running bridges
NOTICE: Bootstrapped 14% (handshake): Handshaking with a relay
NOTICE: Bootstrapped 15% (handshake_done): Handshake with a relay done
NOTICE: Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
NOTICE: Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
NOTICE: new bridge descriptor 'cymrubridge02' (fresh): $97700DFE9F483596DDA6264C4D7DF7641E1E39CE~cymrubridge02 [/LIpGKq6STgqkVJaKWDj92BCzGWbwqe3lBU+8hsQKP8] at 192.0.2.2
NOTICE: Bootstrapped 30% (loading_status): Loading networkstatus consensus
NOTICE: I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
NOTICE: Delaying directory fetches: No running bridges
NOTICE: Bootstrapped 40% (loading_keys): Loading authority key certs
NOTICE: I learned some more directory information, but not enough to build a circuit: No running bridges

Expected result:

Tor successfully connected

Reproduces how often:

100%

Brave version (brave://version info)

Brave 1.44.95 Chromium: 106.0.5249.40 (Official Build) (x86_64)
Revision fab1d91915d2722d6339aaa7f4e9ce44f1e9b103-refs/branch-heads/5249@{#442}
OS macOS Version 11.7 (Build 20G817)

Version/Channel Information:

  • Can you reproduce this issue with the current release?
  • Can you reproduce this issue with the beta channel?
  • Can you reproduce this issue with the nightly channel?

Other Additional Information:

  • Does the issue resolve itself when disabling Brave Shields?
  • Does the issue resolve itself when disabling Brave Rewards?
  • Is the issue reproducible on the latest version of Chrome?

Miscellaneous Information:

cc @MadhaviSeelam @boocmp

@srirambv
Copy link
Contributor

srirambv commented Sep 21, 2022

Maybe same as #25378. Issue doesn't seem to be specific to meek-azure.

@stephendonner
Copy link
Author

Also, meek-azure isn't very reliable, itself:

Screen Shot 2022-09-21 at 1 39 09 PM

@boocmp
Copy link

boocmp commented Oct 5, 2022

It seems the meek PT is completely broken. I can't get it work in either Brave or Tor.

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

3 participants