Troubleshooting Ingress

LiveKit Ingress brings external media into LiveKit rooms through RTMP/RTMPS, WHIP, or URL-based HTTP(S) and SRT sources, publishing the incoming media as a room participant whose tracks can be subscribed to normally. RTMP and URL sources are transcoded for WebRTC, while WHIP generally passes media through unless transcoding is enabled. Common publishing failures stem from invalid, deleted, mismatched, or disabled ingress stream keys, while connection timeouts typically indicate firewall restrictions, often resolved by using RTMPS over port 443 instead of RTMP on port 1935. WHIP can experience separate WebRTC media connection failures due to blocked UDP, unavailable TCP fallback on port 7881, or IPv6 network-path issues, and unsupported codecs can cause tracks to be omitted without an explicit error. The guide also recommends checking regional routing when latency is high, creating rooms in advance when room attributes must be controlled, deleting ingresses before rooms, reusing long-lived RTMP and WHIP endpoints to avoid quota limits, and carefully managing URL inputs and transcoding duration to prevent unnecessary costs.

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.