Skip to content

XC Server Troubleshooting

For interrupted background syncs, cancellation timeouts, or a NoGUI status that needs attention, see NoGUI status and cancellation.

IPTVBoss Pro

XC Server requires Pro.

Series playback from linked groups

For Series playback from a layout containing linked series groups, XC Server can resolve the upstream provider even when no provider was previously remembered. It follows the enabled linked groups and uses the provider when exactly one XC source is available. Playback is still rejected when no provider or multiple providers can be identified; confirm that the user has an enabled credential for the resolved source.

See Linked Layout Groups to check the originating layout and group.

Server did not reload after a client update

PRO This troubleshooting workflow applies to XC Server.

The automatic reload request is sent when a paired IPTVBoss client closes after completing its database backup workflow. It is not sent after every edit.

Check the following:

  1. Confirm the desktop installation still appears under the XC Server's Paired Devices.
  2. Confirm XC is enabled in the client's saved Server Settings and that the configured server address is reachable from that computer.
  3. If database cloud synchronization is enabled, confirm the shutdown cloud backup completed successfully. IPTVBoss intentionally skips the reload request after a failed or incomplete cloud backup.
  4. Check whether the server was already updating, processing an administration or restore operation, or blocked by a database synchronization lock.
  5. Review the client log for the reload notification and HTTP response, then review the XC Server logs for the queued or rejected request.
  6. If the client was revoked, generate a new one-time pairing code and pair it again. Do not reuse an expired pairing code or manually share a reload credential.

See Automatic server reloads from this client for the expected behavior.

XC output is rebuilding or serves an older response

XC Server now prepares and publishes complete response variants, then keeps the previous valid generation available while a replacement is built. A request can temporarily use direct database generation when its cached variant is unavailable or when the database is changing.

Do not delete XC cache files while the server is running. Check the client and XC Server logs for database-transition, cache-build, direct-fallback, or out-of-memory messages. If the problem continues, restart the XC Server after creating a database backup and include the sanitized logs with the application version when requesting support.