Troubleshooting and FAQ

What is included?

xOTT combines source adapters, live/event operation, VOD and recordings, worker processing, subscriber packages/access lines, a native player/API and optional XUI integration. Capabilities and licenses vary by feature, provider and deployment. Included adapters are not a guarantee that upstream services never change.

Which password and FFmpeg do I use?

Use the admin password generated by the installer, not admin/admin. The installer keeps an installed FFmpeg where possible or installs the distribution package; it does not force every old Ubuntu installation onto the newest upstream FFmpeg. Verify available codecs/features before commissioning headend processing.

Licenses and trials

Check the exact expiry shown on the panel/account website rather than assuming a calendar-day boundary. Main-panel and worker licenses have distinct roles. Use the account website for current plans and renewal; ask support before hardware replacement or transfer. Do not post license keys publicly.

How many streams can this server run?

There is no honest universal number. Input/output bitrates, source count, transcoding/audio processing, disk, worker placement, provider limits, proxy throughput and network quality matter. Start small and measure sustained workload. More CPU does not fix packet loss or a saturated proxy.

Why are some qualities or languages absent?

The source, selected tracks, output container and player must all support them. Resolution caps do not transcode. UDP/HTTP TS do not expose a player-style adaptive video menu. Live multi-quality uses compatible source renditions; downloaded VOD file playback is a different delivery path.

Why can a subscriber see fewer channels?

Check saved versus unsaved members, collection health, actual package version, output rights, line expiry and any denials. VOD must be published with a playable asset. Events need the correct native-event or slot grants. See the missing-channel checklist.

Browser works, xOTT does not—what next?

Compare the actual account, region, proxy assignment, processing node and requested source. A browser’s network path can differ from the worker’s. Authentication, manifest, DRM licensing and media acquisition are different stages. Read the precise failed stage before relogging or deleting anything.

The interface is slow

Check the browser network timing, API response time, server resources and database/disk pressure. Compare domain/reverse-proxy routing with direct reachability where safe. Catalogue refreshes and large imports can take longer than cached table reads; do not refresh all providers repeatedly to repair an unrelated slow page.

Prepare a useful support report

• Installed main/worker versions and Ubuntu version.
• Affected stream/event identity and actual processing host.
• Exact action, time/time zone, error and request reference.
• Whether input probing, output playback or only a particular client fails.
• Redacted relevant logs and steps to reproduce.
• Never include passwords, proxy credentials, bearer tokens, DRM material or live subscriber URLs in a public report.

Contact support@xottpanel.com or @xsharer on Telegram.