What this guide helps you do
Work through ingest, codec, transcoder, HLS and browser delivery layers instead of restarting everything blindly. “Connected” narrows the problem but does not finish the diagnosis. It means the panel sees an incoming source. The failure can still sit between the encoder and transcoder, between transcoder and HLS packaging, at the web/CDN layer, or inside the browser because of HTTPS, codec or autoplay rules. 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: Confirm the encoder is actually sending video and audio, not an empty scene or muted track. Review OBS statistics for dropped frames and the configured codec/bitrate.
Confirm the encoder is actually sending video and audio, not an empty scene or muted track. Review OBS statistics for dropped frames and the configured codec/bitrate.
Step 2: Check the channel status and panel logs for transcoding or packaging errors. If a profile expects a codec or resolution the source does not provide, the ingest can appear connected while output fails.
Check the channel status and panel logs for transcoding or packaging errors. If a profile expects a codec or resolution the source does not provide, the ingest can appear connected while output fails.
Step 3: Open the direct viewer/HLS URL generated by the panel. Test it outside your website to separate platform playback from embed/CSS/JavaScript problems.
Open the direct viewer/HLS URL generated by the panel. Test it outside your website to separate platform playback from embed/CSS/JavaScript problems.
Step 4: Check browser developer tools for 404, 403, mixed-content, CORS or manifest/segment errors. These messages identify delivery problems much faster than restarting the source repeatedly.
Check browser developer tools for 404, 403, mixed-content, CORS or manifest/segment errors. These messages identify delivery problems much faster than restarting the source repeatedly.
Step 5: If direct HLS fails while ingest is healthy, collect timestamps, channel ID, encoder settings and log messages before escalating to the streaming host.
If direct HLS fails while ingest is healthy, collect timestamps, channel ID, encoder settings and log messages before escalating to the streaming host.
Verification checklist
Document which layer passes: encoder, ingest, transcoder, manifest, segments, player. Once the failing boundary is identified, change one thing at a time and repeat the external playback test. 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.