Problem
Automatic network failover changes the public IP mid-stream and the broadcast connection does not recover cleanly.
Solution
Root Cause / Diagnostic:
Standard dual-WAN routers execute link failover by terminating the dead interface and rerouting outbound traffic across a backup WAN carrying a different public IP address. Because standard RTMP sessions rely on stateful TCP sockets bound strictly to the initial client IP, YouTube's ingest server rejects packets arriving from the new IP. The encoder enters a continuous reconnection cycle or terminates the stream completely.
Actionable Fix:
1. Implement a network bonding service or cloud aggregation tunnel (e.g., Speedify, LiveU, or an SRT relay) that preserves a persistent single public IP.
2. In encoder settings, enable auto-reconnect with a 1-second retry delay and configure retry attempts to 60 to accelerate socket re-establishment.
3. Simulate an unexpected WAN disconnect during a private test stream to verify that the broadcast reconnects cleanly within YouTube's player buffer window.
Pro Tip:
Utilize YouTube's persistent stream key architecture with backup ingest enabled so that even if an IP reset forces a reconnect, your live viewers stay in the player without refreshing.
Standard dual-WAN routers execute link failover by terminating the dead interface and rerouting outbound traffic across a backup WAN carrying a different public IP address. Because standard RTMP sessions rely on stateful TCP sockets bound strictly to the initial client IP, YouTube's ingest server rejects packets arriving from the new IP. The encoder enters a continuous reconnection cycle or terminates the stream completely.
Actionable Fix:
1. Implement a network bonding service or cloud aggregation tunnel (e.g., Speedify, LiveU, or an SRT relay) that preserves a persistent single public IP.
2. In encoder settings, enable auto-reconnect with a 1-second retry delay and configure retry attempts to 60 to accelerate socket re-establishment.
3. Simulate an unexpected WAN disconnect during a private test stream to verify that the broadcast reconnects cleanly within YouTube's player buffer window.
Pro Tip:
Utilize YouTube's persistent stream key architecture with backup ingest enabled so that even if an IP reset forces a reconnect, your live viewers stay in the player without refreshing.