This page shows you how to resolve issues with the Live Stream API. The errorsshown on this page are specific to the Live Stream API. For information ongeneric errors across Google APIs, see the Cloud APIsErrors page.

Input stream rejected

If your encoder sends an input stream to an input endpoint, but the connectionkeeps getting rejected, check for these possible issues:

Invalid input endpoint URI

An error occurs if your encoder sends an input stream to an invalid inputendpoint URI.

To resolve this issue, check if your encoder is configured to send the inputstream to an input endpoint URI with thecorrect IP address andSTREAM-ID.

Input is not attached to a channel

An error occurs if your encoder sends an input stream to an input endpoint URIthat is not attached to a channel.

To resolve this issue,create a new channel with the inputendpoint. To check if an input endpoint has been successfully attached to thechannel,get the channel details and look for the name of theinput endpoint in theinputAttachments field.

Inactive channel

An error occurs if your encoder sends an input stream to a channel that is notrunning.

To resolve this issue,check the status of the channel to makesure itsstreamingState isAWAITING_INPUT. If thestreamingState of thechannel isSTOPPED,start the channel.

Another encoder already connected with the same input endpoint

An error occurs if multiple encoders attempt to send input streams to the sameinput endpoint. Only one connection is accepted at a time per input endpointURI.

To resolve this issue,check if the channel is already inSTREAMING state. If so, you have the following options:

• Create a separate input endpoint and channel for the second input stream.

• Stop the first input stream before sending another one to the same input endpoint.

Encoder IP address is not in the allowed IP ranges

An error occurs if your encoder sends an input stream from an IP address outsidethe specified IP ranges configured for an input endpoint.

To resolve this issue,get the details for an input endpoint andcheck thesecurityRules field. If there are specifiedipRanges, make sure your encoder has a valid IP address in those IPranges.

Missing output files in the Cloud Storage bucket

If your encoder is successfully sending an input stream to the input endpoint,but no output files appear in the Cloud Storage bucket, check for thesepossible issues:

Incorrect Cloud Storage bucket

Output files may be missing if you are checking the wrong Cloud Storage bucket.

To resolve this issue,get the channel details for your livestream. Check theoutput.uri field for the correct Cloud Storage bucket URI.

Invalid input video/audio codecs

Output files may be missing if your encoder is sending invalid video or audio codecs.

To resolve this issue, make sure your encoder is only sending H264 video and AACaudio codecs.

Cloud Storage permission denied

By default, the Live Stream API creates a service account that can accessCloud Storage buckets in the same Google Cloud project that hosts theLive Stream API resources. Output files may be missing if this service accountloses permission to access the Cloud Storage bucket.

To resolve this issue, make sure the service account has sufficient permissions.The creation of output files may fail for the following reasons:

• The output Cloud Storage bucket is in a different Google Cloudproject from Live Stream API resources such as the channel and input endpoint.

• The default permissions are revoked from the service account.

SeeAccess to Cloud Storage for more information.

Missing audio tracks

Output files may be missing if your encoder sends an input stream with missingaudio tracks. The video pipeline waits for all audio tracks to arrive beforeprocessing begins.

To resolve this issue,get the channel details for your livestream. Make sure your encoder is sending all audio tracks configured in theElementaryStream.audioStream.mapping (AudioMapping) field.