New Private window with Tor broken: ERR_PROXY_CONNECTION_FAILED #8129

kevinp2 · 2020-02-07T20:20:28Z

Description

With this newest release, the private Tor window is 100% broken. Navigating to any web page results in the error message: There is something wrong with the proxy server, or the address is incorrect

Steps to Reproduce

From the menu, select File > New Private Window with Tor
A new window opens with the dark purple background.
Go to any site, including brave.com

Actual result:

No internet
There is something wrong with the proxy server, or the address is incorrect.
Try:

Contacting the system admin
Checking the proxy address
ERR_PROXY_CONNECTION_FAILED

Expected result:

The web site.

Reproduces how often:

100%

Brave version (brave://version info)

MacOS
Version 1.2.43 Chromium: 79.0.3945.130 (Official Build) (64-bit)

Version/Channel Information:

Can you reproduce this issue with the current release? Yes
Can you reproduce this issue with the beta channel? Did not try.
Can you reproduce this issue with the dev channel? Did not try.
Can you reproduce this issue with the nightly channel? Did not try.

Other Additional Information:

Does the issue resolve itself when disabling Brave Shields? No
Does the issue resolve itself when disabling Brave Rewards? Did not try.
Is the issue reproducible on the latest version of Chrome? N/A

Miscellaneous Information:

jumde · 2020-02-11T17:11:02Z

@kevinp2 -

Are you able to reproduce this issue with v1.3.115?
Which version of macOS are you using?
Navigate to brave://components and check if tor client updater version is 1.0.8.
Could you share any errors that you see in: /Users/<user-name>/Library/Application Support/BraveSoftware/Brave-Browser/tor/data/tor.log

kevinp2 · 2020-02-11T17:35:10Z

Hi I am using MacOS High Sierra version 10.13.6 Brave Tor Client Updater (Mac) - Version: 1.0.8 Status - Up-to-date I looked at tor.log and have attached it to this email. Thanks!

…

On Tue, Feb 11, 2020 at 11:11 AM Pranjal Jumde ***@***.***> wrote: @kevinp2 <https://github.com/kevinp2> - Are you able to reproduce this issue with v1.3.115. f so could you check: 1. Which version of macOS are you using? 2. Navigate to brave://components and check if tor client updater version is 1.0.8. 3. Could you share any errors that you see in: /Users/<user-name>/Library/Application Support/BraveSoftware/Brave-Browser/tor/data/tor.log — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#8129?email_source=notifications&email_token=AAEU3DMK6TLFR2G2LJXT27LRCLL2PA5CNFSM4KRULLD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELNHVSA#issuecomment-584743624>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEU3DPQCQ4KHOXH4HUTDLDRCLL2PANCNFSM4KRULLDQ> .

-- Kevin

kevinp2 · 2020-02-11T17:35:57Z

tor.log

@jumde tor.log did not survive the email trip so I have attached it here.

jumde · 2020-02-11T22:22:32Z

Thank you @kevinp2, we were able to reproduce this issue on High Sierra. We are looking into this, stay tuned.

swinginsam · 2020-02-14T16:45:31Z

Same issue here with a very similar setup.

Brave Version 1.3.115 Chromium: 80.0.3987.87 (Official Build) (64-bit)

Hardware Overview:
Model Name: Mac Pro
Model Identifier: MacPro5,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 2.4 GHz
Number of Processors: 2
Total Number of Cores: 8
L2 Cache (per Core): 256 KB
L3 Cache (per Processor): 12 MB
Memory: 32 GB
Boot ROM Version: MP51.0084.B00
SMC Version (system): 1.39f11
SMC Version (processor tray): 1.39f11

System Software Overview:
System Version: macOS 10.13.6 (17G11023)
Kernel Version: Darwin 17.7.0
Boot Volume: Macintosh HD
Boot Mode: Normal
Secure Virtual Memory: Enabled
System Integrity Protection: Disabled

tor.log

I find it interesting that in a similar issue in El Capitan, the user states that he had success with High Sierra. #6629

Components: (seem to have a lot of errors here)

MEI Preload - Version: 1.0.5.0
Status - Component not updated

Brave Local Data Updater - Version: 1.0.22
Status - Up-to-date

Legacy TLS Deprecation Configuration - Version: 0.0.0.0
Status - Update error

Brave Ad Block Updater - Version: 1.0.480
Status - Up-to-date

Brave Tor Client Updater (Mac) - Version: 1.0.8
Status - Up-to-date

Subresource Filter Rules - Version: 9.3
Status - Update error

Crowd Deny - Version: 0.5
Status - Up-to-date

Certificate Error Assistant - Version: 7
Status - Update error

CRLSet - Version: 5696
Status - Update error

Safety Tips - Version: 0.0.0.0
Status - Update error

File Type Policies - Version: 36
Status - Update error

Origin Trials - Version: 0.0.0.0
Status - Update error

NTP sponsored images - Version: 1.0.18
Status - Up-to-date

Widevine Content Decryption Module - Version: 4.10.1582.2
Status - Component not updated

Brave HTTPS Everywhere Updater - Version: 1.0.14
Status - Up-to-date

kevinp2 · 2020-02-28T17:45:45Z

Still broken on Version 1.4.95 Chromium: 80.0.3987.122 (Official Build) (64-bit)

jumde · 2020-03-03T06:36:50Z

@kevinp2 - We just released an update of the extension, could you please try these steps:

Navigate to brave://components and check if the version of Tor Client Updater is 1.0.9
Open New Private window with Tor and check if you can open check.torproject.org

Let me know if you're still running into any issues.

kevinp2 · 2020-03-04T00:18:31Z

Brave Tor Client Updater (Mac) - Version: 1.0.9 Open New Private window with Tor now works properly. Thanks for the fix!

…

On Tue, Mar 3, 2020 at 12:36 AM Pranjal Jumde ***@***.***> wrote: @kevinp2 <https://github.com/kevinp2> - We just released an update of the extension, could you please try these steps: 1. Navigate to brave://components and check if the version of Tor Client Updater is 1.0.9 2. Open New Private window with Tor and check if you can open check.torproject.org — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#8129?email_source=notifications&email_token=AAEU3DJHCI6EG6O7SPM3ITTRFSQQFA5CNFSM4KRULLD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENSI34Q#issuecomment-593792498>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEU3DOQJBSIAMHFDNXSYFDRFSQQFANCNFSM4KRULLDQ> .

-- Kevin

bsclifton · 2020-03-04T06:17:33Z

@swinginsam can you please try the steps that @jumde shared above? Should be fixed 😄

If you can verify too, let's close this issue out! 😄

jessedmatlock · 2020-03-16T16:58:04Z

Still having this issue:
Mac OS X 10.13.6 High Sierra on MacBook Pro
Brave 1.4.96
Tor Updater 1.0.10

Tor Log shows the error:

Mar 16 11:44:24.000 [notice] Tor 0.3.5.8 opening new log file.
Mar 16 11:44:24.136 [notice] Tor 0.3.5.8 running on Darwin with Libevent 2.1.9-beta, OpenSSL 1.0.2q, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A.
Mar 16 11:44:24.138 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Mar 16 11:44:24.138 [notice] Configuration file "/nonexistent" not present, using reasonable defaults.
Mar 16 11:44:24.157 [notice] Opening Socks listener on 127.0.0.1:9350
Mar 16 11:44:24.158 [notice] Opened Socks listener on 127.0.0.1:9350
Mar 16 11:44:24.158 [notice] Opening Control listener on 127.0.0.1:0
Mar 16 11:44:24.158 [notice] Control listener listening on port 61108.
Mar 16 11:44:24.158 [notice] Opened Control listener on 127.0.0.1:0
Mar 16 11:44:24.000 [notice] Bootstrapped 0%: Starting
Mar 16 11:44:25.000 [notice] Starting with guard context "default"
Mar 16 11:44:25.000 [notice] Catching signal TERM, exiting cleanly.

This happened last week, I updated the Tor Updater from 1.0.8 and it was fixed.. now the proxy error is occurring again.

Attempting to view https://check.torproject.org/ gives 'No Internet' ERR_PROXY_CONNECTION_FAILED

Not running on a VPN

Any solution to this?

jessedmatlock · 2020-03-16T17:03:10Z

@jumde

of course, it's:
Brave Tor Client Updater (Mac) - Version: 1.0.10
Status - Component not updated (msg displays after clicking the update button)

jessedmatlock · 2020-03-16T17:08:20Z

@jumde
I do notice, on several other updaters their status is: Status - Update error

jessedmatlock · 2020-03-16T17:09:04Z

Here are the ones with that error.. in case it helps.

Certificate Error Assistant - Version: 7
Status - Update error

CRLSet - Version: 5740
Status - Update error

Safety Tips - Version: 0.0.0.0
Status - Update error

File Type Policies - Version: 0.0.0.0
Status - Update error

Origin Trials - Version: 0.0.0.0
Status - Update error

jessedmatlock · 2020-03-16T17:10:38Z

I updated each of those and all but the Origin Origin Trials updated, or didn't need an update, correctly. The Origin Trials still shows version 0.0.0.0. and update error

jumde · 2020-03-16T17:51:16Z

Thanks for confirming @revivemarketing. I missed the Tor Client version in your original message. Sorry about that.

Some of the components that you see on this list are not supported by Brave so seeing the Update Error for Origin Trials and other components is expected. We have an open issue to clean up the list.

I'm not able to reproduce this issue on my end. So if you could provide me with some additional info that'll be helpful:

Are you using OpenDNS? You can check this by navigating to: https://welcome.opendns.com/
Open terminal and run this:

/Applications/Brave\ Browser.app/Contents/MacOS/Brave\ Browser --user-data-dir=/tmp/test-tor

This starts the browser with a clean profile. Once the tor-client updater is downloaded. You can check by navigating to brave://components. Could you try opening check.torproject.org in the tor window and see if it works?

If tor doesn't work on a clean profile. Could you run these commands in Terminal and share the output of the second and third command. Thanks!

- cd $HOME/Library/Application\ Support/BraveSoftware/Brave-Browser/cldoidikboihgcjfkhdeidbpclkineef/1.0.10/
- shasum tor-0.3.5.8-darwin-brave-1 
- ./tor-0.3.5.8-darwin-brave-1

jessedmatlock · 2020-03-16T17:52:05Z

@jumde
Now, it's working!

jumde · 2020-03-16T17:52:41Z

Ok awesome! Glad to hear 👍

jessedmatlock · 2020-03-16T17:53:09Z

@jumde That was without doing anything.. I hadn't seen your response come through! LOL.

wknapik mentioned this issue Feb 7, 2020

Tor ERR_PROXY_CONNECTION_FAILED when network devices change on Linux #7899

Closed

fmarier mentioned this issue Feb 7, 2020

Expose Tor log in brave://tor #8106

Closed

bsclifton added the feature/tor label Feb 13, 2020

jumde self-assigned this Feb 13, 2020

jumde closed this as completed Mar 16, 2020

bbondy added this to the Closed / Invalid milestone Jun 3, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

New Private window with Tor broken: ERR_PROXY_CONNECTION_FAILED #8129

New Private window with Tor broken: ERR_PROXY_CONNECTION_FAILED #8129

kevinp2 commented Feb 7, 2020 •

edited

Loading

jumde commented Feb 11, 2020 •

edited

Loading

kevinp2 commented Feb 11, 2020 via email

kevinp2 commented Feb 11, 2020

jumde commented Feb 11, 2020

swinginsam commented Feb 14, 2020 •

edited

Loading

kevinp2 commented Feb 28, 2020

jumde commented Mar 3, 2020 •

edited

Loading

kevinp2 commented Mar 4, 2020 via email

bsclifton commented Mar 4, 2020

jessedmatlock commented Mar 16, 2020

jessedmatlock commented Mar 16, 2020

jessedmatlock commented Mar 16, 2020

jessedmatlock commented Mar 16, 2020

jessedmatlock commented Mar 16, 2020

jumde commented Mar 16, 2020

jessedmatlock commented Mar 16, 2020

jumde commented Mar 16, 2020

jessedmatlock commented Mar 16, 2020

New Private window with Tor broken: ERR_PROXY_CONNECTION_FAILED #8129

New Private window with Tor broken: ERR_PROXY_CONNECTION_FAILED #8129

Comments

kevinp2 commented Feb 7, 2020 • edited Loading

Description

Steps to Reproduce

Actual result:

Expected result:

Reproduces how often:

Brave version (brave://version info)

Version/Channel Information:

Other Additional Information:

Miscellaneous Information:

jumde commented Feb 11, 2020 • edited Loading

kevinp2 commented Feb 11, 2020 via email

kevinp2 commented Feb 11, 2020

jumde commented Feb 11, 2020

swinginsam commented Feb 14, 2020 • edited Loading

kevinp2 commented Feb 28, 2020

jumde commented Mar 3, 2020 • edited Loading

kevinp2 commented Mar 4, 2020 via email

bsclifton commented Mar 4, 2020

jessedmatlock commented Mar 16, 2020

jessedmatlock commented Mar 16, 2020

jessedmatlock commented Mar 16, 2020

jessedmatlock commented Mar 16, 2020

jessedmatlock commented Mar 16, 2020

jumde commented Mar 16, 2020

jessedmatlock commented Mar 16, 2020

jumde commented Mar 16, 2020

jessedmatlock commented Mar 16, 2020

kevinp2 commented Feb 7, 2020 •

edited

Loading

jumde commented Feb 11, 2020 •

edited

Loading

swinginsam commented Feb 14, 2020 •

edited

Loading

jumde commented Mar 3, 2020 •

edited

Loading