I am trying to deploy livekit-server and egress to an EKS cluster. Whenever I try to start a RoomComposite Egress I get an error like "Start signal not received" The same config works when I run both locally.

Thanks for reaching out, Erik. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

I am using LiveKit Egress v1.8.4 and LiveKit Server v1.9.0 Attached are the logs. I am not sure about the custom network policies, I've followed the documentation about Security Groups.

Hey there! Dealing with the "Start signal not received" error can be frustrating, but don't worry—we'll work through this together. This usually happens when the egress service starts a browser session but doesn't get the expected start signal within the expected time. Let me walk you through some friendly troubleshooting steps: 1. Check Template Accessibility • First things first, make sure your custom template (or the default LiveKit templates) can actually be reached from your EKS cluster. • Take a moment to verify that network connections are smooth between your egress pods and the template URL. • Do a quick check on any firewalls or network policies that might be blocking access. • Pro tip: Try loading the template manually from within the cluster to see if everything looks good. 2. Browser Resource Issues • Your EKS nodes need some breathing room—make sure they have enough CPU and memory to work comfortably. • Double-check that your egress pods have the resources they need. • Keep an eye out for any pod restarts or resource squeezes. 3. Template Loading Problems • Confirm that your template is playing nicely with the LiveKit egress interface. • If you can, peek at the browser console logs for any JavaScript hiccups. • Verify that your template is sending out that crucial start signal. 4. Timeout Configuration • Sometimes templates just need a bit more time to load, especially with network latency. • You might want to see if you can adjust the timeout settings in your egress configuration. 5. EKS-Specific Considerations • Make sure your EKS cluster can resolve DNS without breaking a sweat. • Check if any service mesh or ingress controllers are causing any interference. • Confirm that the egress service has all the permissions and network access it needs. 6. Version Compatibility • Ensure LiveKit Egress v1.8.4 and Server v1.9.0 are playing well together. • Verify that your template is compatible with the egress version you're using. One more thing—take a peek at the egress service logs. They might give us some extra clues about why that start signal isn't coming through. If you're still stuck after trying these steps, just give me a shout, and we'll solve this together!

When I load the template manually I see an error "could not establish pc connection"

Hey there! Looks like you're running into a tricky WebRTC connection issue with your LiveKit room. Don't worry, we'll work through this together. 😊 1. Network Connectivity • First things first, let's make sure your network is playing nice. Can you confirm that the egress service can actually reach your LiveKit server? • Sometimes firewalls or network settings can be sneaky and block WebRTC connections. We'll want to check those out. 2. Authentication • Quick check: Is your egress token up to date and has all the right permissions to join the room? 3. Template Configuration • Let's take a look at your template setup. Make sure everything is configured correctly to connect to the LiveKit room. • Pro tip: Open up your browser console and see if any JavaScript errors pop up when you load the template. 4. EKS-Specific Issues • If you're using EKS, let's verify that your cluster is WebRTC-friendly and can resolve DNS for the LiveKit server. I recommend checking the egress service logs and browser console for more clues. We'll get to the bottom of this together! If you need more help, just give me a shout. 🤝 Sources: livekit-api/src/services/egress.rs | livekit-android-sdk/src/main/java/io/livekit/android/room/RTCEngine.kt | Universal Egress

Which node actually loads the template?

Hey there! Let me break down how LiveKit RoomComposite Egress works in a super friendly way. It's actually pretty cool how the recording process comes together: • First, the egress service gets your recording request and starts setting everything up. • Then, it launches a headless Chrome browser to help render your view. • This Chrome instance pulls up your chosen template - whether it's the default one or a custom URL you've picked. • It then captures all the participants in the room, creating this awesome composited view that gets encoded into your final output. If you're running into any hiccups with the template loading, don't worry! It might just be a connection issue between Chrome and your LiveKit room. I'm totally here to help you troubleshoot and get everything running smoothly. Just let me know what you're experiencing, and we'll figure it out together! Sources: Universal Egress | Custom recording templates | LiveKit Docs | Composite and web recordings | LiveKit Docs