@M4YN3,
Can you try toggling the tor extension (brave://settings/extensions) on/off and tell me if this makes any difference?
If not, can you please share a screenshot of the logs tab on your brave://tor-internals page?
Out of curiosity, if you were to create a new browser profile (ensure you close your original profile so you only have one browser window with the new profile opened) and launch a tor window from it, do you get the same results?
I saw one tor process and closed it from the task manager, but now when I re-launch a new Private windows with Tor it doesn’t launch that process. Only after a reboot.
Some time ago, I found, that for the TOR process (of Brave Browser) to work, I first had to open a “New Window” (and leave it open). . . and then open a “New Private Window” (and leave it open) . . . and then open the “New Private Window with TOR”. (Leaving the two earlier windows open.) (I would not use multiple tabs.)
Thereafter, I would open another “New Private Window with TOR” for each subsequent entering of a URL address – when I wanted to maintain any earlier TOR window(s).
It just worked. Maybe that sequence of steps will work for you.
(I have a guess, why that works, but it’s late, and time for sleep.)
Glad to have another user having this problem. I raised this in a previous thread when ran out of patience and just switched to the TOR browser itself.
I did find that the status would change to “Connected” occasionally after an indeterminate period of time but that was unusable
Let’s hope the developers can find the issue
and download their TOR [Internet] Browser, and install that, you find that the TOR Browser is their own rendition of the Mozilla Firefox Internet browser.
TOR Browser is set up out-of-the-box, to the following (among other features):
Block Trackers
Defend Against Surveillance
Resist Fingerprinting
TOR Browser uses Multi-Layered Encryption:
“Your traffic is relayed and encrypted three times as it passes over the Tor network. The network is comprised of thousands of volunteer-run servers known as Tor relays.”
There is an article online, that recommends caution:
“Things You Should Not Do When You Are Using TOR Browser”
TOR Anonymity: Things Not To Do While Using TOR Browser
by Aditya Tiwari (who updated the article since 2014)
I experimented with using the TOR Browser, and with using the Brave “Private Window with TOR”. I prefer Brave Browser in general, so I stayed with it.
–
Brave Browser
Brave Browser File menu selections include:
Open New Window
Open New Private Window
Open New Private Window with TOR
Depending upon:
the version of Brave Browser for Mac OS
subsequent updates of Brave Browser for Mac OS
what Brave Browser window was opened first
and qualifications that satisfy readiness for opening a new window – determined by Brave developers
. . . there are both, conditions for which of the following selections are available / not-available, and thus, a status for each, when you select Brave Browser File menu:
Open New Window – always available as a selection
Open New Private Window – not always available, faded when unavailable
Open New Private Window with TOR – not always available, faded when unavailable
From my perspective, there seems to be a pattern of the behavior of those three selections . . . but at times, the pattern of behavior has been interrupted.
That on occasion, has resulted in, my NOT being able to directly select Open New Private Window with TOR . . . and on such occasions, I have had to Open at least one of the other two selections, first.
Opening one of the other two selections, first, causes the Open New Private Window with TOR selection, to become available.
There seems to be instability, non-reliability, re opening the TOR window, and I have been guessing, that certain conditions having to do with
independence from whatever is happening with any, and all, other windows / processes
independence that is finely tuned for the TOR purpose (Brave version respecting what the TOR Browser security policy and practices are)
. . . must be in place, before you get a TOR window.
If anything might upset the finely tuned nature and focused purpose (performance) that is required for a solid TOR window to occur . . . then the window will either
Not Open (selection is faded, unavailable status)
or
Close / Exit / Quit (and the related process(es) that you find for it, in the Task Managers and Activity Monitor, will end, or at least no longer participate in using CPU – “I think”).
The accompanying description for the (–site-per-process) flag:
“Enforces a one-site-per-process security policy: * Each renderer process, for its whole lifetime, is dedicated to rendering pages for just one site. * Thus, pages from different sites are never in the same process. * A renderer process’s access rights are restricted based on its site. * All cross-site navigations force process swaps. * < iframe >s are rendered out-of-process whenever the src = is cross-site. More details here: - “https://www.chromium.org/developers/design-documents/site-isolation” - “https://www.chromium.org/developers/design-documents/process-models” - The class comment in site_instance.h, listing the supported process models. IMPORTANT: this isn’t to be confused with --process-per-site (which is about process consolidation, not isolation). You probably want this one.”
Which fits what I had in mind, writing earlier above: “independence that is finely tuned for the TOR purpose” – in order to focus.
The TOR Browser people seem to me, to say: Do Not Mess with the Settings.
I do not know what Brave Browser Settings are adjusted, when using a New Private Window with TOR, but I respect the “Do Not Mess with the Settings” advice.
So, if either occurs:
TOR Browser window has a problem with a website, or
Brave Browser New Private Window with TOR has a problem with a website
. . . then I do not fiddle with the Settings. I maintain security – over convenience.
When a TOR process runs into a jam, the browser, its TOR window, or a TOR server, will end the delicate, sensitive connection.
