# 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) streams from cameras, encoders, or WebRTC clients, and.

Canonical page: https://ourlocalhost.com/app/7264/livekit-ingress

## Description

LiveKit Ingress is an ingestion service for self-hosted LiveKit deployments that accepts RTMP (Real-Time Messaging Protocol) and WHIP (WebRTC-Initiated HTTP) streams from cameras, encoders, or WebRTC clients, and transcodes that media into WebRTC for publication into LiveKit rooms.

## Platform availability

Available on 1 of 10 platforms: Helm.

## Health score

35/100 (Low), based on 4 of 5 factors.
- Maintained: 0 (GitHub repository is archived)
- Popular: 46 (194 GitHub stars)
- Easy to install: 25 (1 install platform, install notes)
- Security check: 100 (no serious findings, CI, tests)

## Links

- GitHub: https://github.com/livekit/ingress
- Official website: https://kubernetes.github.io/ingress-nginx/

## 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.

---
Source: Our Local Host (https://ourlocalhost.com/app/7264/livekit-ingress), the self-hosted and open-source app directory.
