The RTMP server is a managed ingest and delivery endpoint for OBS, hardware encoders and compatible receivers. Explicit stream access is the safe default; allow-all is a deliberate public-ingest choice.
Antes de começar
A reachable TCP port.
One real publisher and, if needed, one receiver.
A planned stream key or host access policy.
Configurações explicadas
Explicamos apenas os controles úteis ao operador. Nomes internos e eventos de implementação são omitidos de propósito.
Server
Configure the RTMP listener.
- Name and active state
Operator label and lifecycle state.
- Port
TCP port used by RTMP publishers and receivers.
- Buffer length
RTMP buffering used by the server workflow.
Access control
Separate publishing and receiving permissions.
- Explicit access
Require a Stream object with a role and stream key or allowed host.
- Publisher role
Allows a client to send media.
- Receiver role
Allows a client to consume media.
- Allow all
Accepts connections without pre-created Stream access.
Use only when open guest publishing is an intentional product requirement.
Live analytics
Understand who is connected and whether media is flowing.
- Active streams
Current stream count on the server.
- Publishers and receivers
Current connection counts by role.
- Input and output bitrate
Media arriving from publishers and leaving toward receivers.
- Peer address and region
Connection IP and geolocation context shown for active peers.
- Connection duration
How long each publisher or receiver has remained connected.
Primeiro fluxo seguro
- 01
Create the RTMP server on an unused TCP port.
- 02
Choose explicit access unless guest publishing is a product requirement.
- 03
Create a publisher Stream with a unique key and connect OBS or the encoder.
- 04
If playback is needed, create a separate receiver Stream.
- 05
Verify publisher count, input bitrate, peer address/region and downstream playback.
Exemplos de fluxo
Controlled OBS contribution
A known producer sends one RTMP feed from OBS.
Como construir
- 1
Create the RTMP listener and a publisher-only Stream key.
- 2
Enter the RTMP URL and key in OBS and start streaming.
- 3
Confirm one publisher, non-zero input bitrate and the expected peer region.
- 4
Select the verified feed in Recording, Restreaming, Multiview or a Web player.
Guest RTMP publishers with generated stream keys
Your product intentionally lets external publishers create and use their own connection identity.
Como construir
- 1
Define whether guests receive explicit Stream records or an intentionally open server policy.
- 2
Keep publisher and receiver permissions separate.
- 3
Show each guest the correct URL/key without exposing other credentials.
- 4
Monitor connection identity, address, region, duration and bitrate during the session.
Validar o resultado
- The intended publisher appears with non-zero input bitrate.
- Publisher and receiver counts match the real clients.
- Peer address, region and connection duration appear for the active session.
- An unauthorized key or host is rejected under explicit access.
Solução de problemas
OBS cannot publish
Verifique- Check TCP firewall and port.
- Match RTMP URL, stream key and publisher role.
- Confirm the server is active.
Test one explicit publisher before adding receivers or downstream processing.
Publisher is connected but output bitrate is zero
Verifique- Confirm OBS is sending video/audio.
- Check input bitrate first.
- Verify a receiver or downstream module is connected.
Repair the first zero-bitrate boundary rather than changing access policy.