-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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 timeout is too short #24978
Comments
The proposed solution (thanks to @rmcfadden3 and @aguscruiz) is to add a second timer:
|
cc @boocmp |
@boocmp any update on above issue as error message shown for each status takes > 2 minutes https://bravesoftware.slack.com/archives/C85NV6NSG/p1671045026328789 |
cc @rebron on #24978 (comment) |
Removing We decided to confirm that the expected messages display and @MadhaviSeelam will log a follow up issue for the timing if it is still problematic. cc @rebron |
Verification passed on
Verified Tor connection indicator works properly when connection is successful Verified Tor connection indicator works properly when connection has problems Note used STR from #24978 (comment) Connection takes longer than expected Time between states was >2minutes Logged |
Verified on
Once I open the Tor windows I am seeing the different messages as below:
|
Verification
Retested with
|
Verification
|
Brave | 1.47.171 Chromium: 109.0.5414.87 (Official Build) (x86_64) |
---|---|
Revision | 2dc18eb511c56e012081b4abc9e38c81c885f7d4-refs/branch-heads/5414@{#1241} |
OS | macOS Version 11.7.2 (Build 20G1020) |
- installed
1.47.171
- launched Brave
- opened
brave://settings/privacy
in a new-tab - enabled
Use Bridges
in Tor windows section - selected
meek-azure
inSelect a built-in-bridge
drop-down menu - clicked
Apply changes
- clicked hamburger menu >>
New private window with Tor
Once I opened the Tor windows I am seeing the different messages as below:
- 1st message is
Disconnected
remains on the TOR windows around 2 to 3 seconds - 2nd message
Tor connection failed
flashes and go off in a fraction of seconds - 3rd message
Tor is connecting
remains on the TOR windows for around 9 mins 15 seconds - 6th message
Tor connection failed
is shown after 9 mins 15 seconds
1st msg | 2nd msg | 3rd msg | 4th msg | 5th msg | 6th msg |
---|---|---|---|---|---|
The Meek-Azure bridge has begun to show signs of life, it is trying to create a connection and periodically sends a progress message (14% or 15% of Handshake with a relay done). We're resetting the connection timer at every progress message so this causes the messages "still connecting" and "Tor is connecting" to swap each other until the bridge stops trying to connect. We need to check 'count' field of the progress message to determine that is the same as we received early and ignore it. |
When opening a Tor window, the tor daemon needs to start up and connect to the Tor network. While it's doing that, we should a notification:
Once it's done, we change to a successful notification:
In cases of failure, we show an error:
The problem is that the error notification is shown unconditionally after a 30-sec timeout. Sometimes it takes longer than 30s for a connection to be established and in that case, we show the error notification and then a few seconds later, it gets replaced with a success notification, which is pretty confusing.
The text was updated successfully, but these errors were encountered: