👋 Welcome to the Link Help Center
Find the answers you need—fast and easy
Deployment Preparation
1. Prepare the Audio/Video Domain
Prepare a dedicated domain name, for example:
livekit.example.comIn your DNS provider's console, add an A record that resolves the domain to the LiveKit server's public IP address:
Record type: A
Host record: livekit
Value: 203.0.113.10192.168.x.x, 10.x.x.x and 172.16.x.x-172.31.x.x are private IP address ranges and cannot be used as the DNS target for public clients accessing LiveKit. Private addresses may be used only in a fully isolated deployment where every client can directly reach that private network.
Before deployment, run the following command to verify DNS resolution:
host livekit.example.com
The returned address must match the public IP address of the current LiveKit server. Do not start automatic certificate issuance until DNS propagation is complete.
2. Prepare the Certificate Contact Email
Prepare a long-lived, actively monitored email address, for example:
ops@example.com
The installation script writes this address to the dedicated LiveKit Caddy configuration. It is used to register an ACME account with Let's Encrypt, request and renew TLS certificates automatically, and receive certificate-related notifications.
Use a shared operations team mailbox. Do not use the personal mailbox of someone who may leave the company, a temporary mailbox, or an address that cannot receive external email. Verify the spelling after entering the address.
3. Prepare the Link Webhook URL
Prepare a Link audio/video notification callback URL that LiveKit can reach:
http://<gateway-ip>:<gateway-port>/live/v1/webhook
Example:
http://192.168.1.20:19080/live/v1/webhook
Notes:
POST, and the request content type is application/webhook+json.Authorization header. Link uses the same AccessKeyID and AccessKeySecret to verify the request source and body integrity.4. Prepare Access Credentials
Prepare one credential pair shared by LiveKit and Link:
AccessKeyID: LiveKit API Key.AccessKeySecret: LiveKit API Secret.config.yaml in keys.config.yaml in webhook.api_key.