Here’s what this problem looks like in the most popular clients on the web. First, however, you need to be able to recognize it in your browser. We’ll dive into the solutions to the NET::ERR_CERT_COMMON_NAME_INVALID error shortly. NET::ERR_CERT_COMMON_NAME_INVALID Error Variations This can make it hard to pin down the correct solution, but a little patience will go a long way towards helping you fix the problem.

Your browser cache or SSL state has become corrupted.Īs you can see, many different factors can contribute to the NET::ERR_CERT_COMMON_NAME_INVALID error.A browser extension is interfering with your site’s SSL connection.Your antivirus software is blocking your SSL connection.Your site has a self-signed SSL certificate installed and your browser does not recognize it as valid or secure.You tried to switch your website to HTTPS without first installing an SSL certificate.Your SSL certificate does not account for www versus non-www variations of your domain.

However, there are other scenarios that could lead to this message appearing in your browser, including: Often, this means that the name on your certificate does not match the domain it’s installed on. So as the error message states, the root problem behind NET::ERR_CERT_COMMON_NAME_INVALID is that the common name on your SSL certificate is not valid for some reason. The ‘common name’ this error references is the domain on which an SSL certificate is installed.įor example, if you have a website at, the common name on your SSL certificate would be.

Understanding What Causes the NET::ERR_CERT_COMMON_NAME_INVALID Errorīefore we dive into what causes the NET::ERR_CERT_COMMON_NAME_INVALID error, let’s break down the relevant terms.

Fortinet vpn client fedora