NuGet.org migration towards a new multi-CDN infrastructure

[jcjiang]

In the coming weeks, nuget.org will be migrating towards a new multi-CDN infrastructure that will improve the experience of our users. This change allows our team flexibility to switch to a back-up provider in the case that one CDN is down, which will broaden coverage for our users.

Some changes are coming for older TLS cipher suites, which may result in connectivity issues. From our data we believe this will affect only a small percentage of requests. We will be monitoring all feedback channels during the migration to assess impact and adjust our roll-out timeline as needed.

Below, we provide resources to determine whether you will be affected by this change. This utilizes the .NET CLI to install a package from our pre-production (INT) environment which tests connectivity:

mkdir cdn-test
cd cdn-test
dotnet new classlib
dotnet add package BaseTestPackage.NetStandard --source https://apiint.nugettest.org/v3/index.json

If you are experiencing connectivity issues while connecting to nuget.org or restoring packages from https://api.nuget.org/v3/index.json, such as:

"The SSL connection could not be established"

Please ensure that TLS 1.2 and any of the following cipher suites have been enabled on your machine:

TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256

If you have any questions, do reach out to us at support@nuget.org or by commenting on the discussion issue: NuGet/Home#11058

[zhhyu]

The list of cipher suites has been updated and aligned, and this issue is not a concern anymore. The official document will be published very soon.

Closed this issue.