The Subject Alternative Name field in the certificate must list both. Maybe the CSR wasn't properly created to include them?
This is an image from a GoDaddy cert just like the one you got:
Check to see if both entries are there
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I purchased a single-domain SSL from GoDaddy. It was confirmed to me via their support that this certificate covers both the bare domain, AND the www. subdomain.
When I attempt to add the "www.domain.com" Custom Domain in my Azure Container App, it shows "No certificates match the selected hostname". I am able to add the naked domain without any issues.
The Subject Alternative Name field in the certificate must list both. Maybe the CSR wasn't properly created to include them?
This is an image from a GoDaddy cert just like the one you got:
Check to see if both entries are there
Was basing my experience from the app service where this cert is used.
Tested with a container app on my sandbox and got the same result.
A wildcard cert does the job, a single domain one seems as it is broken for now.
This issue was reported in Github a few days back and marked as a bug in the last hours:
https://github.com/microsoft/azure-container-apps/issues/292