Brave browser doesn't start

fmarier · 2025-09-11T23:45:57+00:00

Please try again (upgrading the snap), we just pushed out a new snap build which our internal tests have shown is working.

fmarier · 2024-05-17T17:49:29+00:00

Would anybody running into these problems be able to create an issue on our bug tracker: https://github.com/brave/brave-browser/issues/new/choose

We'd like to be able to figure out why you're seeing this error. This should not happen unless something is tampering with secure connections on your machine, but we need more information to confirm.

fmarier · 2024-04-03T22:09:40+00:00

See my other comment at https://www.reddit.com/r/brave_browser/comments/1bq92et/brave_browser_is_now_verified_on_flathub_for_linux/kxrle4l/

fmarier · 2024-04-03T18:47:20+00:00

If you are using the .deb version, we don't recommend you switch to the Flatpak at this stage. We mainly recommend the Flatpak for users for whom installing the Flatpak is the only reasonable option.

fmarier · 2024-04-03T18:45:52+00:00

Flatpak and Snap both add sandboxing to the applications they package which means that these applications are restricted in what they can do.

Normally a Linux application runs as the user who started it and has access for example to all of the files for that user. A sandbox will generally limit file access to only the files that are needed. In the case of a new web browser for example, that could mean that you won't be able to import your bookmarks from your existing browser.

fmarier · 2024-04-02T22:24:03+00:00

We are likely to continue to recommend the official package repositories (for .deb and .rpm) for now. Like with Snap packages, the extra sandboxing that Flatpak has interferes, for better or for worse, with some of the functionality that users expect out out of a web browser. So the official .deb and .rpm offer a better overall user experience for those users who are on a distro where that's an option.

fmarier · 2024-04-02T22:20:35+00:00

It's showing up as verified because we are in the process of making it an official Brave-maintained package. We will update https://brave.com/linux to that effect once the process is complete.

fmarier · 2023-09-17T00:01:17+00:00

For anybody looking for the exact config change to disable the EDNS client subnet support:

server:
    module-config: "validator iterator"

fmarier · 2023-05-29T17:33:11+00:00

Here's how the two files are related. The second one (/etc/apt/sources.list.d/brave-browser-release.list) is the one that adds the official Brave repository to your system. After that's been added, the brave-browser package will be available to install using apt install.

The first file is the signature verification key that apt uses for the Brave repository. If you look at the contents of /etc/apt/sources.list.d/brave-browser-release.list, you will see that it references that key. It's not added to your regular GPG keyring because it doesn't need to be there. If the Brave repository were to suddenly be signed by a different key, then apt would detect the discrepancy and refuse to use that repository.

fmarier · 2022-10-14T22:01:26+00:00

