👋 Welcome to the Link Help Center
Find the answers you need—fast and easy
Help Center / Audio/video deployment and use / Troubleshooting
Troubleshooting
1. Domain Is Unreachable or Certificate Issuance Fails
Check in the following order:
1. Confirm that the domain's A/AAAA records point to the current server.
2.
80/TCP and 443/TCP are allowed.3. Confirm that Caddy is running normally and that its configuration passes validation.
4. Check whether another process is using port
80 or 443.5. Confirm that the server can reach the ACME certificate service.
6. Confirm that the certificate contact email entered during installation is valid.
2. Clients Cannot Join a Room
Check the following:
• Confirm that the domain, port, and credentials in Link are correct.
• Confirm that clients use
wss://<livekit-domain>.• Confirm that Caddy can connect to
127.0.0.1:7880.• Confirm that the LiveKit and Link server clocks are synchronized.
• Confirm that the AccessKeyID/AccessKeySecret match exactly and contain no extra spaces.
3. Clients Can Join but Have No Audio or Video
This usually means signaling succeeded but the RTC media path failed. Check the following:
•
50000-60000/UDP is fully allowed and mapped correctly.•
7881/TCP is allowed.• Confirm that the server's public IP address is correct and NAT mappings are complete.
• Confirm that clients have granted microphone and camera permissions.
• Check whether the enterprise network or carrier restricts UDP.
• Determine whether TURN/UDP should be enabled or TURN/TLS deployed to support restricted networks.
4. Only One Party Can Hear or See the Other
Check permissions on both clients, uplink connectivity, UDP port mappings, and firewall return-traffic rules. One-way media is usually not a Caddy reverse-proxy issue; focus on WebRTC ICE candidate addresses and media ports.
5. Webhooks Do Not Reach Link
Test network connectivity to the Gateway address from the LiveKit server, then check the following:
•
webhook.urls address, port, and path are correct.• Confirm that Gateway has registered the
/live/v1/webhook route.• Check whether outbound traffic from LiveKit to Gateway is blocked.
• Check the Gateway and Infrastructure logs for signature or request-body parsing errors.
•
webhook.api_key exists in the LiveKit keys.