Skip to content

Desktop GUI Settings

IPTVBoss Pro

XC Server requires Pro.

Open Settings → Server Settings in the desktop IPTVBoss application. These settings connect the desktop installation to the XC Server and control its server, network, output, security, and synchronization behavior.

Desktop XC API Settings

Desktop XC API Settings: output and security

Bootstrap an empty XC Server with GUI pairing

An IPTVBoss Pro desktop installation can initialize a new XC Server using the database currently open in the GUI:

  1. Open https://boss.domain.com/boss.php on the new server.
  2. Copy the server URL and one-time pairing code shown under Link from IPTVBoss.
  3. In the desktop application, open Settings → Server Settings.
  4. Enter the server URL and pairing code, then select Link XC Server.
  5. Confirm that the current GUI database should become the authoritative server database.
  6. Wait for the upload and server bootstrap to finish, then verify the connection and backup status.

The pairing code expires and can be used only once. Confirm that the intended database is open and backed up before linking because it becomes the initial authoritative database for the server. A non-Pro installation can pair only after bootstrap has been completed.

XC Cloud Database

When upgrading from before 3.12.22, update both desktop and server before resuming database sync. To move database synchronization to Dropbox or Google Drive, follow the provider-switch procedure.

  1. Enter the Server URL and Server Port.
  2. Enable Include Port in URL when required by the public address.
  3. Review the displayed connection address.
  4. Link the installation before enabling cloud database synchronization.

HTTP and HTTPS server URLs are accepted. IPTVBoss displays a warning when the configured endpoint uses unencrypted HTTP; use HTTPS for connections that cross an untrusted network or the public Internet. Other URL schemes are not supported.

After pairing, actions such as Refresh Cloud Status, Disable Sync, Retry Current Database, and Unlink This Installation apply immediately. Unlink This Installation removes the local pairing even when the server cannot be reached; if revocation cannot be sent, the old server-side pairing may remain until the server is reachable again.

Shutdown publication and next startup

When XC Server is the database synchronization provider and synchronization and database backups are enabled, closing the desktop creates and publishes a backup. Progress shows Creating backup, Uploading backup, Waiting for XC Server, and Closing application as the work proceeds. The closing desktop does not restore the published database; the next startup restores the server database before editing resumes.

If shutdown cannot finish, Shutdown needs attention shows the failure and the local backup path when available. Choose Retry, or Exit with Local Backup to close while retaining a verified local backup. The latter is available only when that backup exists and does not confirm that the server received the changes.

If the previous publication or restore still needs to be resolved at startup, XC database reconciliation required pauses editing and automatic source synchronization. Choose Retry Connection to resolve the publication and restore the server database, Exit to leave, or Unlink Server to continue with the local copy. Unlinking first saves a safety backup and disables database synchronization. The local copy may lack server-side changes; unlinking abandons automatic reconciliation and does not restore or modify the server database.

See XC shutdown or startup needs attention for recovery steps.

Automatic server reloads from this client

Pairing does more than connect the desktop installation to the XC Server database. The server also provisions a client-specific, reload-only credential. IPTVBoss stores and uses this credential automatically; it does not grant general Server Console or administration access.

When the desktop client closes after producing a database backup, the database provider determines how the paired XC Server receives the update:

  • If database cloud synchronization is disabled, the server reloads its local database.
  • If Dropbox or Google Drive database synchronization is enabled and the cloud backup succeeds, the client asks the server to reload from the synchronized cloud database after a short delay.
  • If XC Server is the database synchronization provider, the server applies the uploaded backup through its publication workflow; the client does not send a separate reload request.
  • If an enabled cloud backup fails or is incomplete, the client does not request a reload. This prevents the server from loading an incomplete update.

The client must be paired, XC must be enabled in its saved configuration, and the server address must be reachable. This is not a live reload after every edit; it occurs as part of the client's shutdown and backup workflow. If the server is offline, busy, or blocked by another database operation, review the client and server logs before trying again. See Paired Devices for access management and Server did not reload after a client update for troubleshooting.

Server and Network

Use Enable XC Server when this installation should provide the XC Server service. Use Block direct connections (bind to 127.0.0.1) when a native server should accept connections only from the same host, such as through a reverse proxy running on that host. Remote devices can still connect through that proxy. Clear it for direct LAN connections. Command-line and environment bind-address overrides take precedence; see Update from 3.11.16.

Enabling the XC Server does not require any layout to be enabled for XC output. The server can be used solely to deliver M3U playlists. Enable XC Enabled on a layout only when that particular layout should participate in XC Server output.

  • Output and Links controls M3U downloads, cloud-provider links, and TinyURL links. Enable only the link types required by the deployment.
  • Security controls the administrator password and which console areas require administrator protection.
  • Operations and Sync Runs contains the update interval, testing-server controls, and Manage Sync Runs. The update interval is measured in minutes and controls automatic backup checks, not software update checks or source sync schedules. Set it to 0 to disable automatic backup checks. Negative saved values reset to 30 minutes.

Warning

Never publish an administrator password, API key, pairing code, or private server address.