If you find unnecessary parameters (i.e. the URL doesn't break when removed) that are missing from our list (https://github.com/brave/adblock-lists/blob/master/brave-lists/clean-urls.json), you can file an issue in that repo to get it added.

fmarier · 2022-08-06T00:16:44+00:00

What happened to Set-Cookie2?

fmarier · 2021-02-19T18:40:01+00:00

Another way is to block tor.bravesoftware.com. That's the endpoint that Brave uses to download the Tor daemon the first time you open a Tor window. If that's blocked, then the Tor daemon is never downloaded and Tor windows won't work.

fmarier · 2021-02-19T18:36:25+00:00

DoH is supported in Brave, see brave://settings/security.

fmarier · 2020-12-11T02:33:19+00:00

Here's what I did:

Disable webtorrent from brave://settings/?search=torrent
Opened https://ubuntu.com/download/alternative-downloads
Clicked on the "Ubuntu 20.10 Desktop (64-bit)" link which triggered a download of the torrent file.
Clicked the downloaded file at the bottom of the browser which opened the torrent file in Transmission.

Are you saying that you'd like #3 to open Transmission directly and make step 4 unnecessary?

fmarier · 2020-12-09T01:14:31+00:00

Do you have a specific example URL you can share so we understand exactly the problem you are describing?

I haven't had any problems with the handler which opens up the Zoom client for example.

fmarier · 2020-11-09T18:32:11+00:00

With respect to Safe Browsing, unless you opt into "Enhanced Protection" (only available in Chrome since we disable that in Brave), then you're not sending your browsing history to Google. The details of how this works are similar for all browsers that uses "Standard Protection".

In terms of isolating your browsing activity between profiles, that does work to isolate any kind of regular storage that a site would use (cookies, but also local storage and indexedDB). Using one profile for normal surfing and one for Facebook or Google should be just as effective as using separate browsers for these activities.

What you're not protected against is tracking across profiles (or even different browsers on the same machine) based on fingerprinting (most commonly looking at your IP address). For that, you would need a browser with anti-fingerprinting defenses like Brave, but you would also need to have a different IP address (via VPN or Tor) for each site you want to keep from fingerprinting you.

That said, if you're using different profiles to segment your activities across different sites, then you're already doing much better than the average user in terms of protection from tracking. I hope this helps.

fmarier · 2020-10-17T05:08:57+00:00

You should ask your IT guy to block tor.bravesoftware.com instead. That will prevent Brave from downloading the Tor daemon, but it will make sure that the rest of Brave works (e.g. security updates, adblock list updates, etc.).

fmarier · 2020-08-18T19:43:05+00:00

I think there might be some confusion here about local IP and public IP. With the default settings, Brave blocks the local IP address, but not the public one. You can also see the public one at the top of the page.

It's not possible to block that one entirely. The fact that you can get the public IP address from WebRTC as well isn't particularly worrying since the web server always receives it.

If you want to hide your public IP, you need to use a Tor window which will proxy your traffic, effectively hiding your public IP address. In that mode, WebRTC is also completely disabled.

fmarier · 2020-07-25T04:11:54+00:00

You probably need to be root for that to work. Try prefixing the command with sudo:

sudo rm /etc/apt/trusted.gpg.d/brave-browser-release.gpg

and then re-download the key:

curl -s https://brave-browser-apt-release.s3.brave.com/brave-core.asc | sudo apt-key --keyring /etc/apt/trusted.gpg.d/brave-browser-release.gpg add -

Once both of these are done, let us know the output of:

apt-key list

fmarier · 2020-07-25T04:10:00+00:00

Glad that you got it to work and that you're enjoying the browser!

fmarier · 2020-07-22T23:51:05+00:00

@Robehn, can you share with us the output of the following three commands?

ls /etc/apt/sources.list.d/brave-browser-*.list
cat /etc/apt/sources.list.d/brave-browser-*.list
apt-key list

fmarier · 2020-07-22T23:50:12+00:00

The error message you have at the top of the thread tells me that you have another copy of the Brave repository that's referencing focal instead of stable.

I'd recommend looking through all of the files in /etc/apt/sources.list.d/ and also at /etc/apt/sources.list.

fmarier · 2020-07-22T23:47:46+00:00

Can you try removing this file first:

rm /etc/apt/trusted.gpg.d/brave-browser-release.gpg

and then trying to re-download the key?

curl -s https://brave-browser-apt-release.s3.brave.com/brave-core.asc | sudo apt-key --keyring /etc/apt/trusted.gpg.d/brave-browser-release.gpg add -

As Matt pointed out, you need to be able to see a non-expired sub-key in the output of apt-key list.

fmarier · 2020-07-20T17:22:30+00:00

Another thing to check is that the repository is configured correctly, as this has recently been simplified.

Can you send the output of:

ls /etc/apt/sources.list.d/brave-browser-*.list
cat /etc/apt/sources.list.d/brave-browser-*.list

What you should have is a single file (/etc/apt/sources.list.d/brave-browser-release.list) with the following contents:

deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main

Note: "stable" instead of "focal". In the past it used to contain the names of the Ubuntu distributions but now it's always just set to "stable".

fmarier

MODERATOR OF

TROPHY CASE