Troubleshooting Output Error Messages

If your live output is in the Error state and you are unable to fix it. This page offers a comprehensive guide to troubleshooting common messages that may occur during the broadcast. The steps outlined aim to assist users in resolving any technical issues and ensuring the smooth operation of their broadcast:

Output in an error state

Received error: Operation not permitted

• This error message is usually returned by an RTMP server when it rejects the stream. This could be because:
  • There is already a stream publishing to that endpoint
  • The server application or stream key has been entered incorrectly
  • There is a missing username/passphrase
  • Some other error on the server
• Try double checking your server hostname, application and streamkey are correct. For more information on how to construct RTMP urls, click here.
• If that does not fix it, please contact the downstream server administrator.

Received error: Failed to resolve hostname:

• This error message occurs when the hostname cannot be resolved by DNS.
• Double-check that you have entered the correct destination URL.
• If that does not fix it, please contact the downstream server administrator.

Received error: Cannot open connection:

• This error message occurs when there is a problem with the destination URL.
• Double-check that you have entered the correct destination URL.
• If that does not fix it, please contact the downstream server administrator.

Received error: Operation timed out:

• This error message is caused when we attempt to connect to a server, but receive no response.
• This can be caused by
  • A firewall blocking our incoming connection attempts.
  • The incorrect hostname/IP. Please do
  • The downstream server not being setup to receive the stream yet.
• Double-check that you have entered the correct destination URL.
• Check the downstream server's firewall settings and make sure the server has incoming traffic allowed.
  • For RTMP, usually this is on TCP port 1935
  • For SRT, this will correspond to the port in the URL
• Ensure the downstream server is up, and accessible by other means
• If that does not fix it, please contact the downstream server administrator.

Received error: Connection refused:

• This error message occurs when we reach the downstream server, but it refuses to accept our connection attempt.
• This is typically when the downstream server is not running
• Verify that the endpoint is online and reachable, and that your firewall settings are not blocking the connection.

You are trying to send multi-track audio to RTMP which only supports one audio track:

• RTMP only supports one audio track, so if you are trying to send a multi-track audio stream, it will result in an error.
• Use the "Advanced Settings" to select the audio track you would like to send, using the "Audio Selector" option.

Received error: Operation not supported: Bad parameters:

• This error message is usually returned by an RTMP server when it rejects the stream. This could be because:
  
  • The server application or stream key has been entered incorrectly
  • There is a missing username/passphrase
  • The audio and video settings are not accepted
  • Some other error on the server
• Try double checking your server hostname, application and streamkey are correct. For more information on how to construct RTMP urls, click here.
• If that does not fix it, please contact the downstream server administrator.

If your error message does not match any of the messages listed above, we recommend contacting your broadcast engineers or reaching out to Spalk support. Our team will do their best to assist you in resolving any technical issues and ensuring the smooth operation of your broadcast.