I had today the issue, that a Website had problems with the SSL Certificate and the www. subdomain.
I had all the settings from your side, but it seemed that for www.example .com used the example .com certificate.
But in my honest opinion, why does the cleavr script not include the www. version in the request if you already take care of the www. redirection.
I had to install and run certbot myself to get it working.
I presume that the DNS Settings have an issue.
What it is:
example .com A 192.168.1.1
www. example .com A 192.168.1.1
What it should be in my eyes
example.com A 192.168.1.1
www.example .com CNAME @
Somehow, some browsers redirected from www.example .com automatically to example .com, but some browsers didn’t and pushed the error. So regarding that the IT of the client (DNS Manager) tells me it’s on our end, but where we put a CNAME in the dns ourselfs it worked fine, i’m a bit lost
My 2 Requests/questions:
- What is the issue exactly?
- Could the www. also be included in the ssl generation? Or that we can add multiple domains to it?