- Newest
- Most votes
- Most comments
Greetings!
Thanks for your question. It appears the preview player provides the same error message in multiple scenarios. I was able to replicate your issue by creating a new MediaPackage channel and endpoint without pushing any content to it.
The first things to check are to make sure you've configured your MediaLive channel properly to connect to MediaPackage, using the drop-down to select the appropriate channel in the MediaPackage Output Group settings. Once your MediaLive channel is up and running, confirm in the Health tab of the channel console that there are no alerts present that might indicate an issue with the workflow, that could prevent the stream from reaching MediaPackage. It might also be helpful to enable logging in MediaLive, see https://docs.aws.amazon.com/medialive/latest/ug/monitoring-with-logs.html to set that up. MediaPackage also offers operational metrics for the channel on its console, so confirming data is coming in there (and also pay attention to "Egress Request HTTP Status" to confirm the player is getting successful transfer requests).
If you have any questions about what you're seeing please follow-up here.
Regards, Steve
Relevant content
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
Hi! I solved the problem by re-creating my IAM role and granting them all access to MediaLive and MediaPackage. Thank you for the support!