Skip to main content

Troubleshooting Input Connection Issues

Written by Julian Rodrigues
Updated today

When an Input fails to connect or appear in LIGR Live, your encoder video feed won't reach the platform, which prevents streaming to Destinations and can disrupt graphics output during a Match.


Before You Start

Make sure you have the following in place before troubleshooting:


• An active Match set up in the Matches section


• An encoder such as OBS, vMix, or a hardware encoder ready to send video


• The RTMP or NDI connection details from your Input in LIGR Live


• A stable internet connection on the encoder machine


[ Image placeholder: Streaming tab showing the list of Inputs and their connection status ]


Check Your Input Status in LIGR Live

The first step is to confirm what LIGR Live is seeing from your encoder.


1. Open the Streaming tab in the left sidebar.


2. Locate your Input in the list.


3. Check the connection status indicator next to the Input name.


4. If the Input shows as disconnected, your encoder is not successfully sending video to LIGR.


What the Status Tells You

Connected — LIGR is receiving the feed and the Input is healthy


Disconnected — No feed is arriving from the encoder


Unstable — The feed is arriving but with drops or quality issues


Common Causes of Input Connection Issues

Most Input problems come down to one of these areas:


• Incorrect RTMP URL or stream key in the encoder


• Encoder not running or not started


• Firewall or network blocking the outbound stream


• Bitrate set too high for the available upload bandwidth


• NDI source not visible on the same network as LIGR


• Encoder sending an unsupported resolution or frame rate


Troubleshooting Steps

1. Verify Your Encoder Settings

1. Open your encoder (OBS, vMix, or hardware).


2. Check that the RTMP URL and stream key match exactly what is shown for your Input in the Streaming tab.


3. Confirm the encoder is actively streaming, not just previewing.


[ Image placeholder: Streaming tab showing the RTMP URL and stream key fields for an Input ]


2. Restart the Stream from the Encoder

1. Stop the stream in your encoder.


2. Wait 10–15 seconds.


3. Start the stream again.


4. Return to the Streaming tab in LIGR Live and check if the Input status updates to Connected.


3. Check Your Network and Bandwidth

1. Run a speed test on the encoder machine.


2. Confirm your upload speed is well above your configured bitrate.


3. If bandwidth is limited, lower the bitrate in your encoder and try again.


4. Check Firewall and Port Access

1. Make sure your network allows outbound RTMP traffic.


2. If you are on a corporate or venue network, ask IT to confirm RTMP is not blocked.


5. For NDI Inputs

1. Confirm the NDI source machine and LIGR receiver are on the same network.


2. Restart the NDI source in the encoder.


3. Check that NDI discovery is not blocked by a firewall.


Tips

• Always test your Input connection before the scheduled Match start time, ideally 15–30 minutes in advance.


• Keep a note of your RTMP URL and stream key somewhere secure so you can quickly re-enter them if the encoder is reset.


• If you are using vMix NDI, refer to the existing vMix NDI troubleshooting article for source-specific fixes.


• Use the Multiview feature to visually confirm the Input is arriving as expected.


Common Issues

Input Shows Connected but No Video in Multiview

• The encoder may be sending audio only or a black frame


• Check the video source selected in your encoder scene


Input Keeps Disconnecting Mid-Match

• Usually caused by unstable upload bandwidth


• Lower the bitrate in your encoder


• Switch to a wired network connection if possible


Input Never Connects

• Double-check the RTMP URL and stream key for typos


• Confirm the encoder is pointed at the correct Input for this Match


• Make sure another encoder is not already using the same Input


Stream Arrives but Destinations Don't Receive It

• The issue is likely on the Destination side, not the Input


• Verify the Destination RTMP details and that the target platform (YouTube, Facebook, RTMP endpoint) is live-ready

Did this answer your question?