Description of the issue:
Brave is my default browser. It is up-to-date.
At many sites that I visit (including https://community.brave.com) all I see is
Your connection is not private
Attackers might be trying to steal your information from www.community.brave.comcom (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_DATE_INVALID
When I click the “Advanced” button I see the following:
community.brave.com normally uses encryption to protect your information. When Brave tried to connect to community.brave.com this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be community.brave.com, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Brave stopped the connection before any data was exchanged.
You cannot visit community.brave.com right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later.
Actual Result (gifs and screenshots are welcome!):
There is no attack. Brave is faulty. When I use another browser (I am using Firefox right now to access community.brave.com), there is no problem.
Expected result:
I want to be able to access every web site I choose to visit. So, I have no interest in trying to fix this prohibition of Brave, I want to simply completely disable this nonsense feature. Make it go away. I have been using the web since the mid-90s. I don’t care if the site uses http or https. Please tell me how to kill this ‘feature.’ I want it dead. 100% gone. Please.
Reproduces how often:
This happens to about 1/5th of the sites I visit. It is making Brave.com almost unusable and may force me to switch to another browser.
Operating System and Brave Version(See the About Brave page in the main menu):
iMac 24-inch, early 2009
chip: 3.06 GHz Intel Core 2 Duo
memory: 4 GB 1067 MHz DDR3
graphics: ATI RAdeon HD 4850 512 MB
Brave is up to date
Version 1.30.87 Chromium: 94.0.4606.71 (Official Build) (x86_64)
Additional Information:
At another thread there was the suggestion to ENABLE:
Allow invalid certificates for resources loaded from localhost.
Allows requests to localhost over HTTPS even when an invalid certificate is presented. – Mac, Windows, Linux, Chrome OS, Android#allow-insecure-localhost
That is now enabled, and it does not fix the problem.