Solution: The self-signed https certificate is not issued by a trusted ca organization and is not trusted by major browsers. It is easy to be forged and attacked by middlemen, so there will be risk warnings. It is suggested to replace the https certificate issued by the regular ca organization to eliminate this hidden danger.

2. Reason 2: A self-signed https certificate was used.

Solution: The self-signed https certificate is not issued by a trusted ca organization and is not trusted by major browsers. It is easy to be forged and attacked by middlemen, so there will be risk warnings. It is suggested to replace the https certificate issued by the regular ca organization to eliminate this hidden danger.

3. Reason 3: The domain name and web address contained in the certificate are inconsistent.

Solution: The domain name corresponding to each htps certificate is unique. When the domain name contained in the certificate issued by the website is inconsistent with the domain name of the website, the system will automatically issue a report, prompting that the certificate domain name does not match. This requires re-applying for an https certificate. If there are multiple domain names to be protected, it is recommended to apply for a multi-domain SSL certificate or a wildcard certificate.