Disabling CDN legacy mode support in front of the Update Center (downloads.cloudbees.com)

1 minute readKnowledge base

Context

At CloudBees, we are constantly working to improve our security protocols, and therefore, we regularly update our internal infrastructure to remain compliant with the latest security standards. Our latest update will allow us to provide support for SNI (Server Name Indication), nevertheless, in exchange we will lose support for the Legacy Mode in front of our Update Center (downloads.cloudbees.com). In August 2023 the Legacy Mode will reach its EOL, and thus, it will deny access to the Update Center for some specific environments indicated below. If you are not under such circumstances, everything will continue working without taking any action.

Affected environments

  • The only affected environments will be the ones whose CloudBees CI release is lower than 2.332.1.4, using Custom Update Centers and running the cloudbees-update-center plugin older than 4.67.

Resolution

You should upgrade as soon as possible. To do so, we recommend you to raise an Assisted Upgrade Support Ticket so we can help and guide you through the complete upgrade process.

Workaround

If you can’t upgrade at the moment and you have an affected environment, you can still update plugins in your Custom Update Center by uploading the plugins manually.

Since your Custom Update Center won’t be able to reach the default CloudBees Update Center (downloads.cloudbees.com), it won’t be able to download/update plugins, however there is a section called Upload plugin in the Custom Update Center that allows the administrator to manually upload a previously download hpi file.