I have 2 dedicated servers with the last version from cyber panel and I notice now when I install a new domain/website and issue a certificate for this domain all other domains the SSL fails with the warning the certificate origins from the last installed domain.
Domains already working with letsencrypt certificate:
Now when I install domainC the certificates from domainA.com and domainB.com becomes invalid claiming the certificate is from domainC
The problem exists since the last update and affects both servers.
Thank you for the tutorial, however, it still doesn’t work. It loads the Certificate correctly on Desktop Browsers but not in Android chrome where it still claims the certificate comes from another domain.
It also shows the correct certificate in SSL Checker → SSL Checker
I have certain urgency to fix this problem since it affects 2 servers and several domains.
So I would like to ask if some expert here would be so kind and fix this problem for me and I pay him for the service.
Ok there is definitive some bug I follow all instructions all domain certificates become invalid NET::ERR_CERT_COMMON_NAME_INVALID
And it seems there are more people who have the same problem.
When i remove the certificates and issue a new one in the cyber panel it shows success and it is on 89 days. SSL checker shows also everything correct but on mobile phones when disabling wireless and getting the internet from a handy provider the error NET::ERR_CERT_COMMON_NAME_INVALID comes up, and not only for me I have a lot of claims from clients who can’t access the websites with the same error.
Try it by yourself open in wlan www.saudenatural.info and than turn off wireless and connect to your mobile internet provider and reload or reopen www.saudenatural.info.
Of course, I delete all cookies all website data cleared the app cache etc. i am not behind a VPN or proxy
Kindly share which instructions you followed that led to the domain certificate becoming invalid so that i can report them to be removed.
Error NET::ERR_CERT_COMMON_NAME_INVALID can be cause by various issues and most of the time its usually either SSL is configured incorrectly or client issues such as VPN, browser addons, cookies etc.
CyberPanel from experience with latest update it issues SSL certificates perfectly but there maybe conflicts or bugs around reissuing it seldoms works as expected.
Your argument is counter intuitive. To check if SSL is correctly installed a proper host/sysadmin should not rely on client experiences but professional tools that verify the SSL certificate on their web servers is installed correctly without errors. For example examining www.saudenatural.info:
With these deductions you can now check server errors for SSL configuration issues. As far as that tool is concerned your ssl is setup correctly. You can always confirm this be clicking on padlcok icon on the address bar when visiting said domain and confirm if certificate is valid. A certificate cannot be valid and cause Error NET::ERR_CERT_COMMON_NAME_INVALID there must be other underlyting factors on the client side.
I installed on both servers a new website and issue with the cyberpanel a certificate for the new website / domain. From this moment all other domains have a certificate error claiming Error NET::ERR_CERT_COMMON_NAME_INVALID
When i clicked the padlock and looked at the certificate details i can see it takes the common name from last installed domain / website certificate and not his own certificate.
I installed / moved now 2 websites to an other server (not litespeed) and it worked fine.
Look i am willing to pay to fix the issue because i literally tried everything to get this back working.
When I remove a website that previously show the NET::ERR_CERT_COMMON_NAME_INVALID when issuing a new certificate with the steps above and then reinstall the website the SSL gets also issued successfully and stays valid when I repeat the step with other websites.
However, this would be an enormous work backup emails websites databases then delete the website and reinstall everything again.