Managing stream reconnection in LIGR Live helps you recover quickly when an Input drops out or a Destination stops receiving video during a live Match.
Overview
A stream disconnection can happen for several reasons, including encoder issues, network interruptions, or problems at the Destination (such as YouTube Live or Facebook Live). LIGR Live provides visibility into stream health through the Streaming tab and individual Match Stream View pages, so you can identify issues and restore your broadcast as quickly as possible.
This guide covers how to monitor stream status, reconnect a dropped Input, and troubleshoot when a Destination stops receiving video.
Prerequisites
Before you can manage stream reconnection, you need:
• An active Match with streaming configured
• Access to the Streaming tab or the relevant Match Stream View page
• Access to your encoder (OBS, vMix, or hardware encoder)
• Permission level of Gameday Operator, User, Admin, or Owner
Monitoring Stream Health
You can check the health of your streams in two places:
• Streaming tab — View multiple streams at once using Multiview and see the overall status of each Input and Destination.
• Match Stream View — Open a specific Match to see detailed status for its Input and Destinations.
[ Image placeholder: Streaming tab showing Multiview with stream health indicators for each active Match ]
What to look for
• Input status (connected or disconnected)
• Destination status for each output (YouTube Live, Facebook Live, RTMP endpoints)
• Bitrate and stream activity indicators
Reconnecting a Dropped Input
If your encoder loses connection to LIGR, the Input will show as disconnected.
1. Open the Streaming tab or the affected Match Stream View.
2. Confirm the Input has dropped by checking its status indicator.
3. Go to your encoder (OBS, vMix, or hardware encoder).
4. Stop streaming in the encoder.
5. Verify your network connection is stable.
6. Restart the stream in your encoder using the same RTMP settings.
7. Return to LIGR Live and confirm the Input status returns to connected.
[ Image placeholder: Match Stream View showing Input status and Destination status panels ]
Reconnecting a Destination
If your Input is healthy but a Destination has stopped receiving video, the issue is usually at the Destination end.
1. Open the Match Stream View for the affected Match.
2. Check the status of each configured Destination.
3. If a Destination shows as disconnected, verify the Destination itself (for example, check your YouTube Live dashboard or Facebook Live Producer).
4. If the Destination is still active on its end, stop and restart the Destination from within LIGR Live.
5. Confirm the Destination status returns to connected.
Tips
• Always test your Input and Destinations before the Match starts to catch configuration issues early.
• Keep your encoder's streaming settings documented so you can restart quickly without reconfiguring.
• Use Multiview in the Streaming tab on match day so you can spot dropouts across multiple Matches at once.
• A wired internet connection on the encoder side is more reliable than Wi-Fi for live streaming.
• If you know network conditions are unstable, lower your encoder bitrate before going live.
Common Issues
Input keeps dropping repeatedly
This usually points to an unstable connection on the encoder side. Check your upload bandwidth, switch to a wired connection if possible, and lower the encoder bitrate.
Input is connected but Destination shows no video
Verify the Destination is still live on its platform. Some platforms (like YouTube Live) will end a broadcast if they stop receiving video for too long, requiring you to create a new stream key.
Stream reconnects but graphics are missing
After an Input reconnection, check the Control Room to confirm your Overlays and Scorebug are still active. You may need to re-trigger graphics manually or resume your Automated Game Plan.
Can't identify which end caused the dropout
Check the Input status first. If the Input is healthy, the issue is between LIGR and the Destination. If the Input is disconnected, the issue is between your encoder and LIGR.