For anyone here encountering this issue, can you try launching the tor binary from the terminal? You can do this by entering the following command:
cd ~/Library/Application\ Support/BraveSoftware/Brave-Browser/cldoidikboihgcjfkhdeidbpclkineef/1.0.13/
./tor-0.4.4.6-darwin-brave-0Hi, What do you mean with “from the terminal”
I’ve copied the link; I just got search results like:
Please help
@iMaan,
On your mac, open the Terminal application. Then copy the command I provided in my previous reply, paste it into the terminal and hit enter.
I copied the command into the terminal and hit enter. Nothing changed.
Then I restarted my MacBook and checked again; result still the same “Tor-status disconnected”
How can??
Do you have any idea what the problem could be???
Could anybody help me with the TOR window.
It’s still; “Tor-status disconnected” !!!
how to connect again??
an 27 15:07:17.130 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Jan 27 15:07:17.130 [notice] Configuration file “/Users/jenkins/jenkins/workspace/brave-tor-client-build/tor-0.4.4.6/root/etc/tor/torrc” not present, using reasonable defaults.
Jan 27 15:07:17.145 [notice] Opening Socks listener on 127.0.0.1:9050
Jan 27 15:07:17.145 [notice] Opened Socks listener on 127.0.0.1:9050
Jan 27 15:07:17.000 [notice] Bootstrapped 0% (starting): Starting
Jan 27 15:07:17.000 [notice] Starting with guard context “default”
Jan 27 15:07:18.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Who is user jenkins ?
Tor works here but is unusable due to unresolveable captcha
I’ve been experience this fora couple of weeks and c through a couple of updates.
OS X 10.16.7
[
Version 1.19.92 Chromium: 88.0.4324.152 (Official Build) (x86_64)
]
I ran the above terminal command:
./tor-0.4.4.6-darwin-brave-0
Feb 06 13:27:20.863 [notice] Tor 0.4.4.6 running on Darwin with Libevent 2.1.11-stable, OpenSSL 1.0.2u, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A.
Feb 06 13:27:20.863 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Feb 06 13:27:20.863 [notice] Configuration file “/Users/jenkins/jenkins/workspace/brave-tor-client-build/tor-0.4.4.6/root/etc/tor/torrc” not present, using reasonable defaults.
Feb 06 13:27:20.864 [notice] Opening Socks listener on 127.0.0.1:9050
Feb 06 13:27:20.864 [notice] Opened Socks listener on 127.0.0.1:9050
Feb 06 13:27:20.000 [notice] Bootstrapped 0% (starting): Starting
Feb 06 13:27:20.000 [notice] Starting with guard context “default”
Feb 06 13:27:21.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Feb 06 13:27:22.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Feb 06 13:27:22.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
Feb 06 13:27:22.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
Feb 06 13:27:22.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
Feb 06 13:27:22.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
Feb 06 13:27:23.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus
Feb 06 13:27:24.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Feb 06 13:27:25.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs
Feb 06 13:27:25.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.
Feb 06 13:27:25.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
Feb 06 13:27:25.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7077, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
Feb 06 13:27:26.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors
Feb 06 13:27:27.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.
Feb 06 13:27:27.000 [notice] Bootstrapped 55% (loading_descriptors): Loading relay descriptors
Feb 06 13:27:28.000 [notice] Bootstrapped 61% (loading_descriptors): Loading relay descriptors
Feb 06 13:27:28.000 [notice] Bootstrapped 69% (loading_descriptors): Loading relay descriptors
Feb 06 13:27:28.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Feb 06 13:27:28.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
Feb 06 13:27:29.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
Feb 06 13:27:29.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
Feb 06 13:27:29.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Feb 06 13:27:29.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Feb 06 13:27:30.000 [notice] Bootstrapped 100% (done): Done
I have had this same issue for months. I am on MacOS Catalina, currently on Version 10.15.7. Normal and private windows work just fine but a Private Window with Tor shows the message below and trying to navigate to any site will spin for minutes and then eventually show an error that the page cannot be reached.
I do not have a virus scanner and my firewall is not blocking the traffic. I can use the official Tor browser just fine.
I’ve updated Brave at least once during that time. I am currently running on the latest version available on the Brave site:
I am pretty well frustrated with this. Brave was working fine until about a month ago Tor tabs stopped working entirely. Just spins and hangs. Was on catalina and have since upgraded to Big Sur. Same issue persists.
Component “Brave Tor Client Updater (Mac)” says it’s up to date at v1.0.14
Yes thats an unrelated issue but I’ve had that problem on some sites as well, where the Brave Tor browser could never solve [only certain specific] captchas. Had to use official Tor Browser as a workaround, and now I have to do the same since Tor stopped working entirely and seems it happens to most people on Mac at various times and no fix or acknowledgment in sight
I was running brave from the Terminal in Big Sur, looks like no connection is made to the tor daemon:
$ /Applications/Brave\ Browser.app/Contents/MacOS/Brave\ Browser
[9611:775:0225/224101.306079:ERROR:brave_new_tab_message_handler.cc(184)] Ads service is not initialized!
[9611:775:0225/224102.163497:ERROR:CONSOLE(0)] “Unchecked runtime.lastError: Not available in Tor/incognito/guest profile”, source: chrome://newtab/ (0)
[9611:775:0225/224102.165796:ERROR:CONSOLE(0)] “Unchecked runtime.lastError: Not available in Tor/incognito/guest profile”, source: chrome://newtab/ (0)
[9611:775:0225/224102.234981:ERROR:CONSOLE(0)] “Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.”, source: chrome://newtab/ (0)
Feb 25 22:41:02.831 [notice] Tor 0.4.5.6 running on Darwin with Libevent 2.1.11-stable, OpenSSL 1.1.1i, Zlib 1.2.11, Liblzma N/A, Libzstd N/A and Unknown N/A as libc.
Feb 25 22:41:02.831 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Feb 25 22:41:02.831 [notice] Configuration file “/nonexistent” not present, using reasonable defaults.
Feb 25 22:41:02.836 [notice] Opening Socks listener on 127.0.0.1:0
Feb 25 22:41:02.837 [notice] Socks listener listening on port 52566.
Feb 25 22:41:02.837 [notice] Opened Socks listener connection (ready) on 127.0.0.1:52566
Feb 25 22:41:02.837 [notice] Opening Control listener on 127.0.0.1:0
Feb 25 22:41:02.837 [notice] Control listener listening on port 52567.
Feb 25 22:41:02.837 [notice] Opened Control listener connection (ready) on 127.0.0.1:52567
That’s all that comes up; it’s the same issue @brow was reporting I just wanted to confirm that this is exactly the same for me. Brave reports “disconnected” and it never connects. Tor Browser is working on the same system.
For me the Tor option don’t exist, I have only the private session option, any idea?
Still running into this issue every couple months, no idea why. 4th time have now had to uninstall/remove app data/reinstall
Hey Mattches,
I was able to run the tor binary from terminal, and it appears to start and run normally, but the tor window in the browser still says “Disconnected”. It almost seems like the browser itself isn’t able to invoke the tor binary for some reason. Is there a log generated when you select “New Private Window with Tor” that would show that startup sequence (and any potential failures)?
@evanschmitt,
I believe that we have started implementing some fixes that should help with Tor windows getting stuck in Disconnected state:
I just read through the comments on github and it turns out removing the “tor” folder in “~/Library/Application Support/BraveSoftware/Brave-Browser/” fixed the issue. I’m now able to use the Private Window with Tor.
To anyone else reading this, here’s how I fixed the issue on my Mac:
~/Library/Application Support/BraveSoftware/Brave-Browser/
After I restarted Brave, Tor private windows started working again. I’m using MacOS Catalina 10.15.7 and the latest regular release of Brave (Version 1.25.70 Chromium: 91.0.4472.77 (Official Build) (x86_64).
Where’s the folder to delete if you’re running Linux? Is it in:
/home/local name/.config/BraveSoftware/Brave-Browser
?
Update: It does seem to work. I saw it initialize and quickly went into a couple of pages. Same principle despite the different names of folders. So yeah works in Linux (Mint.) If anything changes, I’ll let you all know. Thanks.
I did what [@evanschmitt] did.
It seems this is caused by some Tor process not shutting down correctly. For me the following worked:
