What this guide helps you do
Set OBS output deliberately: server URL, stream key, bitrate, keyframe interval and an external playback test. OBS is reliable when the encoder profile matches the streaming platform. Connection failures usually come from the wrong ingest URL/key, network filtering or copying viewer URLs into the broadcast settings. Playback problems after connection are more often codec, bitrate, transcoding or HLS delivery issues. This guide is written for production-minded administrators and site owners: make a backup before material changes, keep credentials private, and prefer the controls supplied by your own hosting provider when its environment differs from a generic example.
Before you begin
Record the domain, server or station you are changing and the current working state. If the task touches DNS, SSH, firewall rules, databases, stream credentials or application configuration, make sure you have a recovery path first. Screens and menu names can vary between cPanel, AzuraCast, VDO Panel and Linux releases, so follow the purpose of each step rather than forcing an old screenshot onto a newer version.
Step 1: Copy the ingest server URL and stream key from your own VDO Panel channel. In OBS, open Settings → Stream and choose the custom service option if your panel does not provide a preset.
Copy the ingest server URL and stream key from your own VDO Panel channel. In OBS, open Settings → Stream and choose the custom service option if your panel does not provide a preset.
Step 2: Paste the server address and stream key separately. Do not append the key to a URL unless the panel explicitly displays it that way. Prefer RTMPS when the platform supplies it.
Paste the server address and stream key separately. Do not append the key to a URL unless the panel explicitly displays it that way. Prefer RTMPS when the platform supplies it.
Step 3: In Output settings, use H.264 video and AAC audio when that is what the service expects. Set bitrate within your plan limits and use a keyframe interval commonly supported by the platform, often two seconds.
In Output settings, use H.264 video and AAC audio when that is what the service expects. Set bitrate within your plan limits and use a keyframe interval commonly supported by the platform, often two seconds.
Step 4: Start Streaming and watch OBS for dropped frames or reconnect loops. At the same time, confirm the panel sees the source and receives roughly the bitrate you expect.
Start Streaming and watch OBS for dropped frames or reconnect loops. At the same time, confirm the panel sees the source and receives roughly the bitrate you expect.
Step 5: Test the public player independently. A green OBS indicator proves upload to the ingest server, not end-to-end delivery to viewers.
Test the public player independently. A green OBS indicator proves upload to the ingest server, not end-to-end delivery to viewers.
Verification checklist
The correct test checks both directions: OBS sends without sustained dropped frames, the panel reports the source, HLS/player output loads externally, audio stays in sync, and reconnect behaviour is understood. Always test from the user side as well as the administrator side. A control panel saying “active” is useful evidence, but it is not the same as an external browser, player or SSH client proving that the full path works.
Troubleshooting method
When the result is not what you expected, avoid changing several unrelated settings at once. Identify the last known-good point, collect the exact error message and determine which layer is failing: DNS, network, authentication, service process, application configuration, web/stream delivery or browser/player. Check timestamps and logs around the failure. If you need to escalate to hosting support, include the affected hostname or station, the time of the test, what you expected, what happened instead and the checks you already completed. Do not include passwords, API keys or private stream keys in a public ticket or screenshot.
Keep the system maintainable
Document the final configuration after it works. Note the important URLs, service names, backup locations, renewal/expiry dependencies and any change that would surprise another administrator. Revisit the setup after major platform upgrades because defaults, supported runtimes and interface labels evolve. A reliable environment is not one that was configured once; it is one whose current state is understood, monitored and recoverable.
Where to go next
Use the related guides below to expand the setup rather than solving the same problem from scratch. If the platform has outgrown shared hosting or you need managed implementation, the service recommendation at the bottom of this guide links to the most relevant hosting, streaming, development or optimisation option on this site.
Interface labels and supported versions can change. Use the controls and documentation supplied with your current hosting environment, and keep a backup or recovery path before material changes.