👋 Welcome to the Link Help Center
Find the answers you need—fast and easy
Verify HTTPS/WSS Configuration
LiveKit clients must use HTTPS/WSS. The installation script deploys a dedicated Caddy instance for LiveKit, generates its Caddy configuration automatically, and reverse-proxies signaling requests to 127.0.0.1:7880.
1. Verify Prerequisites
Before the installation script requests a TLS certificate, verify the following:
80/TCP and 443/TCP are allowed by the cloud security group, host firewall, and NAT configuration.80/TCP and 443/TCP are not in use by another application or container.2. Review the Generated Caddy Configuration
Based on the audio/video domain entered by the user, the installation script automatically generates a Caddy configuration equivalent to the following:
{
admin off
email ops@example.com
}
livekit.example.com {
reverse_proxy 127.0.0.1:7880
}
Caddy uses the email entered during installation to register an ACME account with Let's Encrypt and to request and renew TLS certificates automatically. A normal installation does not require manual Caddyfile changes. If the domain or email is incorrect, rerun the LiveKit installation script and enter the correct configuration when prompted.
3. Verify Caddy and TLS
After installation, use the installation output or LiveKit service status to confirm that the dedicated Caddy instance is running. To inspect container status, run:
sudo docker ps --filter name=livekit
Verify HTTPS:
curl -v https://livekit.example.com/
The TLS handshake and certificate validation must succeed. If a certificate error or connection timeout occurs, check DNS, 80/TCP, 443/TCP, and the status of the dedicated LiveKit Caddy instance.