Source Status & Error Reference
A source (input) reports a connection state plus, when something goes wrong, an error reason. The states and error reasons below are the full set a source can display.
Connection States
Status | Meaning |
|---|---|
Offline | The source is not active. It is stopped or has not started yet. |
Connecting | The source is attempting to establish its connection for the first time. |
Reconnecting | The source lost its connection and is trying to re-establish it. |
Connected | The source is connected and receiving data normally. |
Error Reasons
Network & Connection
Status | Why it happens |
|---|---|
Resolve | The hostname of the remote source could not be resolved via DNS. Usually a bad address or a DNS problem. |
Timeout | No response or no data was received within the allowed time. The remote end is unreachable, too slow, or has gone away. |
Network | A general network failure, or the network subsystem could not be started. |
TCP connect failed | A TCP connection to the remote source could not be established (wrong address/port, blocked by firewall, or remote not listening). |
Connection closed | The remote end closed the TCP connection. |
Failed to connect | The connection attempt failed. |
Failed to bind | The local socket could not be bound to the requested address/port. |
Failed to enter listening state | The source could not start listening for incoming connections. |
Port in use | The port the source needs is already being used by something else. |
Failed to open port | The required port could not be opened (the source is busy or the port is unavailable). |
Socket open error | A network socket could not be created or opened. |
Too large MTU | The configured packet size (MTU) exceeds what is allowed. |
Redirected | The server redirected the source to a different host (normally handled automatically). |
Protocol & Stream Negotiation
Status | Why it happens |
|---|---|
Protocol | A protocol-level message could not be parsed, or the remote reported a protocol error. |
Full | The remote server is at capacity and cannot accept the connection. |
Rejected | The connection was refused. Usually this stream is already connected elsewhere. |
Reconnected | The source was replaced by a newer connection (e.g. during failover). |
Remote stream closed | The remote side closed the stream. |
Stopped | The source was stopped manually. |
Limit | A configured limit was reached. |
Not Supported | A requested feature or operation is not supported. |
Illegal name | The stream name is invalid or improperly formatted. |
Double RTP header | A packet arrived with a malformed (double) RTP header. |
Payload is not transport stream | The incoming data is not valid MPEG transport stream. |
Source Availability
Status | Why it happens |
|---|---|
No Source | The requested stream was not found on the remote server, or no stream is currently available. |
Over max outputs configuration | The source has reached its configured maximum number of outputs/connections. |
Multiple sources detected | More than one source is broadcasting to the same stream simultaneously (a collision). |
No multicast data | The source could not join the multicast group, or no multicast data is being received. |
NDI Stream not found | The specified NDI stream could not be located on the network. |
Authentication, Licensing & Security
Status | Why it happens |
|---|---|
Authentication | Authentication with the remote source failed (bad credentials). |
Licensing | The connection failed due to a licensing restriction on the remote. |
Certificate error | The security certificate presented during a secure (DTLS) handshake was invalid. |
DTLS handshake error | The encrypted (DTLS) handshake failed, or encryption was unexpectedly disabled. |
Wrong DTLS-SRP username or password | The DTLS-SRP credentials supplied were incorrect. |
Data is encrypted | The data is encrypted and cannot be processed (a key mismatch, missing key, or an attempt to re-encrypt already-encrypted data). |
Bitrate & Quality
Status | Why it happens |
|---|---|
Zero bitrate | The source stream is reporting no data flow (zero bitrate). |
Insufficient bitrate | The source bitrate is too low for what is required. |
Remote version doesn't support high bitrate | The remote device's software version cannot handle the required high bitrate. |
Max bitrate times latency too high | The combination of maximum bitrate and configured latency exceeds the allowed limit. |
Performance | A performance threshold was exceeded (the system could not keep up). |
Data Integrity
Status | Why it happens |
|---|---|
Overflow | A buffer overflowed: data arrived faster than it could be processed. |
Compression error | An incoming packet could not be decompressed. |
Muxing error | The stream could not be re-muxed/combined correctly. |
Multiplex error | A multiplexing operation failed. |
Bad PID mapping configuration | The PID remapping configuration is invalid. |
Error concealer | The error-concealment subsystem encountered a problem. |
CBR Padder error | The constant-bitrate padding subsystem failed. |
PID interleaver error | The PID interleaver subsystem failed. |
Frame thinner error | The frame-thinning subsystem failed. |
RTMP Sources
Status | Why it happens |
|---|---|
RTMP connect failed | The RTMP connection could not be established. |
RTMP handshake failed | The RTMP handshake negotiation failed. |
RTMP stream failed | The RTMP stream operation failed. |
RTMP publish failed | The RTMP publish operation failed. |
RTMP play failed | The RTMP play operation failed. |
RTMP protocol malfunction | The RTMP protocol could not be parsed or handled correctly. |
Timeout, Bad stream data | RTMP stream analysis timed out because the incoming data was bad or incomplete. |
Unsupported encoding | The RTMP stream uses an encoding that is not supported. |
Akamai authentication | Authentication to Akamai failed. |
Adaptive / HLS / DASH
Status | Why it happens |
|---|---|
Adaptive stream | An adaptive stream was received but no adaptive handler is configured to process it. |
Source not adaptive | The source does not support adaptive bitrate. |
Unaligned timestamps | The adaptive stream has timestamps that are not aligned, preventing segmentation. |
Failed to create segment | A timeout occurred while creating an adaptive stream segment. |
No valid segmentation point found | No suitable point was found to split the stream into segments. |
HLS/DASH failed to upload | An HLS or DASH segment failed to upload to its destination. |
HLS disabled | HLS output is disabled. |
MDP disabled | DASH (MPD) output is disabled. |
Head request failed | An HTTP HEAD request (used to probe an adaptive source) failed. |
RIST
Status | Why it happens |
|---|---|
Didn't receive RTCP packets for 10 seconds | A RIST Simple Profile source stopped receiving the expected RTCP control packets for over 10 seconds. |
Files & Storage
Status | Why it happens |
|---|---|
End of file | A file-based source reached the end of the file. |
Local file error | An error occurred accessing the local file system. |
Remote file error | An error occurred accessing a remote file system. |
Invalid file | The source file is invalid or corrupt. |
file not found | The source file could not be found. |
can not open file | The source file could not be opened. |
Not enough disk space | The disk ran out of space. |
System & Hardware
Status | Why it happens |
|---|---|
Out of memory | A memory allocation failed. |
Failed to create sink | An output (sink) for the source could not be created. |
Transcoder | The transcoding subsystem encountered an error. |
Failed to start program | An external helper program could not be started. |
Failed to access program | Communication with an external helper program failed. |
Failed to load library | A required software library could not be loaded. |
Driver not up to date | The hardware driver is too old. |
Cuda not up to date | The CUDA (GPU) version is too old. |
P2P error | A peer-to-peer connection was aborted. |
Destination address error | The destination address could not be found or is invalid. |
DRM
Status | Why it happens |
|---|---|
DRM license or cpix error | A DRM license or CPIX configuration error occurred. |
DRM encryptor init error | The DRM encryptor failed to initialize. |
DRM encrypt error | A DRM encryption operation failed. |
DRM wrong flow | DRM operations were performed in an invalid order. |
DRM missing buffer | A required buffer for DRM was missing. |
DRM not supported feature | A requested DRM feature is not supported. |
Licensing (License Manager)
Status | Why it happens |
|---|---|
License file not found | The license file is missing. |
License file wrong version | The license file is the wrong version. |
License file wrong format | The license file is malformed. |
License file sign / License file verification | The license file's signature could not be verified. |
License expired | The license has expired. |
License limit | A licensed limit has been reached. |
License value out of range | A license value is outside its allowed range. |
Unknown license name | The license name is not recognized. |
The license is not present in the license file | The required license entry is missing from the file. |
License hostname and hostname mismatch | The license is tied to a different hostname than the current machine. |
System clock has been set back | The system clock was moved backward (license tamper protection). |
VM is not allowed | The license does not permit running in a virtual machine. |
Expired | The item has expired. |
Billing code | A billing-code related error occurred. |
Failover
Status | Why it happens |
|---|---|
Streams not identical | Sources in a failover group could not be merged because the streams are not identical. |
Generic / Fallback
Status | Why it happens |
|---|---|
Error | A generic, unclassified error occurred. |
Unknown | The cause of the error could not be determined. |
None | No error reason is reported. On a Connected source this is the normal state. On any other state it means no reason was given, so check the Broadcaster Event Log. |