OBS setup guide
Add a custom RTMP destination from OBS
A custom destination gives you an RTMP or RTMPS server address and a separate stream key. RelayHalo forwards your OBS stream there as encoded, so check the format and test privately before announcing a live.
Get the two values from the platform
In the platform’s live or encoder settings, copy the server URL and the stream key separately. The URL names the ingest server and usually starts with rtmp:// or rtmps://. The key identifies your stream and works like a password: never put it in a ticket, a screenshot or an export.
What goes in each field
| Server URL | Stream key |
|---|---|
Example: rtmps://ingest.example/liveCopy the address exactly, with its scheme and any path or port. Use RTMPS when the platform offers it. |
Example: a private value given by the platform Paste only the key itself. If the platform changes it, update the destination before your next live. |
Connect OBS through RelayHalo
- Create your free RelayHalo account and add a custom destination with the server URL and key you collected. No plan is needed to set up or test.
- For your first real live, create a private or unlisted event on the platform when possible: going live can open a public event on some platforms.
- Copy your RelayHalo server and stream key into OBS under Settings → Stream → Custom. Your OBS key is not the platform key.
- Start streaming in OBS: a private signal test opens by itself in your studio, without sending anything to the platform. Then click “Go live” and watch that platform’s status. A connected output confirms data delivery, not that viewers can see the live.
Check the shared format
RelayHalo does not transcode: every platform receives the same encoded OBS stream. H.264, AAC, CBR and 2-second keyframes are good starting points, but each platform’s current rules come first. If one platform rejects a format, adjust OBS or use a destination with compatible requirements.
If the destination fails
| What you see | What to do |
|---|---|
| Secure connection or connection error | Check rtmp:// versus rtmps://, the host, the port and that the server is reachable from the internet. |
| Stream rejected | Copy a fresh key and check that the account is allowed to stream to that server. |
| Connected but no video on the platform | Check the live’s visibility and the platform’s current codec, bitrate and keyframe rules. A connection alone does not prove playback. |
| Only one output keeps retrying | Read that platform’s events, fix the cause, then retry that output; the others keep streaming. |
Continue with a private test
Keep the live private until OBS reaches RelayHalo and the platform shows the expected preview. Then make it public with the platform’s own controls.
Official documentation
Questions
Should I use RTMP or RTMPS?
RTMPS when the platform offers it: it encrypts the stream and the key on the way. Copy the address exactly, with its scheme and port.
What if my stream key leaks?
Reset it on the platform right away and paste the new key into the destination. Anyone with the key can stream to your channel.