Publish with OBS over WebRTC (WHIP) and play with WHEP

OBS Studio 30 and later can publish over WebRTC (WHIP) instead of RTMP. It is the lowest-latency way in, and it reaches our media server directly rather than through our website's CDN.

Your WHIP details

Open your stream channel → Technical Connection Details. You will find:

• WHIP publish URL — https://webrtc-node1.streamrepeater.com:8889/<your-stream-path>/whip
• WHIP bearer token — your stream path and stream key joined by a colon, <your-stream-path>:<your-stream-key>

The :8889 port is part of the address. Leave it in.

Set up OBS

1. Settings → Stream → Service: WHIP.
2. Server: paste the WHIP publish URL.
3. Bearer Token: paste the WHIP bearer token.
4. Settings → Output: set Keyframe Interval to 2 seconds, and use a baseline H.264 profile (or turn off B-frames). WebRTC cannot carry B-frames.
5. Press Start Streaming. Every destination on the channel goes live exactly as it does with RTMP.

The bearer token contains your stream key. Treat it like a password, and rotate the key from the channel page if it leaks.

Play with WHEP

Any WHEP player can read your stream with sub-second latency:

• WHEP playback URL — https://webrtc-node1.streamrepeater.com:8889/<your-stream-path>/whep
• WHEP bearer token — <your-stream-path>:<your-playback-key>. This is the read-only playback key, so it cannot publish.

To embed playback on your own site, use your channel's public watch page or embed. They already use WHEP and fall back to HLS.

If it will not connect

• Check that port 8889/TCP (signalling) and 8189/UDP and TCP (media) are allowed outbound on your network. Some office and campus networks block them. If they are blocked, use RTMP or SRT instead.
• OBS rejects a server it cannot verify. Always use the https:// URL exactly as shown.
• A 401 in the OBS log means the bearer token is wrong. Copy it again from the channel page, with no spaces.