Skip to main content

​
Browser cannot access microphone

Browser microphone access requires HTTPS in production. Use one of these:
  • https://your-domain.com
  • http://localhost for local development
If your WaGo server is behind a reverse proxy, make sure the browser calls the HTTPS URL.

​
WebRTC connects on localhost but not for users

WaGo currently uses STUN only: 
stun:stun.l.google.com:19302
Some networks require TURN relay. Until TURN support is added, calls may fail on:
  • Strict NAT networks
  • Corporate networks
  • Some mobile networks
  • Firewalls that block UDP

​
turn.status is coming_soon

This is expected. TURN configuration is not available yet.

​
Repeated empty Opus packet logs

Browsers can send empty RTP packets for padding or keepalive. WaGo ignores empty RTP payloads before decoding. If live audio works, these packets are not a call failure.

​
No active call found

Make sure you have a valid CallID. List active calls: 
curl -H "token: YOUR_TOKEN" \
  http://localhost:1337/call/status

​
Call starts but no audio is heard

Check these points:
  • The browser has microphone permission.
  • The session is connected and scanned.
  • The call is answered.
  • The browser has completed the WebRTC offer flow.
  • The server is reachable from the browser over HTTPS.
  • The network does not require TURN relay.