O365 CDN Invalid nonce key configuration

[palcheuski]

Category

• Question
• Typo
• Bug
• Additional article idea

Expected or Desired Behavior

SPFx webpart/extension solution package JavaScript scripts loaded successfully on SharePoint modern page from Office 365 CDN default origin (*/CLIENTSIDEASSETS) enabled on a tenant.

Below is a sample from working tenant

Observed Behavior

SPFx webpart solution package is successfully deployed to AppCatalog and all resources appear in the ClientSideAssets library. Finally, SPFx solution is successfully installed on the target site collection. After adding webpart on the canvas we see the following results. Here on the screenshot you can see that SharePoint tries to access resources from CDN, but it results to 406 error code.

Below is a sample from NOT working tenant

Some inspection in Fiddler, here we can see an error message that is not very clear what exactly wrong.

Steps to Reproduce

1. Enable O365 CDN using PowerShell Cmdlet, so that we have the final settings as bellow
   

2. Deploy SPFx solution package to the AppCatalog, here is what I have in my tenant
   

When deployment completed, i could see that resources are added to the ClientSideAssets library. Here is the proof.

3. Create a team site (classic or modern, it doesn't matter).
4. Install SPFx solution from the AppCatalog to the target site collection.

When it is added to the site, there is no errors in the App Details page. here is a screenshot

5. Add custom webpart from the SPFx solution to the modern page, open DevTools in the Chrome and switch to the network tab, from here you can see a lot requests with 406 errors when trying to access resources from the public cdn.

[michelsmit]

Have the same exact error message on my tenant. No solution yet.

{"HttpStatus":"NotAcceptable","ErrorMessage":"Invalid nonce key configuration","ErrorCode":406001}

[patmill]

Just being super clear - the configuration is for a public CDN, correct? My understanding was that the nonce for a request to a CDN was only for private configurations. Is it possible that the configuration was changed in some form? If you request private configurations, what comes back?

[palcheuski]

@patmill , yes, that is the configuration for the public CDN, we don't yet have a private CDN configured. As shown in my screenshots, all requests to the CDN start with the base path https://publiccdn.sharepointonline.com///<resource_relative_path>. It seems to me, that there are some problems with the propagation to the public CDN.

[palcheuski]

@VesaJuvonen , maybe there is some news on this issue?

[luis-ribeiro]

Are you using a O365 developer account? I had the same issue (the error output was the same) when using a O365 developer account tenant.
I have repeated the same steps on a fresh regular trial tenant and everything worked as expected.

[michelsmit]

For me no developer account (production tenant), public cdn. The issue is only with this particular tenant, not other tenants I manage. I created a ticket with MS support.

[waldekmastykarz]

I'm experiencing the same issue in my non-dev tenant:

• Public CDN enabled with default origins
• Assets provisioned from the solution package to ClientSideAssets and accessible via the doc lib URL
• Accessing the same assets via the Public CDN URL results in a 406 and prevents the web part from loading

[LeemansBE]

Any update on this? We are experiencing the same issue in our newly created tenant.

• Files are accissible through the style library
• Accessing the same files through the public CDN results in 406: "Invalid nonce key configuration"

[jeslas]

Same issue on newly created dev tenant

[palcheuski]

I lost hope for an answer, issue is still actual for me.

[patmill]

We are working with the owning team on this issue. If you can open a support ticket, that would help as well.