Tor broken with Brave 1.23.75

Description of the issue:
Private Browsing with Tor is no longer working in Brave Desktop for MacOS Version 1.23.75 Chromium: 90.0.4430.93 (Official Build) (x86_64)

It was working in the previous version

How can this issue be reproduced?

  1. Open Brave Browser in MacOS Mojave 10.14.6
  2. Menu > New Private Window with Tor
  3. New Tor window opens.
  4. At the bottom of the page, Tor Status shows Disconnected.
  5. Type brave.com in the URL bar
  6. The wheel spins indefinitely without connecting

Expected result:
Should establish a connection and be able to navigate to a web site.

Brave Version( check About Brave):
Brave Desktop for MacOS Version 1.23.75 Chromium: 90.0.4430.93 (Official Build) (x86_64)

Additional Information:

If Tor status shows as “Disconnected”, it is normal that you won´t be able to use Tor. That is where the problem is. When you launch New Private Window with Tor, Tor status should display “Initialising” and a percentage that keeps increasing until it shows “Connected”, this takes two or three seconds.

If you don´t see that, it could be something in your network or operating system blocking Tor. Antivirus? Firewall? College? ISPs in dictatorships like China?

It might also be something in Windows 7, which no longer receives security or software updates and has been abandoned by Microsoft.

CORRECTION : This issue is on MacOS Mojave 10.14.6

I had a brain cramp when I first reported this issue.

The Tor Status Disconnected message remains after even 5 minutes.

Brave 1.23.75 on Windows 7 works fine with Tor and connects within a few seconds.

@braveman,
I have some other issues encountering this as well so I’m glad you reported. Can you share a screen shot of the General info and Logs tab found on the brave://tor-internals page?

From brave://tor-internals

General Info tab:

Tor Version: 0.4.5.7
Tor Process Id: 84484
Tor Proxy URI: socks5://127.0.0.1:60321
Tor Connection Status: Disconnected
Tor Initialization Progress:

Logs tab:

May 03 14:22:54.000 [notice] Tor 0.4.5.7 opening new log file.
May 03 14:22:54.520 [notice] We compiled with OpenSSL 101010bf: OpenSSL 1.1.1k  25 Mar 2021 and we are running with OpenSSL 101010bf: 1.1.1k. These two versions should be binary compatible.
May 03 14:22:54.523 [notice] Tor 0.4.5.7 running on Darwin with Libevent 2.1.11-stable, OpenSSL 1.1.1k, Zlib 1.2.11, Liblzma N/A, Libzstd N/A and Unknown N/A as libc.
May 03 14:22:54.523 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
May 03 14:22:54.523 [notice] Configuration file "/nonexistent" not present, using reasonable defaults.
May 03 14:22:54.526 [notice] Opening Socks listener on 127.0.0.1:0
May 03 14:22:54.526 [notice] Socks listener listening on port 60321.
May 03 14:22:54.526 [notice] Opened Socks listener connection (ready) on 127.0.0.1:60321
May 03 14:22:54.526 [notice] Opening Control listener on 127.0.0.1:0
May 03 14:22:54.527 [notice] Control listener listening on port 60322.
May 03 14:22:54.527 [notice] Opened Control listener connection (ready) on 127.0.0.1:60322
May 03 14:22:54.000 [notice] Bootstrapped 0% (starting): Starting
May 03 14:22:54.000 [notice] Starting with guard context "default"
May 03 14:22:54.000 [notice] New control connection opened from 127.0.0.1.
May 03 14:22:54.000 [notice] Tor 0.4.5.7 opening log file.

@braveman,
Appreciate the information – will return when I know more. Thanks for your patience.

1 Like

Still not working with Version 1.24.85 Chromium: 90.0.4430.212 (Official Build) (x86_64)

From brave://tor-internals

General Info tab:

Tor Version: 0.4.5.8
Tor Process Id: 1545
Tor Proxy URI: socks5://127.0.0.1:63690
Tor Connection Status: Disconnected

Tor Initialization Progress:

Logs tab:

