Support Knowledge base Misc

Troubleshooting Methodology - Main feed

You have some trouble to publish your main feed?

Troubleshooting Methodology - Main feed

This little guide is here to help you to troubleshoot using the tools we provide.

DO NOT PANIC: Technical problems arrive and panicking won’t help. You must remain calm to troubleshoot effectively.

Stopping everything won’t help because you won’t understand what went wrong and the root cause: 99.9% of the reported issues are human’s mistakes. 

  1. Workflow

Ref 1: local encoder

Ref 2: local internet connection or network for producer

Ref 3: easylive.io platform

Ref 4: local internet connection or network for receiver

Ref 5: RTMP pulled into local encoder

2. Prerequisite

A - Activate flash on your local browser to make sure you can access all monitoring tools provided by easylive.io.

In Chrome, go to chrome://settings/content/flash then, click in the section “Allow” on  “Add” and copy paste the following url: https://www.goeasy.live:443

B - Download VLC player: you can download it here

3. Viewers are complaining about the stream

Being the last step of the process, every single step before could be the cause of the issue. So the idea here is to isolate every step one after the other and isolate the root cause.

A - Access easylive.io control Room and click go to the "Publish" section and then click on “RTMP” button.

You can now look at the quality we are currently delivering.

⇒ Is the quality of the live feed as expected?

Yes ⇒ contact support@easylive.io and report the issue.

No ⇒ go to next step

B - Open the monitoring (left vertical bar)

  • Select the right live source and click on “view”
  • Preview your feed

⇒ Is the quality of the live feed as expected?

Yes ⇒ contact support@easylive.io and report the issue.

No ⇒ go to next step

C - Bitrate variations

Close the player and scroll down to the bitrate graphic. easylive.io provides CBR (Constant Bitrate) to guarantee the delivery toward your publishers.

Too much variations implies an issue with the live source you are ingesting.

Profiles you might get: