Facebook Live Not Connecting? How to Fix Stream Errors
Your encoder says it's streaming but Facebook shows nothing, or the connection fails outright. Here are the usual causes, from RTMPS and expired keys to Page roles and encoder settings, with fixes to work through in order.
About 6 min read
On this page
When Facebook Live won't connect, the cause is usually one of five things: a plain RTMP address instead of Facebook's RTMPS server, an expired or single-use stream key, a key from the wrong Page or live video, a Page role or restriction that blocks going live, or encoder settings outside Facebook's specs. Check them in that order.
Symptoms narrow it down. A connection that fails immediately points to the server address or network. A connection that works while nothing appears on Facebook points to the key, the Page or Live Producer. A stream that connects and then drops points to settings and bandwidth.
Key takeaways
- Use
rtmps://live-api-s.facebook.com:443/rtmp/; a plain RTMP address won't connect.- Single-use keys stop working once their live video ends, and resetting a key replaces the old one.
- Confirm you're streaming to the right Page with a role that allows going live.
- Keep bitrate, keyframes and audio within Facebook's specs so the stream stays up.
Fix 1: Point the encoder at Facebook's RTMPS server
If your encoder reports a failed connection within seconds, check the server address first. Facebook's ingest expects a secure connection, so it should read exactly rtmps://live-api-s.facebook.com:443/rtmp/, with the key in its own field.
- Old profiles. An encoder preset saved years ago may still use an
rtmp://address or omit the:443port. - Outdated software. Very old encoders and some hardware units don't support RTMPS at all; update the firmware or software.
- The device clock. A clock set far from the real time can make the secure handshake fail.
- The network. Office, school and venue networks that inspect encrypted traffic can break RTMPS. A quick test over a phone hotspot shows whether the network is to blame.
More on the secure protocol in RTMP vs RTMPS.
Fix 2: Replace an expired or mismatched stream key
If the encoder connects but Facebook never shows your video, suspect the key.
- Single-use keys belong to one live video. Once that video has ended or its setup was discarded, the key stops working, so copy a fresh one.
- Persistent keys can be reused for recurring streams, but resetting one invalidates the old value everywhere you pasted it. The option sits in Live Producer's stream setup, though wording can change.
- The wrong destination. A key copied from your personal profile, another Page or an old browser tab looks identical but sends video elsewhere.
- Copy errors. A trailing space or truncated key fails silently.
- Two sources on one key. A forgotten encoder or a teammate's test can take over the connection.
Our guide to finding your Facebook stream key shows where both key types appear.
Fix 3: Check the Page, your role and any restrictions
Facebook can accept the connection and still not publish if the account side isn't in order.
- Page role. You need access to the Page that includes creating content and going live. An admin can confirm roles in the Page settings or Meta's business tools.
- Restrictions. Pages and profiles with recent Community Standards violations can be temporarily blocked from going live. Look for notices in the Page's account status or quality information.
- Eligibility conditions. Meta has at times applied conditions to newer profiles and Pages before they can go live; the Facebook Help Center lists current requirements.
- Audience settings. If the live video's audience is limited, another account may not see a stream that's actually working.
Managing several Pages? Confirm the one selected in Live Producer is the one you meant; streaming to multiple Facebook Pages covers keeping keys organized.
Fix 4: Bring encoder settings inside Facebook's specs
If the stream connects and appears, then drops or shows poor health, the settings are probably too ambitious for the connection or outside what Facebook expects.
- Bitrate: well under your measured upload speed, for example 4,500–6,000 kbps for 1080p30.
- Keyframe interval: exactly 2 seconds, not automatic.
- Resolution and frame rate: 1080p or 720p at 30 fps covers most content; don't exceed Meta's current specs.
- Audio: include an AAC track at 44.1 or 48 kHz, since some ingest servers handle video-only streams poorly.
- Consistent sources: files played back to back should share resolution and frame rate.
The full breakdown is in Facebook Live settings for bitrate, resolution and keyframes. Drops that persist with sensible settings usually trace to the network; see why live streams drop.
Keeping a Facebook stream connected from the cloud with StreamHouse
Many of these failures start at the home or office end: mistyped server addresses, restrictive networks, sleeping laptops and settings that drift between files. For recorded content, StreamHouse removes those:
- No server address to get wrong. The Facebook destination only asks for your stream key; the RTMPS server is already set.
- No local network in the path. A playlist streams from the cloud to Facebook, so an office firewall or busy home connection doesn't matter.
- Consistent files. Uploads are prepared to one encode profile, keeping bitrate, keyframes and timestamps steady.
- Automatic reconnects if Facebook or the network hiccups mid-broadcast.
StreamHouse can't fix account-side problems: if Facebook rejects a key or restricts a Page, generate a new key or resolve the notice in Meta's tools, then paste the key back in. Set up Facebook Live streaming.
Frequently asked questions
Why is Facebook rejecting my stream key?
Most often the key is single-use and its live video has already ended, a persistent key was reset, or the key belongs to a different Page or profile. Copy a fresh key from Live Producer for the right Page, paste it without spaces, and make sure no other encoder uses it.
Does Facebook Live work with plain RTMP?
No. Facebook's live ingest expects RTMPS, the encrypted form of RTMP, at rtmps://live-api-s.facebook.com:443/rtmp/. If your encoder or hardware can't send RTMPS, update it, or send the stream through a cloud service that delivers it to Facebook securely.
Why does my stream connect but never appear on my Page?
Check that you're viewing the Page the key came from and that the live video's audience includes you. In many setups, Facebook shows a preview in Live Producer and waits for you to confirm going live, so look there before changing encoder settings.
Can a work or school network block Facebook Live?
Yes. Networks that filter or inspect encrypted traffic can break the RTMPS connection Facebook needs, even when browsing works normally. Test over a phone hotspot to confirm, then ask IT to allow outbound streaming, or run recorded content from a cloud service instead.
