We have setup a custom subdomain for a third party app following their instructions using CNAME (dns only) and TXT record. DNS records are fine and verified from both sides. HTTP is working, but there is a problem with SSL so HTTPS is not working. Chrome is showing “NET::ERR_CERT_COMMON_NAME_INVALID” error. There is a certificate, but it is deemed invalid.
I have created similar subdomains before, for gsuite for example, and it is working without problem, cname is even proxied, and there were no problems with ssl certificate.
What could be the problem now?
- Cloudflare did send an email notification observing issuance of the certificate for subdomain.
- ssl setting is set to Full (Encrypts end-to-end, using a self signed certificate on the server)
- dns cname is “dns only”
- dns records are fine as in setup properly (cname, txt)
- http working, https not, ssl issued from third party, but it is invalid according to chrome