Configure RTMP and RTMPS Output
Securely configure ingest URL, stream key, TLS, receiver format, and reconnect testing.
Written By 4ALL.LIVE
Last updated 12 days ago
Deliver a stable live stream to an RTMP-compatible platform while protecting destination credentials.
Best for: Streaming operators and platform administrators.
Before you start
Requires a valid RTMP/RTMPS ingest endpoint and stream key.
- Sign in with access to the correct organization, team, and event.
- Record event, language, workstation, app build, OS, drivers, destination, and operator.
- Commission with test pattern and a non-public receiver before program video.
- Obtain server URL/key and technical specification.
- Allow outbound access to the ingest host/port.
- Prepare a private test event or preview.
Configuration
- Add an RTMP target and name it for the destination.
- Enter the RTMP or RTMPS server URL; prefer RTMPS and keep TLS enabled where supported.
- Paste the key only in its protected field.
- Match H.264 profile, frame rate, bitrate, keyframe interval, and AAC requirements.
- Start with test pattern and captions.
- Confirm connecting becomes connected and validate destination preview.
- In rehearsal, test a brief interruption and confirm recovery.
- Stop, rotate any exposed key, and use program input only after validation.
What success looks like: The destination receives continuous video/audio and handles embedded captions as documented.
Check your setup
- RTMPS is used when supported.
- Destination health checks pass.
- Bitrate/keyframe cadence comply.
- Caption preservation is independently confirmed.
Troubleshooting
- Authentication fails: replace key and verify application/path.
- Connection refused: inspect scheme, DNS, firewall, and port.
- Unstable ingest: reduce bitrate and use wired networking.
- No captions: confirm platform ingest/transcode preserves CEA.
Security and operational notes
Important: Stream keys are credentials. Redact them from logs/screenshots and rotate after suspected exposure.