Private with TOR won't work

Mattches · June 8, 2021, 4:56pm

@evanschmitt,
I believe that we have started implementing some fixes that should help with Tor windows getting stuck in Disconnected state:

github.com/brave/brave-browser

Tor state is `Disconnected` in New Private Window with Tor tab

opened 07:09PM - 18 May 21 UTC

stephendonner

OS/Desktop bug feature/tor regression

## Description Tor state is `Disconnected` in New Private Window with Tor tab ## Steps to Reproduce 1. new profile on `nightly` 2. open `File` | `Private Window with Tor` 3. scroll down to the bottom of the tab 4. look at `Tor Status` ## Actual result: ![tor-disconnected](https://user-images.githubusercontent.com/387249/118709171-80b00800-b7d1-11eb-8919-953c22d15238.png) Logs: ``` May 18 11:53:42.000 [notice] Tor 0.4.5.8 opening new log file. May 18 11:53:42.153 [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 18 11:53:42.161 [notice] Tor 0.4.5.8 running on Windows 8 [or later] 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 18 11:53:42.161 [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 18 11:53:42.162 [notice] Configuration file "C:\nonexistent" not present, using reasonable defaults. May 18 11:53:42.163 [warn] Path for GeoIPFile (<default>) is relative and will resolve to C:\Program Files\BraveSoftware\Brave-Browser-Nightly\Application\91.1.26.22\<default>. Is this what you wanted? May 18 11:53:42.163 [warn] Path for GeoIPv6File (<default>) is relative and will resolve to C:\Program Files\BraveSoftware\Brave-Browser-Nightly\Application\91.1.26.22\<default>. Is this what you wanted? May 18 11:53:42.166 [notice] Opening Socks listener on 127.0.0.1:0 May 18 11:53:42.166 [notice] Socks listener listening on port 57149. May 18 11:53:42.166 [notice] Opened Socks listener connection (ready) on 127.0.0.1:57149 May 18 11:53:42.166 [notice] Opening Control listener on 127.0.0.1:0 May 18 11:53:42.166 [notice] Control listener listening on port 57150. May 18 11:53:42.166 [notice] Opened Control listener connection (ready) on 127.0.0.1:57150 May 18 11:53:42.000 [notice] Bootstrapped 0% (starting): Starting May 18 11:53:42.000 [notice] Starting with guard context "default" May 18 11:53:42.000 [notice] New control connection opened from 127.0.0.1. May 18 11:53:42.000 [warn] Got mismatched authentication cookie May 18 11:53:43.000 [notice] Bootstrapped 5% (conn): Connecting to a relay May 18 11:53:43.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay May 18 11:53:43.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay May 18 11:53:43.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done May 18 11:53:43.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits May 18 11:53:43.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits May 18 11:53:43.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit May 18 11:53:44.000 [notice] Bootstrapped 100% (done): Done ``` General Info: ``` Tor Version: Tor Process Id: 11772 Tor Proxy URI: Tor Connection Status: Disconnected Tor Initialization Progress: ``` ## Expected result: Should say `Initializing %` until it's ready, at which point it'll read `Connected` under `Tor Status` ## Reproduces how often: It's not 100%, but it's pretty prevalent - @kjozwiak can give better insight as to how often this happens for him, as he's dogfooding on Windows ## Brave version (brave://version info) Brave | 1.26.22 Chromium: 91.0.4472.57 (Official Build) nightly (64-bit) -- | -- Revision | e3443317fa07f1e9997e4a9c738eddfefc3c0292-refs/branch-heads/4472_54@{#6} OS | Windows 10 OS Version 2009 (Build 21382.1)

github.com/brave/brave-browser

The Tor daemon can get into a bad state and break Tor windows

opened 04:36AM - 06 Mar 21 UTC

closed 04:59AM - 06 May 21 UTC

fmarier

OS/Desktop QA Pass-Linux QA Pass-Win64 QA Pass-macOS QA/Test-All-Platforms QA/Test-Plan-Specified QA/Yes feature/tor release-notes/include

I collected a browser profile from a user on Mac Catalina 10.15.7 who is unable …to use Tor windows in 1.21.73. All he sees in `brave://tor-internals` is: ``` Mar 04 09:28:01.000 [notice] Tor 0.4.5.6 opening new log file. Mar 04 09:28:01.248 [notice] We compiled with OpenSSL 1010109f: OpenSSL 1.1.1i 8 Dec 2020 and we are running with OpenSSL 1010109f: 1.1.1i. These two versions should be binary compatible. Mar 04 09:28:01.254 [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. Mar 04 09:28:01.254 [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 04 09:28:01.254 [notice] Configuration file "/nonexistent" not present, using reasonable defaults. Mar 04 09:28:01.263 [notice] Opening Socks listener on 127.0.0.1:0 Mar 04 09:28:01.264 [notice] Socks listener listening on port 56449. Mar 04 09:28:01.264 [notice] Opened Socks listener connection (ready) on 127.0.0.1:56449 Mar 04 09:28:01.264 [notice] Opening Control listener on 127.0.0.1:0 Mar 04 09:28:01.264 [notice] Control listener listening on port 56450. Mar 04 09:28:01.264 [notice] Opened Control listener connection (ready) on 127.0.0.1:56450 Mar 04 09:28:01.000 [notice] Bootstrapped 0% (starting): Starting Mar 04 09:28:02.000 [notice] Starting with guard context "default" Mar 04 09:28:02.000 [notice] New control connection opened from 127.0.0.1. Mar 04 09:28:02.000 [notice] Catching signal TERM, exiting cleanly. ``` @darkdh took a look and found that it is affected by some states in the `tor/data` folder. The circuit cannot be established and gets stuck in the bootstrapping phase at 0%. After deleting the folder, it returns to normal. We can't clear the `tor/data` directory on startup because it would cause long delays in creating new Tor circuits, but perhaps we can clear that directory on **update**. Right now, users can't recover from this state without blowing away their profile. If we could fix these problems automatically for them on update, then the recovery would be automatic, at the cost of longer circuit creation for everyone (only after an update though).

Topic		Replies	Views
New Private Window with Tor broken on Mac? "tor-0.3.5.8-darwin-brave-0" can't be opened Desktop Support bug	6	3533	November 4, 2024
When I open a new private tab with Tor, it says the Tor Status is disconnected Desktop Support	3	2400	November 4, 2024
Brave browser tor network not working in private window (disconnected) privacy , browser , tor	6	5817	July 13, 2022
Private window with tor never works Desktop Support macos	4	2839	June 13, 2022
Tor broken with Brave 1.23.75 Desktop Support macos	12	1463	September 3, 2021
Private Window with Tor always shows as Disconnected - Tor Browser works fine Desktop Support privacy	5	1384	November 21, 2024
Private window TOR tab problem Desktop Support	36	8046	October 18, 2018
TOR shows Blank Screen Web Compatibility performance , browser , tor	3	2364	July 11, 2022

Private with TOR won't work

Related topics