I am using LiveKit *Cloud* (not local Docker). I’m...
# ask-ai
f
I am using LiveKit Cloud (not local Docker). I’m running a room composite Egress to a WebSocket stream output. - My WebSocket server URL is:
wss://<my-ngrok-url>/?sessionId=12345-test
- The Node.js server and
wscat
test confirm that this exact URL (with query params) works fine. - But when LiveKit Cloud Egress tries to connect, it strips the query parameter and only connects to the root path
/
. This causes my server not to recognize the session properly. Question: Is this a known issue in LiveKit Cloud Egress where query parameters are removed? Or is there a specific configuration/setting to make Egress preserve the full WebSocket URL with query parameters?
t
Thanks for reaching out, Priyanshu. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
Hey there! Just a quick heads-up: LiveKit Cloud Egress doesn’t support WebSocket URLs for room composite egress. WebSocket streaming works only for Track egress, and that’s specifically for audio-only tracks. When using Track egress, it’s a good idea to include query parameters in the WebSocket URL—they’re supported and recommended. If you’re looking to stream room composite content in real-time, you’ve got some great options like RTMP or SRT streaming. But if WebSocket streaming is a must for you, you’d want to go with Track egress to export individual audio tracks without transcoding. Hope this helps! Let me know if you have any other questions. Sources: Egress output types | LiveKit Docs | Track Egress | LiveKit Docs