Skip to main content
Streaming from dfine.io Studio? See Streaming from dfine.io Studio. This page is for any other RTMPS encoder.

​
The encoder cannot connect

Check these first. Most problems are a wrong value in the encoder.
Copy it again from the slot’s Ingest tab. It must start with rtmps://, because every stream is encrypted. Plain RTMP does not work.
The stream key publishes the signal. The access key is for viewers who log in to watch.
The credentials are wrong, the share is turned off, or the project is archived. Copy URL and key again from the app and make sure the project is active.
The encoder reached a server your account may not use, for example a TISAX or on-premises server that is not assigned to you. Use the default ingest URL from the app, or ask your administrator to assign the server.
Another encoder is already live on this slot. Stop it, wait a moment and start again. An administrator can reset a stuck slot.
With a fixed IP setup, the encoder’s IP and gateway must be in the same range as your workstation.

​
The stream was paused or blocked

You see “Your stream went over your plan’s bitrate, so we paused it. Lower your encoder’s bitrate, then unlock and restart it in your dashboard.” and a red Blocked badge. Lower the bitrate below the Max bitrate in the Ingest tab, click Unblock in the dashboard and restart the encoder.
“Your stream reached its run-time limit, so we paused it…” stops a forgotten stream. Click Unblock in the dashboard and restart the encoder.
“You have reached the limit … your account will need to be upgraded” means your plan runs no more streams at the same time. End one, or upgrade.

​
Viewers get no picture

Viewers see “Please set your encoder to the Main or Constrained Baseline H.264 profile, then restart the stream.” Set the profile to Main and restart. All values: Encoder values.
Check the encoder for CBR and a keyframe every second, see Encoder values.

Still stuck?

Write to support@dfine.io and we will help you out.