In some cases, the problematic browser extension could be a reason for the error. First of all, try to open the website in Incognito window and if that solves the issue then no need to check extensions. Otherwise, follow the next steps: - Click the "three dots" button on the top right corner of your browser window
- Select More tools and Extensions
- Turn off extensions one by one to find culprit extension and delete it to fix the browser error.
- 3
Solution 3: Check Installed SSL certificate In most cases the issue comes from wrong SSL installed, it may simply not support the correct domain name or sub-domain. That makes a real mismatch result. For example, you issued and installed SSL for www.domain.tld, but installed it for sub.domain.tld which is not protected. You can check that with your browser.
In Chrome, you have to click to the "Not Secure" button located on the left side of the address bar, and then click to "Certificate". There you will see the details of SSL certificate using the field "issued to". The feature is available in most browsers. - You can also check that using Online SSL test by SSL Labs, that will be a more accurate result.
- Make sure Self-Signed SSL is not in use, as they are used for internal server purposes only.
- 4
Solution 4: Protection of both with/without WWW
All Single Domain SSL certificates we sell protect WWW and non-WWW version of your domain name. However, there are some certs that do not protect it by default. In that case, you may have a problem using redirection from WWW to non-WWW or opposite option.
The possible solution is to install a proper SSL certificate or remove any redirect and install Multi-Domain, or Wildcard SSL or even multiple single-domain SSL to protect all domains/sub-domains in use. - 5
Solution 5: For WordPress users
A very popular issue is forgetting to purchase an SSL certificate. WordPress owners enable secures HTTPS protocol for their website without installing or buying SSL, as result they get NET::ERR_CERT_COMMON_NAME_INVALID error message in the browser. There are two possible solutions in that case: - a purchase an SSL certificate and install it your web server;
- or changing HTTPS back to HTTP to enable your website without any protection and encryption of transmitted data.
- 6
Solution 6: Clear the SSL cache
The browser's SSL cache can be an issue. You have to try clearing the cache to resolve the error. - For IE/Edge. You have to open the Internet properties and find the "Content" tab, there will be a button to "Clear SSL state".
- For Chrome browser the process is similar, click "Three dots" button on the top right side of the browser, find the "Settings". There you will find "Advanced settings" at the bottom of a page. Now find "Open Proxy Settings" and there you will see the "Content" tab with "Clear SSL state"
- 7
Solution 7: Proxy settings
You may have limited browsing experience if Automatical detection of settings is not set via proxy setup. The solution is a Right-click on the Network Access icon to see Internet Properties. Tap on the "Connection" tab and then to "LAN Settings".
You will see a new window where you have to click to checkbox near the "Automatically detect settings" if it is not checked already. Once done, you can retry opening the website to see if error was solved.
- 8
Solution 8: Update OS and Browser
The classical idea is to make sure your OS and Browser is Up to Date as old or outdated software may bring unexpected issues. The developers are working hard to create new patches and bug fixes, so that is critical to have an updated system. - 9
Solution 9: Checking your Firewall/Antivirus We suggest checking Firewall and Antivirus settings and LOG files to be sure they are not blocking the website you are trying to visit. Review the blocking reason carefully, if you found a block, as probably they are trying to secure you from a malicious website. We do not suggest switching off Antivirus. Net :: Err_cert_common_name_invalid là lỗi gì?Ví dụ, lỗi NET::ERR_CERT_COMMON_NAME_INVALID thường là do tên trong chứng chỉ không khớp với đường dẫn đã nhập. Một lý do thường gặp khác là vì bạn truy cập từ mạng internet công cộng tại sân bay hoặc thư viện. Mạng Wi-Fi công cộng có nguy cơ cao bị tấn công xen giữa từ những người cùng truy cập. Kết nối của bạn không phải là kết nối riêng tư là gì?
Lỗi "kết nối của bạn không phải là kết nối riêng tư" này còn gọi là lỗi SSL (Secure Sockets Layer), trong đó SSL là các chứng chỉ của trang web. Chứng chỉ này đại diện cho độ an toàn của trang web đó, nên nếu chứng chỉ của web đã lỗi thời thì trình duyệt web sẽ không cho người dùng truy cập.
|
