Updating IPTVBoss¶
Update IPTVBoss while protecting the database, settings, layouts, and source configuration already on the computer.
Startup update check
Packaged desktop installations check for a newer release before loading application data. The prompt shows the installed and available versions. A failed or timed-out update check allows normal startup to continue.
For a server, use the platform-specific backup and update procedures.
Upgrading to 3.12.22 or later¶
When upgrading from an earlier release, update both the desktop and XC Server before resuming XC database synchronization. Version 3.12.22 introduces persistent XC stream IDs and cloud-sync protocol 2.0; incompatible peers are rejected with an instruction to update both installations.
Startup creates and retains a verified local backup before the first stream-ID migration. Allow the migration to finish. Existing positive XC IDs up to 2,147,483,647 are preserved; oversized IDs are replaced with IDs within that range. If a player could not load the oversized IDs, refresh its playlist once after updating.
Old oversized IDs remain playback and metadata aliases while the original layout channel exists and the user has access. Removed IDs are reserved rather than assigned to replacement content. Playlist positions, EPG IDs, and provider episode IDs are unchanged. Cached XC responses from the old ID format are rebuilt automatically.
The ID registry travels with database backups and XC synchronization. Restoring a historical backup restores that snapshot's identities; independently edited databases are not merged.
Update from 3.11.16¶
Read Update from 3.11.16 before upgrading an existing installation. It covers the new XC Server administrator username (admin with your existing password) and the settings for reverse proxy, direct LAN HTTP, and direct HTTPS connections.
Use the startup update prompt¶
When an update is available:
- Choose Update now when offered to hand installation to the native updater and restart before loading your data.
- Choose Later to continue using the installed version.
- If Open download page appears instead, download and install the update manually, then relaunch with your usual shortcut or command. This applies when the native updater is unavailable, including launches with command-line arguments or software rendering.
On Linux, update a Debian/Ubuntu package through your package manager. For a tarball installation, stop IPTVBoss and replace the installation using the download for the matching architecture and Ubuntu variant. Preserve the application data directory.
If local XC Server or sync work is active, or its status cannot be verified, the prompt reports Update available — installation deferred. Choose Continue to Boss or Exit, stop the local work safely, and reopen the desktop to update. IPTVBoss does not stop that work for you.
Update a community Docker GUI container¶
In 3.12.24 and later, a GUI container configured with IPTVBOSS_COMMUNITY_DOCKER=true offers Open Docker instructions and Later when a newer release is available. Open Docker instructions opens the community maintainer's update instructions; Later continues startup. If the browser cannot open, the prompt displays the address to open manually.
Update the Docker image and recreate the container using the maintainer's instructions, preserving the configured data volumes. Do not install a Debian package or replace application files inside the container. A newer IPTVBoss release may be available before the community image has been updated.
This prompt applies to community GUI containers that set the environment flag. For XC Server containers, follow the server backup and update procedures.
Recover an incomplete update¶
While an update is pending, new background launches are deferred. If startup reports Previous update has not completed, let any running installer finish. If the installer has failed and closed, choose The updater has closed — recover startup. Background jobs remain paused until the update succeeds or startup is recovered.
If the native updater cannot start, use the offered download page to install manually. See If the update fails if the installation itself fails.
Before updating¶
- Finish any source synchronization and output operation, or select Cancel for an in-progress source sync and wait for its progress view to close.
- Confirm that no second IPTVBoss process is using the database.
- Create or confirm a recent backup.
- Record the current IPTVBoss version and operating system.
- Download the new installer only from the official IPTVBoss download page. Use the GitHub Releases page when you need direct assets or release notes.
Warning
Do not remove the existing application data directory as part of a normal update. That directory contains configuration and database files.
Install the update¶
- Close IPTVBoss.
- Install the package for your operating system.
- Start IPTVBoss.
- Wait for the database migration or startup process to finish.
- Confirm that your layouts, sources, and settings are present.
Do not interrupt a database migration. If startup fails, stop and collect the logs before trying a reset or restore.
Confirm the update¶
Check the version shown by the application, then test a low-risk workflow:
- Open Sources Manager.
- Confirm that a source is present and review its health and last successful sync without synchronizing it yet.
- Open Layout Manager, confirm that your layouts are present, and review the selected layout’s health dashboard.
- Review Application Settings, including the Layout Manager attention checks when the release adds them.
- Generate a test output only after the database, source health, layout inventory, and settings look correct.
If the update fails¶
Do not delete the database. Save the logs, note the version you installed, then ask in the IPTVBoss Discord or open a support ticket through the member portal if the issue is account-specific or private.
Note
The release page and installer names may change as new IPTVBoss releases are published.