You might be running into this problem:
opened 04:36AM - 06 Mar 21 UTC
closed 04:59AM - 06 May 21 UTC
OS/Desktop
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).
In Brave 1.26, you will be able to recover from that bad state by turning off private windows with Tor and turning back on again. At the moment, the only fix is to manually delete the tor data directory within your browser profile.
1 Like