May 16 18:55:02.000 [notice] Tor 0.4.5.8 opening new log file.
May 16 18:55:02.593 [notice] We compiled with OpenSSL 101010bf: OpenSSL 1.1.1k  25 Mar 2021 and we are running with OpenSSL 101010bf: 1.1.1k. These two versions should be binary compatible.
May 16 18:55:02.607 [notice] Tor 0.4.5.8 running on Darwin with Libevent 2.1.11-stable, OpenSSL 1.1.1k, Zlib 1.2.11, Liblzma N/A, Libzstd N/A and Unknown N/A as libc.
May 16 18:55:02.608 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
May 16 18:55:02.608 [notice] Configuration file "/nonexistent" not present, using reasonable defaults.
May 16 18:55:02.616 [notice] Opening Socks listener on 127.0.0.1:0
May 16 18:55:02.616 [notice] Socks listener listening on port 63690.
May 16 18:55:02.617 [notice] Opened Socks listener connection (ready) on 127.0.0.1:63690
May 16 18:55:02.617 [notice] Opening Control listener on 127.0.0.1:0
May 16 18:55:02.617 [notice] Control listener listening on port 63691.
May 16 18:55:02.617 [notice] Opened Control listener connection (ready) on 127.0.0.1:63691
May 16 18:55:02.000 [notice] Bootstrapped 0% (starting): Starting
May 16 18:55:02.000 [notice] Starting with guard context "default"
May 16 18:55:02.000 [notice] New control connection opened from 127.0.0.1.
May 16 18:55:02.000 [notice] Tor 0.4.5.8 opening log file.

Still not working with Version 1.25.70 Chromium: 91.0.4472.77 (Official Build) (x86_64) :neutral_face:

Still not working with Version 1.25.73 Chromium: 91.0.4472.106 (Official Build) (x86_64)

From brave://tor-internals

Tor Version: 0.4.5.9
Tor Process Id: 40930
Tor Proxy URI: socks5://127.0.0.1:54315
Tor Connection Status: Disconnected
Tor Initialization Progress:

Logs tab:

Jun 20 11:44:52.000 [notice] Tor 0.4.5.9 opening new log file.
Jun 20 11:44:52.222 [notice] We compiled with OpenSSL 101010bf: OpenSSL 1.1.1k 25 Mar 2021 and we are running with OpenSSL 101010bf: 1.1.1k. These two versions should be binary compatible.
Jun 20 11:44:52.236 [notice] Tor 0.4.5.9 running on Darwin with Libevent 2.1.11-stable, OpenSSL 1.1.1k, Zlib 1.2.11, Liblzma N/A, Libzstd N/A and Unknown N/A as libc.
Jun 20 11:44:52.236 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Jun 20 11:44:52.236 [notice] Configuration file “/nonexistent” not present, using reasonable defaults.
Jun 20 11:44:52.244 [notice] Opening Socks listener on 127.0.0.1:0
Jun 20 11:44:52.244 [notice] Socks listener listening on port 54315.
Jun 20 11:44:52.245 [notice] Opened Socks listener connection (ready) on 127.0.0.1:54315
Jun 20 11:44:52.245 [notice] Opening Control listener on 127.0.0.1:0
Jun 20 11:44:52.245 [notice] Control listener listening on port 54316.
Jun 20 11:44:52.245 [notice] Opened Control listener connection (ready) on 127.0.0.1:54316
Jun 20 11:44:52.000 [notice] Bootstrapped 0% (starting): Starting
Jun 20 11:44:52.000 [notice] Starting with guard context “default”
Jun 20 11:44:52.000 [notice] New control connection opened from 127.0.0.1.
Jun 20 11:44:52.000 [notice] Tor 0.4.5.9 opening log file.

@Mattches , any idea when this could be fixed? It’s a really useful feature!

@braveman,
I’ve pinged the team on this again – apologies for the inconvenience. We do appreciate your patience and your updates on the issue.

1 Like

Same issue, 1.26.74, Win10 x64

BUT over in this thread they seem to have a solution:

However, does anybody have the equivalent for Windows machine? I.e to “manually delete the tor data directory within your browser profile”?

Thanx