StreamLive ProDestination not supported": WHIP and HLS destinations
Why StreamLive Pro answers "WHIP and HLS destinations are not supported yet", what to ask your service for instead, and how to add it as a Custom RTMP or SRT destination.
StreamLive Pro sends every broadcast out over RTMP, RTMPS or SRT only. When a WHIP or HLS address is saved as a destination, StreamLive Pro refuses it with the code DESTINATION_NOT_SUPPORTED and this message: "WHIP and HLS destinations are not supported yet: broadcasts go out only over RTMP, RTMPS or SRT. If your service gives you an RTMP or SRT address, add it with the Custom RTMP or Custom SRT card." The fix is on the side of the service you want to reach: ask it for an RTMP, RTMPS or SRT ingest address and a key, and add those instead.
Why WHIP and HLS cannot be destinations
Our servers do not send a separate stream to each network themselves. Each destination is added as an output of the broadcast's live input at Cloudflare Stream, and those outputs push RTMP, RTMPS or SRT. A WHIP or HLS destination would be saved and then receive nothing for the whole broadcast. Earlier, the Connections page offered Custom WHIP and Custom HLS cards that did exactly that, so both cards were removed and the server now refuses such destinations up front, instead of keeping one that silently stays dark.
There is also a difference in kind. HLS is a way of delivering video to viewers: players fetch it from a web server. It is not something an encoder pushes into. A link ending in .m3u8 is usually where people watch, not where you send.
WHIP as a way into StreamLive Pro is a different matter: the Encoder card has a WHIP tab in beta for the incoming stream (WHIP from OBS to StreamLive Pro: beta status and setup).
Symptom table
| Symptom | Likely cause | Fix |
|---|---|---|
| "WHIP and HLS destinations are not supported yet" | A WHIP or HLS address was sent as a destination, for example from an older dashboard tab, a saved link, or a script using our API | Get an RTMP, RTMPS or SRT address from the service and add it with Custom RTMP or Custom SRT |
| A WHIP or HLS destination saved long ago never receives anything | It was saved before the server started refusing them | Remove it from your destinations and add an RTMP or SRT one |
| "That address points to a private network" | The address is 127.0.0.1, 192.168.x.x or similar | Use the public server address your service gives you |
| "The URL must start with rtmp://, rtmps://, srt:// or https://" | The address has no scheme or a wrong one | Copy the full address again from the service |
| A plan-limit message when saving | A custom destination counts as an account in your plan | See When you reach a limit: what the message means |
Steps
- Ask the service for a push address. In its streaming settings, look for words like RTMP, RTMPS, SRT, "stream URL", "server" or "ingest", with a stream key. A WHIP endpoint or a .m3u8 link is not it.
- Open Connections. Go to Connections and find the Custom RTMP or Custom SRT card.
- Add the destination. Paste the server address and the stream key, and give it a name you will recognise.
- Remove any old WHIP or HLS destination. If one is still listed under Connections, use Disconnect on it, so it does not sit in your list doing nothing.
- Tick it for a test broadcast. Start a broadcast with the new destination and one other channel, and check on the service's side that the picture arrives.
The full walk-through for custom servers, with what to expect on the receiving side, is in Stream to a custom RTMP or SRT server. The difference between the three protocols that do work is in RTMP vs RTMPS vs SRT: which one to use and when.
When the service offers only WHIP or HLS
Then StreamLive Pro cannot deliver to it today. Some services offer an RTMP or SRT ingest only on certain plans or in an advanced setting, so check their help pages or ask their support. If you are the one running the receiving server, most media servers can accept RTMP or SRT alongside WHIP.
When to contact support
If you see the message while adding an RTMP or SRT address, or a destination you added keeps failing, write to [email protected]. Send the name of the service, the first part of the address (up to the host name, never the key), where you saw the message, and the date and time.
Frequently asked questions
What does "Destination not supported" mean in StreamLive Pro?
You tried to add a WHIP or HLS address as a destination. Broadcasts go out only over RTMP, RTMPS or SRT, so add an address of one of those kinds instead.
Can StreamLive Pro restream to a WHIP server?
Not today. Destinations are pushed over RTMP, RTMPS or SRT only. Ask the receiving service for an RTMP or SRT ingest address.
Can I add an HLS link as a destination?
No. HLS is how players fetch video from a web server, not an address an encoder pushes into. Look for the service's RTMP or SRT ingest instead.
Can I send WHIP into StreamLive Pro?
The Encoder card has a WHIP tab in beta for the incoming stream. We have not tested it with encoders; RTMPS or SRT are the reliable way in.
Where do I add a custom RTMP or SRT destination?
In Connections, on the Custom RTMP or Custom SRT card. Paste the server address and the stream key from your service.
Keep reading
Stream key or server URL not accepted in Connections? What each message means, from "The stream key does not look right" to a Vimeo URL refused, and how to fix it.
My Kick stream does not startKick stays offline while other networks go live? Usually Kick did not hand out the stream key, the sign-in expired, or the title and category are missing.
My Twitch stream does not startThe other networks go live but Twitch stays offline? Usually the Twitch sign-in expired or a pasted key was reset. How to read the message and fix it fast.
My Telegram live stream does not showThe live goes out but nothing appears in the Telegram channel or group? Usually Start streaming was not tapped in Telegram, or the key changed. How to fix it.
Want to try it? 7-day trial, no credit card.
Start free