Upgrading Broadcaster from legacy versions
Broadcaster Upgrade Preparation Reference
Use this checklist before upgrading your Broadcaster from a legacy version.
Before You Begin
- Back up your configuration file. In the Broadcaster UI, go to Settings > Export and save the configuration before starting the upgrade.
- Confirm your license. Depending on your upgrade path, the license may need to be reloaded or reactivated after the upgrade completes.
- Whitelist the license server. Versions 16 to 18 use license2.zixi.com, and version 19 uses licensing.zixi.com. Allow outbound TCP 443 and 80 to the license server on your network before upgrading.
- Check the release notes. Release notes are on portal.zixi.com, where you can also sign up to be told when a new version is released.
Upgrade Paths by Platform
Recommended path: upgrade one major version at a time, installing the last release of each in turn: 16.13, then 17.9, then the last 18 release, then 19. This applies to Linux and Windows. Version 18 can go straight to 19. The table below applies the same approach to specific platforms.
Current Version | Target | Path |
|---|---|---|
v13/v14 | v16 | Upgrade through the last release of each major version: the last v15 release, then 16.13. This helps prevent potential issues during the jump. |
v15.3.44122+ (Linux x86) | v17 | Upgrade to 16.13 first, then to 17.9. |
Linux ARM | v17 | Upgrade to the last v16 release for ARM (v16.12.45243 or later) first, then to 17.9. |
AWS Graviton (ARM) | v17 | Requires Amazon Linux 2023. Amazon Linux 2 is not supported. |
Windows/Mac | All Versions | No in-place UI upgrade. Run the installer directly to upgrade. On Windows, the installer stops and restarts the Broadcaster service, and the host does not need a reboot. |
For full OS compatibility details, refer to the System Requirements document.
Network & Licensing Configuration
Before configuring v16.x Broadcasters, make sure your port settings and licensing URL match the current requirements:
After Upgrading: Migrating the Files Directory
The upgrade installer does not automatically move files between the old and new install directories. Deleting the old directory without migrating it first can break existing workflows.
Once upgraded to v16, before you delete the old v15 directory:
- Locate the files directory under the old install path, e.g.: zixi_broadcaster-centos7/files
- Move its contents into the corresponding directory in the new install path: zixi_broadcaster-linux64/files
- Confirm dependent workflows still function correctly.
- Only then delete the old v15 directory to reclaim disk space.