I ended up switching the CDN from Edgio Premium to Microsoft Classic CDN and that resolved this.
I get ERR_CERT_COMMON_NAME_INVALID error on Edgio Premium CDN custom domain pointed to storage account website
I have a website hosted on a storage account. I have a Azure CDN endpoint pointed to this storage account. I have a custom domain name on this endpoint with a managed HTTPS cert. The cert has finished config. I am using Edgio Premium as the CDN.
When I go to access the website via https, I get an error stating the "The certificate for this site is not valid.". If I use firefox, I get "Websites prove their identity via certificates. Firefox does not trust this site because it uses a certificate that is not valid for www.somewebsite.org. The certificate is only valid for the following names: *.vo.msecnd.net, *.cmsresources.windowsphone-int.com, *.ads2.msads.net, *.aspnetcdn.com, *.cmsresources.windowsphone.com, *.microsoft-sbs-domains.com, ......
Ive doublechecked dns, the settings for the endpoint, created dummy storage account and repointed, purged CDN,
I can access via the endpoint URL via HTTPS and also via the storage account url via HTTPS with no issue.
Its just when I access via the custom domain name via HTTPS.
I have another CDN endpoint similarly configured and it has no issues.
2 answers
Sort by: Most helpful
-
-
GitaraniSharma-MSFT 49,586 Reputation points Microsoft Employee
2024-01-18T09:43:21.19+00:00 Hello @Wayne Massey ,
I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others", I'll repost your solution in case you'd like to "Accept" the answer.
Issue:
You were getting "ERR_CERT_COMMON_NAME_INVALID" error on Edgio Premium CDN custom domain pointed to storage account website, when accessing it via HTTPS.
Solution:
Switching the CDN from Edgio Premium to Microsoft Classic CDN resolved this issue.
If you have any other questions or are still running into more issues, please let me know.
Thank you again for your time and patience throughout this issue.
Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.