Thanks — I’m looking at the logs you sent showing the Room Composite egress failing with

page load error: timed out

. I’ll walk through the most likely causes and step-by-step checks you can do for a custom template to get this working. Quick summary of what this means • The Room Composite egress starts a headless Chrome process to render your custom template and capture video. The error means Chrome could not load the page within the allowed time, so the egress failed. Please try these checks and let me know results for any item you can’t complete or if something changes. 1) Verify your custom template URL is reachable • Open the template URL from a browser on a machine in the same network as your egress service. Confirm it loads quickly and without redirects that require user interaction. • If your template references remote assets (fonts, scripts, video overlays), ensure those assets are reachable from the egress host. 2) Test using a known working layout • Temporarily switch to a built-in layout (for example

speaker-dark

) to confirm if the problem is specific to the custom template. • If the built-in layout works, the issue is in the custom template (size, assets, JS blocking page load). 3) Confirm Chrome/Chromium is installed and accessible • Ensure a Chrome/Chromium binary is present on the egress host and is runnable by the egress process. • If the binary isn’t on PATH, set

CHROME_EXECUTABLE

to the full path of the binary. 4) Check host resources and instance type • Chrome in headless mode needs CPU and memory. Ensure the host has sufficient resources and isn’t CPU-throttled. • Avoid CPU-burstable instances (t3/t4) where CPU credits can be exhausted; use general-purpose instances (m5, c5, etc.) for stable CPU performance. 5) Inspect network and DNS from the egress host • From the egress host, curl or wget your template URL and any external assets to ensure DNS and outbound network are working. • If your template uses HTTPS, confirm certificate trust is OK on the host. 6) Look for Chrome startup/renderer errors • Check egress or Chrome logs for errors about sandboxing, missing libraries, or crashes that could prevent Chrome from launching. • If running in a container, ensure necessary libraries (libnss, libatk, etc.) or packages that Chrome requires are installed. 7) Reduce template complexity and JS blocking • Some heavy JS or long-running synchronous scripts can delay load. Try a minimal version of your template (static HTML/CSS) and see if the page loads for the egress. • Gradually reintroduce complexity until you identify the blocking piece. 8) Consider using Track Composite as a fallback • Track Composite egress does not require headless Chrome. If you need an immediate workaround while debugging the template, use Track Composite to produce files without browser rendering. If you want, please share: • The custom template URL (or a minimal reproduction) so I can suggest specific edits. • The host environment (container vs VM, instance type) and whether Chrome is installed there. • Any additional egress logs around the time of failure (Chrome startup lines or more verbose logs). I’ll help you narrow it down based on what you find. Sources: Universal Egress | Troubleshooting Latency and Timeout Errors with Turn Detection on AWS