My feed isn't arriving

Your app says it’s broadcasting, but on Stream Keys the key is still on No signal.

First of all, look at what the Live signal card on your home dashboard says. No signal yet (nothing reaches us) is not the same as Rejected (it arrives, but we reject it) or Your signal dropped (it was arriving and it’s gone). What each one means: Your home dashboard.

Check this first

1. Copy the publish URL again with that key’s Publish button. If you changed the region or the protocol, the old URL is dead and your encoder is still broadcasting to the old place.
2. Did you hit Rotate? The previous key stops working that same instant. Copy the new URL and paste it in again.
3. Check that the protocol in the URL and the one in your app match. In Moblin, the SRTLA URL starts with srtla://, not with srt://.
4. On SRT and SRTLA, the streamid carries publish: in front of your key. read: is for watching the feed, not for sending it.
5. Look at the key’s status. If it says No subscription, it isn’t a network problem: the subscription isn’t active.
6. Drop your encoder’s bitrate below your plan’s cap and try again.
7. If you broadcast through the Cloud OBS, check whether your server is Stopped. It turns off on its own after a while unused, so it can be off without you having touched it: your feed does reach the key, but nothing goes out to your channel until you hit Turn on. See It turns off on its own.

Check the chain

The Broadcast chain on the home dashboard tells you which link the stream breaks at (signal, reading, OBS or destination) and links to the guide for that step. See Your home dashboard.

Common causes

What you see	What it means	What to do
Your app says “connected” and the key stays on No signal	You’re broadcasting to an old URL (different region or protocol)	Copy it again with Publish and paste it into the app
The encoder never connects and talks about authentication	The key was rotated, revoked, or the streamid is mistyped	Copy the whole URL again, without editing it by hand
Key on No subscription	That key’s subscription isn’t active	Check Billing and reactivate it
Key on Revoked	That key no longer exists for broadcasting	Use another active key or subscribe to one
Moblin won’t connect and the error looks like a password problem	The Big packets option is on	Turn it off; with it on the connection never gets established
Rejected · Your stream key does not match	Your app is broadcasting with a stream key that is almost yours: a character went missing, got added or changed when you copied it	Copy the publish URL again with Publish (or scan the QR code) and paste it without editing it
Rejected · You are using an inactive stream key	Your app is still broadcasting with a stream key that is no longer active	Copy the publish URL of an active key and paste it into your app
Rejected · Your subscription is not active	The signal arrives, but that key’s subscription is not active	Check Billing and reactivate it

It drops in the middle of the stream

If your signal was arriving and it’s gone, the dashboard tells you: the Live signal card switches to Your signal dropped and, if it doesn’t come back within a minute, the bell alerts you with that same title. If you stopped it yourself, there’s no alert: the card says Ended.

• It’s almost always the connection: coverage where you are or your phone’s network. Your app should reconnect on its own; if not, start the broadcast again.
• With SRTLA, use at least two connections (for example, mobile data and Wi-Fi). With just one, bonding has nothing to fall back on when it goes down.
• If it drops often, lower the bitrate. See The bitrate keeps bouncing or the picture stutters.
• A drop of under a minute doesn’t ring the bell: your stream carried on, and you’ll see it under Drops.

The typical mistake, encoder by encoder

• Moblin: Big packets always off. srtla:// URL for SRTLA, srt:// for SRT, and streamid with publish:. See Broadcasting with Moblin.
• BELABOX / belaUI: check that the connections you’re bonding actually have data; one of them dropping shouldn’t take the stream down, but all of them at once will. See BELABOX.
• Larix Broadcaster and IRL Pro: they run on RTMP or SRT. If you copied an SRTLA URL they won’t connect. See Larix and IRL Pro.
• Your OBS: on RTMP, the server and the key go in two different fields; don’t put the whole URL in the server field. See Broadcasting from your own OBS.
• Another encoder: only three things have to be right — the publish URL, the streamid when it’s SRT or SRTLA, and staying under the bitrate cap. See Another encoder.

Quick test

Broadcast for 30 seconds from another app on your phone with the same URL. If that one arrives, the problem is in your encoder’s setup; if it doesn’t either, it’s in the key or in the subscription.

Still not working

Open a ticket from Support in the dashboard or write to support@enhancedirl.com. Tell us what plan you’re on, what encoder you use, which protocol and the exact message you see in the app.

Dashboard states and the Index of dashboard messages can help too.