# Brave Desktop says connection not secure **URL:** \ **Category:** Help\ **Created:** [November 24, 2022, 2:17pm UTC](https://community.letsencrypt.org/t/brave-desktop-says-connection-not-secure/188384 "2022-11-24T14:17:00Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![shakty](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/shakty/32/65892_2.png) [@shakty](https://community.letsencrypt.org/u/shakty)\ **Post date:** [November 24, 2022, 2:17pm UTC](https://community.letsencrypt.org/t/brave-desktop-says-connection-not-secure/188384/1 "2022-11-24T14:17:00Z")
Hi, Recently, somebody has reported that my web site is not secure, however the certificate has been installed a long ago and the setup has been working nicely in the past. I tested that only Brave Desktop is throwing the warning (see images below), but it works fine with my other browsers (Opera, Firefox, Chrome). I wasn't able to verify the browser of the person who has reported the warning. Many thanks for any help! Info: - My domain is: [stateofcrypto.net](http://stateofcrypto.net) - I ran this command: certbot certificates It produced this output: Saving debug log to /var/log/letsencrypt/letsencrypt.log * * * Found the following certs: Certificate Name: [stateofcrypto.net](http://stateofcrypto.net) Serial Number: 355c22ffbd4d058a10f95e28bb4b1dac745 Key Type: RSA Domains: [stateofcrypto.net](http://stateofcrypto.net) [survey.stateofcrypto.net](http://survey.stateofcrypto.net) [www.stateofcrypto.net](http://www.stateofcrypto.net) [www.survey.stateofcrypto.net](http://www.survey.stateofcrypto.net) Expiry Date: 2023-02-20 21:48:10+00:00 (VALID: 88 days) Certificate Path: /etc/letsencrypt/live/stateofcrypto.net/fullchain.pem Private Key Path: /etc/letsencrypt/live/stateofcrypto.net/privkey.pem * * * I can login to a root shell on my machine (yes or no, or I don't know): Yes I'm using a control panel to manage my site (no, or provide the name and version of the control panel): Custom setup The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot): 1.32.0 Web server is Nginx and system is Linux, Debian, I believe. ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/6/c/6c9fa60e888d65394955f73756c51b57703ab4a6.png) ---
**Author:** ![shakty](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/shakty/32/65892_2.png) [@shakty](https://community.letsencrypt.org/u/shakty)\ **Post date:** [November 24, 2022, 2:25pm UTC](https://community.letsencrypt.org/t/brave-desktop-says-connection-not-secure/188384/2 "2022-11-24T14:25:01Z")
I forgot to mention that there is no warning for [www.stateofcrypto.net](http://www.stateofcrypto.net) in Brave. ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [November 24, 2022, 2:37pm UTC](https://community.letsencrypt.org/t/brave-desktop-says-connection-not-secure/188384/3 "2022-11-24T14:37:42Z")
I don't see anything wrong with your certs either. You are redirecting http requests to https and your cert contains both domain names. The [SSLLabs report gives you an A](https://www.ssllabs.com/ssltest/analyze.html?d=stateofcrypto.net&hideResults=on) The screen snap even says the cert is valid. Did the "Learn more" option give any other reasons for this error? Another volunteer may have come across this but you may want to search the Brave forums for a solution. ---
**Author:** ![danb35](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/danb35/32/70869_2.png) [@danb35](https://community.letsencrypt.org/u/danb35)\ **Post date:** [November 24, 2022, 2:51pm UTC](https://community.letsencrypt.org/t/brave-desktop-says-connection-not-secure/188384/4 "2022-11-24T14:51:17Z")
I can't duplicate this even in Brave: ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/a/f/af0995c6f26653e3c759df51fa1cf396989c4c01.png) ---
**Author:** ![shakty](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/shakty/32/65892_2.png) [@shakty](https://community.letsencrypt.org/u/shakty)\ **Post date:** [November 24, 2022, 3:46pm UTC](https://community.letsencrypt.org/t/brave-desktop-says-connection-not-secure/188384/5 "2022-11-24T15:46:45Z")
Many thanks for your answer! I will dig into the Brave forum then. ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [November 24, 2022, 5:29pm UTC](https://community.letsencrypt.org/t/brave-desktop-says-connection-not-secure/188384/6 "2022-11-24T17:29:01Z")
Maybe some dynamically loaded element over HTTP? Check the console or security tab in the developer toolbar. ---
**Author:** ![webprofusion](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/webprofusion/32/85310_2.png) [@webprofusion](https://community.letsencrypt.org/u/webprofusion)\ **Post date:** [November 25, 2022, 2:31am UTC](https://community.letsencrypt.org/t/brave-desktop-says-connection-not-secure/188384/7 "2022-11-25T02:31:04Z")
Brave has stricter settings regarding privacy protection than some other browsers do, as a result certain things will fail in Brave that will pass in other browsers. Currently your homepage seems fine though, if you click other pages such as About or Story the developer tools console is showing various ad trackers being blocked but these shouldn't result in "Not Secure". You should review the dev tools console to see if it's complaining of something specific. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [December 25, 2022, 2:31am UTC](https://community.letsencrypt.org/t/brave-desktop-says-connection-not-secure/188384/8 "2022-12-25T02:31:25Z")
Closed on December 25, 2022, 2:31am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.