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
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
The web site.
100%
MacOS
Version 1.2.43 Chromium: 79.0.3945.130 (Official Build) (64-bit)
@kevinp2 -
tor client updater version is 1.0.8./Users/<user-name>/Library/Application Support/BraveSoftware/Brave-Browser/tor/data/tor.logHi
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 notifications@github.com
wrote:
@kevinp2 https://github.com/kevinp2 - Are you able to reproduce this
issue with v1.3.115. f so could you check:
- 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/
/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
https://github.com/brave/brave-browser/issues/8129?email_source=notifications&email_token=AAEU3DMK6TLFR2G2LJXT27LRCLL2PA5CNFSM4KRULLD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELNHVSA#issuecomment-584743624,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEU3DPQCQ4KHOXH4HUTDLDRCLL2PANCNFSM4KRULLDQ
.
--
Kevin
@jumde tor.log did not survive the email trip so I have attached it here.
Thank you @kevinp2, we were able to reproduce this issue on High Sierra. We are looking into this, stay tuned.
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
I find it interesting that in a similar issue in El Capitan, the user states that he had success with High Sierra. https://github.com/brave/brave-browser/issues/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
Still broken on Version 1.4.95 Chromium: 80.0.3987.122 (Official Build) (64-bit)
@kevinp2 - We just released an update of the extension, could you please try these steps:
Let me know if you're still running into any issues.
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 notifications@github.com
wrote:
@kevinp2 https://github.com/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โ
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/brave/brave-browser/issues/8129?email_source=notifications&email_token=AAEU3DJHCI6EG6O7SPM3ITTRFSQQFA5CNFSM4KRULLD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENSI34Q#issuecomment-593792498,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEU3DOQJBSIAMHFDNXSYFDRFSQQFANCNFSM4KRULLDQ
.
--
Kevin
@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! ๐
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?
@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)
@jumde
I do notice, on several other updaters their status is: Status - Update error
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
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
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:
/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?
- 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
@jumde
Now, it's working!
Ok awesome! Glad to hear ๐
@jumde That was without doing anything.. I hadn't seen your response come through! LOL.
Most helpful comment
Thank you @kevinp2, we were able to reproduce this issue on High Sierra. We are looking into this, stay tuned.