Slicer Certificate
The Uplynk Slicer family of applications runs on select Linux, MacOS, and Windows hosts in customer-managed deployments. The Slicer applications are required to perform certain communications tasks with the Uplynk Cloud infrastructure, such as logging in and reporting status.
Since the slicer's very early days, we have bundled Root Certificate Authority Certificates with the application to manage our TLS/SSL trust chain. In the June 2023 release, we upgraded the bundled Root CA Certificates to align with our cloud hosting platform requirements.
The Uplynk Cloud infrastructure provides TLS certificate security based on a certificate signed by a trusted Root CA. Slicer versions released prior to June 2023 do not contain the updated Root CA certificate required for validating future TLS certificates. As a result, these versions must be updated to maintain connectivity and functionality.
Starting August 1, 2025, the cloud management system will only support slicers released in June 2023 or later. Slicers older than this date will log an error message stating that they do not meet the system’s minimum requirements, and content will not be processed. To resume content processing, the slicer must be updated. This change does not impact VoD or linear content already processed and stored in the library using older versions.
Customers with Recent Activity:
Even if your slicers are inactive, we recommend reviewing your live and VoD slicer versions and upgrading any version dated before June 2023. Please ensure any inactive workflows are prepared to go live when needed. You will also see a CMS news item confirming this message.
If you need to upgrade your slicers, we strongly recommend using the most recent slicer version. We also advise testing in a staging environment to ensure workflow compatibility.
Customers without Recent Activity:
Even if your slicers are inactive, we recommend reviewing your live and VoD slicer versions and upgrading any version dated before June 2023. Please ensure any inactive workflows are prepared to go live when needed. You will also see a CMS news item confirming this message.
We strongly recommend using the most recent slicer version if you need to upgrade your slicers. We also advise testing in a staging environment to ensure workflow compatibility.
Important exception:
If you are running Python 2.0 plugins (used for SCTE ad marker detection), do not upgrade beyond version 23062600. Slicers released after that version only support Python 3.0 or later. While not required, we recommend rewriting any Python 2.0 plugins in a current version of Python and using them on the latest supported Slicer version.
We value your business and apologize for any inconvenience this may cause. If you have questions, please get in touch with your account team or our support team.