Unable to create specific CDN custom domain: Exception of type 'Microsoft.Azure.Cdn.Common.ProviderPluginContracts.ProviderException' was thrown.

Thierry 0

Been trying for some time now to add another custom domain to our server. Normally this goes without any issues, however I now run into one where the CDN custom domain doesn't work. I have already recreated the CNAME in azure once thinking I might have made a typo, but without any luck.

When I go to the endpoint and add a custom domain I add the custom hostname and it gives me an ok. It starts working and after a while I get the message:
Exception of type 'Microsoft.Azure.Cdn.Common.ProviderPluginContracts.ProviderException' was thrown.

If I use nslookup on this domain I get the same information as I get on one of the already existing ones. What can I do or try?

Ki-lianK-7341 345 Reputation points

2024-11-19T09:57:52.6966667+00:00
Verify CNAME: Ensure the CNAME record points to your CDN endpoint.

Check DNS Propagation: Use nslookup to confirm the CNAME is resolving correctly.

Review Certificates: Ensure any custom HTTPS certificates meet Azure’s requirements.

Retry: Delete and re-add the custom domain in the Azure portal.

Check Azure Status: Look for any ongoing service issues on the Azure status page.
Thierry 0 Reputation points

2024-11-19T10:22:24.6266667+00:00
The CNAME points to the correct CDN endpoint

NSlookup gives me the same information on this CNAME as it does on a working one

Certificates are still correct

Tried removing and re-adding the domain CNAME

Azure status gives no issues at this moment
KapilAnanth-MSFT 47,206 Reputation points Microsoft Employee

2024-11-19T11:38:56.04+00:00
@Thierry ,

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

I understand that you are unable to add custom domain to an CDN.

I assume you are using a Microsoft CDN, and not from Edgio

Please let me know if this is incorrect

You mentioned, "I add the custom hostname and it gives me an ok. It starts working and after a while I get the message:"

Can you elaborate where exactly are you getting the error message from?

Are you using "cdnverify" subdomain? or regular domain.

Cheers,

Kapil.
Thierry 0 Reputation points

2024-11-19T12:27:05.4466667+00:00

@KapilAnanth-MSFT we use Azure CDN Standard from Microsoft (classic).

This is what I meant with it gives me an ok:

Then after a while I see the error appear in the Notifications.

If I look at the recordsets I see a cdnverify. CNAME for the domain I have been trying to add. The old ones don't have these.
KapilAnanth-MSFT 47,206 Reputation points Microsoft Employee

2024-11-19T12:35:49.2+00:00
@Thierry ,

I see this is not recommended

Can you please remove it, and use a regular domain like www.contoso.com or cdn.contoso.com and let me know.

If the above does not help, please share a screenshot of error message from notifications.

Cheers,

Kapil
Thierry 0 Reputation points

2024-11-19T14:14:41.71+00:00

@KapilAnanth-MSFT Sorry, think I wasn't clear. I meant that I haven't seen the cdnverify names before. But I use the cdn.contoso.com variant. This is what I get from the notifications.
KapilAnanth-MSFT 47,206 Reputation points Microsoft Employee

2024-11-20T04:28:53.8066667+00:00
@Thierry , Thanks for the info.

Are you sure the error pops up randomly and not when you try to enable HTTPS on this custom domain?

Because, I can see similar issues

https://learn.microsoft.com/en-us/answers/questions/1386611/exception-of-type-microsoft-azure-cdn-common-provi

https://learn.microsoft.com/en-us/answers/questions/788838/exception-of-type-microsoft-azure-cdn-common-provi

Both mentioning the same error and the issue being ,

The TLS certificate created is not a complete certificate chain with leaf and intermediate certificates.

The root CA is not a part of the Microsoft Trusted CA List.

These requirements are documented here.

Please confirm if you are trying to enable HTTPS on this custom domain or not?

Cheers,

Kapil
Thierry 0 Reputation points

2024-11-20T14:36:31.28+00:00

@KapilAnanth-MSFT Normally we would add the custom domain by adding the Endpoint Hostname and Custom Hostname, as shown in the screenshot you send earlier. Then once it is created we need to activate the custom domain https, but we never get to this step. Googling brought me a lot of items about certificates as well, but we never get to making https available.

The endpoint has 22 domains underneath it currently, so we should still have room as well (limit is 25?)
KapilAnanth-MSFT 47,206 Reputation points Microsoft Employee

2024-11-22T07:06:52.6933333+00:00
@Thierry , You are correct.

Since you mentioned "This is what I meant with it gives me an ok:"

I thought that at first the custom domain got added

Then when you were trying to enable custom domain's HTTPS, you were facing the error.

Custom domains per endpoint is 25, see Content Delivery Network limits.

To troubleshoot further, we will need a specialized 1:1 session, where a support engineer can check the backend logs to pinpoint the issue. If you have a support plan you may file a support ticket, else please do let us know, we will try and help you get a one-time free technical support.

P.S : We will be able to provide you one-time support if and only if your subscription is not managed by a CSP

Cheers,

Kapil

Share via

Unable to create specific CDN custom domain: Exception of type 'Microsoft.Azure.Cdn.Common.ProviderPluginContracts.ProviderException' was thrown.

Your answer