Wildcard certificate, no sub domain, common name invalid

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:*.arcofusion.com

I ran this command:
sudo env AWS_ACCESS_KEY_ID=accesskey
certbot certonly --dns-route53 -d *.domain.com --agree-tos --non-interactive --email you.name@domain.com

It produced this output:a valid certificate and key

My web server is (include version):wildlfy 17

The operating system my web server runs on is (include version):AWS Linux 2

My hosting provider, if applicable, is:AWS

I can login to a root shell on my machine (yes or no, or I don't know):yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):no

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):1.11.0

I generated the certificate, with a wildcard, but when someone uses the site without a sub domain name, they get the error: ERR_CERT_COMMON_NAME_INVALID
This would indicate to me that no subdomain is not covered by the wildcard certificate.
I have certificates from other providers where the wildcard certificate includes no sub domain. Is there something I need to include to include no sub domain in my willdcard cert?

Hi @charlescivi,

Wildcard like *.arcofusion.com only cover subdomains like a.arcofusion.com, b.arcofusion.com etc. but doesn’t cover neither a.b.arcofusion.com nor the base domain arcofusion.com. So if you want to cover the base domain then you need to add it to the certbot command -d *.arcofusion.com -d arcofusion.com.



This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.