LiveKit Ingress
LiveKit Ingress is an ingestion service for self-hosted LiveKit deployments that accepts RTMP (Real-Time Messaging Protocol) and WHIP (WebRTC-Initiated HTTP)…
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
35/100 Low
- Maintained
- 0GitHub repository is archived
- Popular
- 46194 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
- Security check
- 100no serious findings, CI, tests
Based on 4 of 5 factors.
Availability: platform listings confirmed today
- GitHub stars
- 194
- Open issues
- 21
- Last commit
- 2026-11-09
- Latest release
- v1.6.0
- License
- Apache-2.0
- Activity
- rising
Checked 12 days ago - source: GitHub (livekit/ingress)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Fill in required LiveKit settings Set api_key, api_secret, ws_url, and redis (a running Redis service) before starting Ingress. These connect it to LiveKit and keep session state, so missing values will break startup or streams. source
- Open the RTMP port you configure If you'll use RTMP, open the TCP port (the network port) configured for RTMP in your firewall. If it's blocked, RTMP streamers won't be able to connect. source
- Open WHIPPort if using WHIP If you'll use WHIP (WebRTC stream input), open WHIPPort (the network port it listens on). If it's blocked, browsers or other WebRTC clients can't push streams. source
- Ingress usage Send RTMP or WHIP streams to the configured ingress endpoint. source
Fetched 2 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Why might a Helm chart not fully solve an ingress deployment?
Helm may only solve part of the problem. Ingress setups can still be an issue even when using Helm.
What should I check when an Ingress request returns a 404?
Verify the Ingress controller is installed and configured correctly. Also review routing and controller configuration.
What DNS or TLS issues can cause Ingress to stop working?
DNS misconfiguration and TLS misconfiguration are common causes of broken Ingress routing.
What troubleshooting help is available for Ingress sign-in problems?
The Ingress help center includes troubleshooting for sign-in issues. It also provides a way to file a bug report for technical problems.
Answers sourced from oneuptime.com, support.ingress.com, www.kubekanvas.io, www.reddit.com
Community
- Basic ingress routing example for proxmox : r/selfhosted - Reddit (reddit)
- Mixing Self-Hosted/Cloud-Hosted: Thoughts on cost ... - Reddit (reddit)
- r/selfhosted on Reddit: I need a Wireguard VPN with multiple ingress ... (reddit)
- Kubernetes: how do you expose your services? : r/selfhosted - Reddit (reddit)
Collected 29 days ago - public community threads