Skip to content

Medialive getting error with SRT output - Failed to Write to UDP Socket ReliableTs Output Not Connected (retrying...)

0

I've setup live this

OBS Studio --> AWS Medialive : by RTMP Push AWS Medialive -> YouTube : with SRT protocol

In this, I'm getting error like this - Failed to Write to UDP Socket ReliableTs Output Not Connected (retrying...)

What could be issue here?

asked a year ago336 views

3 Answers
0

Hi Ganesh,

It sounds like the RTMP from OBS to MediaLive is working but the SRT output from MediaLive to YouTube is not.

The most likely issue is with the SRT settings on the YouTube endpoint. MediaLive SRT outputs require encryption to be enabled. You will need to ensure that you have the same encryption key (passphrase) setup on both sides. Check the MediaLive user guide for details on how to configure the encryption key using AWS Secrets manager: https://docs.aws.amazon.com/medialive/latest/ug/srt-output-encryption-asm.html

Regards, Steve

AWS

answered a year ago

  • Thanks Steve for quick response!

    Just wanted to check if I doing correctly doing "Output Group" configuration

    1. URL - srt://a.srt.youtube.com:2010
    2. Stream Id - Added "Stream Key" from YouTube
    3. Encryption Passphrase - Added "Passphrase" from YouTube in AWS Secret Manager with "passphrase" as key and passphrase in value.

    Could you please configure if this is correct? Thanks!

  • Following up, you need to use plaintext secrets instead of key/value pairs. This is not mentioned in the MediaLive guide but you can find the details in the MediaConnect guide at https://docs.aws.amazon.com/mediaconnect/latest/ug/encryption-srt-password-set-up.html

0

This error indicates that your MediaLive channel is having trouble establishing or maintaining the SRT connection to YouTube. Here are several potential causes and solutions:

  1. Connection Issues: The SRT protocol requires a stable connection between MediaLive and the destination (YouTube in this case). The error suggests that the UDP socket connection is failing, which could be due to network issues or firewall restrictions.

  2. SRT Configuration Mismatch: There might be a mismatch in the SRT configuration parameters between MediaLive and YouTube. Verify that you've configured the correct:

  • Port numbers
  • Latency settings
  • Encryption settings (if applicable)
  • Connection mode (caller vs listener)
  1. YouTube SRT Endpoint: Ensure that the YouTube SRT ingest endpoint is correctly configured and active. YouTube may have specific requirements for SRT connections that need to be matched in your MediaLive output settings.

  2. Single Connection Limitation: SRT outputs in MediaConnect only support one connection per output. If there are multiple connection attempts to the same SRT endpoint, only one will succeed. Make sure there aren't multiple systems trying to connect to the same YouTube SRT endpoint.

  3. Monitoring and Troubleshooting: To diagnose the issue further:

  • Monitor your stream health using Amazon CloudWatch
  • Review MediaLive log files for more detailed error messages
  • Perform test streams to validate your setup before going live

Before your next streaming attempt, I recommend conducting a test stream to verify your configuration. You can use tools like the active input thumbnail feature or set up a MediaConnect SRT listener output to test your MediaLive output before sending it to YouTube.
Sources
Best practices for streaming to social media platforms using AWS Media Services | AWS for M&E Blog
Only one viewable SRT connection | AWS re:Post

answered a year ago

0

You can try other ingest protocols that accepted by YouTube like RTMP or HLS. MediaLive support both options.

AWS

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.