Troubleshooting Egress
Blog post from LiveKit
LiveKit Egress troubleshooting covers the recording lifecycle, common status codes, storage uploads, content behavior, layouts, webhooks, and self-hosted deployment issues across both the current StartEgress API and deprecated source-specific APIs. Egress joins a room as a dedicated participant and should be monitored through webhooks, EgressInfo fields, and the LiveKit dashboard, with successful sessions ending as EGRESS_COMPLETE. Frequent failures include missing template start signals, inaccessible or faulty custom templates, unpublished participants or tracks, expired cloud-storage credentials, output-finalization problems, timeouts, duration caps, account usage limits, unsupported codecs, and unavailable AWS AssumeRole access. The guidance recommends testing templates locally, starting recordings only after required tracks publish, using durable credentials and unique output paths, and accounting for differences between raw recorded tracks and processed audio heard by agents. It also explains that default layouts show only video publishers, custom templates are required for dynamic layouts and overlays, webhook handlers must tolerate duplicate or missing events, republished tracks may require a new Egress, and self-hosted installations should share Redis connectivity with LiveKit, use current Egress versions, and enable Chrome logging when debugging templates.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.