Introduction
Use this guide to configure origin failover for a live stream so playback can continue if the primary origin becomes unavailable. This setup is commonly used in broadcast, OTT, live sports, and other professional streaming workflows where continuity and low downtime are critical.
Issue description
Failover allows your publication destination, player, or delivery layer to switch from a primary origin to a backup origin when the primary path fails. When configured correctly, viewers keep using the same playback URL while traffic is redirected to the backup origin.
Prerequisites
- A primary origin and a backup origin already deployed
- An encoder, packager, or origin workflow that can publish to both origins
- Matching ingest protocol, stream parameters, and authentication settings on both origins
- Network access from your publishing system to the backup origin
- Permission to review encoder logs, origin health checks, and load balancer or DNS settings
Step-by-step instructions
1. Configure the primary and backup origins
Set up both origins in your workflow and confirm that each one is ready to receive the same live stream. Use the same stream name, ingest protocol, codec profile, and authentication method on both sides.
2. Enable redundancy or failover on the publication destination
In your encoder, packager, or publication destination, enable the redundancy or failover option. If your platform supports primary and secondary endpoints, enter both origin endpoints and define the primary as the default path.
3. Verify network reachability
Confirm that the backup origin is reachable from the network where your encoder or packager runs. Check firewalls, routing rules, security groups, and any allowlists that may block the backup path.
4. Review health check and switch thresholds
Set or confirm the health check interval, timeout, and retry thresholds used to detect origin failure. Shorter thresholds can improve recovery time, but overly aggressive values may cause unnecessary switching.
5. Test the failover behavior
Start a live stream through the primary origin, then temporarily stop the primary origin or block its ingest path. Verify that playback continues through the backup origin without changing the playback URL.
6. Restore the primary origin and confirm recovery behavior
Bring the primary origin back online and confirm whether your workflow switches back automatically or remains on the backup until the next session. Use the behavior that best matches your operational requirements.
Basic troubleshooting steps
- Confirm both origins use identical stream parameters
- Check that authentication credentials are valid on both origins
- Verify the backup origin is reachable from your network
- Review encoder or packager logs for connection errors
- Check DNS, load balancer, or routing rules if failover depends on them
- Confirm health check thresholds are not delaying the switch
Diagnostic tools and resources
- Encoder or packager logs
- Origin health check status pages
- Network connectivity tests such as ping, traceroute, or telnet where appropriate
- Load balancer or DNS configuration panels
- Playback monitoring tools or test players
Advanced troubleshooting steps
1. Inspect encoder logs for failover triggers
Look for connection timeouts, authentication failures, repeated retries, or origin unreachable messages. These entries usually indicate whether the failover condition was detected and whether the backup path was attempted.
2. Validate origin health checks and timeout logic
Review the health check method used by your platform. If the check depends on HTTP responses, ingest acknowledgements, or segment availability, confirm that the backup origin returns the expected response within the configured timeout.
3. Review DNS or load balancer rules
If failover is handled by DNS or a load balancer, confirm that the failover target is updated correctly and that TTL, caching, or routing rules are not delaying the switch.
4. Check latency and segment timing
Excessive latency, long segment durations, or mismatched buffer settings can delay failover detection. Align timing settings across the workflow so the backup origin can take over quickly and cleanly.
5. Confirm playback continuity on the client side
Test with more than one player or device if possible. Some playback clients cache manifests or segments differently, which can affect how quickly they recover after an origin switch.
Contact support
If failover still does not trigger, contact Cires21 support with the following details: the product or service name, origin configuration, ingest protocol, health check settings, relevant logs, and the time the test was performed. If available, include the playback URL and a short description of the observed behavior.
Additional information
For best results, keep the primary and backup origins synchronized and test failover regularly as part of your operational checks. If your deployment uses a specific Cires21 product such as C21 Live Origin or another publication workflow, refer to the product documentation for any platform-specific failover options.
Conclusion
A reliable failover setup depends on matching origin settings, reachable backup paths, and clear health check logic. After you configure and test the workflow, your live stream should continue on the backup origin without requiring viewers to change URLs.
Comments