What this guide helps you do
Understand streamer accounts, source connection details, handoff behaviour and the safest way to test a live presenter. Live broadcasting introduces a second audio source into a station that may already be running AutoDJ. The goal is a controlled handoff: the presenter authenticates with a streamer account, AzuraCast accepts the source, the live programme takes priority, and automation resumes when the presenter disconnects. 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: Create a dedicated streamer or DJ account for the presenter instead of sharing administrator credentials. Give it an identifiable username and rotate the password when the presenter changes.
Create a dedicated streamer or DJ account for the presenter instead of sharing administrator credentials. Give it an identifiable username and rotate the password when the presenter changes.
Step 2: Open the station’s Streamers or connection instructions and copy the host, port, username/mount details and protocol shown for your exact configuration. Different source applications label these fields differently.
Open the station’s Streamers or connection instructions and copy the host, port, username/mount details and protocol shown for your exact configuration. Different source applications label these fields differently.
Step 3: Configure the encoder bitrate and codec to match the station’s accepted format. Extremely high bitrates do not improve a stream if the configured mount or audience connection cannot support them.
Configure the encoder bitrate and codec to match the station’s accepted format. Extremely high bitrates do not improve a stream if the configured mount or audience connection cannot support them.
Step 4: Test at low risk before a real programme. Watch the station dashboard as the source connects, verify the live indicator, listen from a separate device and then disconnect cleanly.
Test at low risk before a real programme. Watch the station dashboard as the source connects, verify the live indicator, listen from a separate device and then disconnect cleanly.
Step 5: Confirm AutoDJ resumes and metadata returns to normal. If connection fails, read the broadcasting logs and encoder error rather than randomly changing ports or firewall rules.
Confirm AutoDJ resumes and metadata returns to normal. If connection fails, read the broadcasting logs and encoder error rather than randomly changing ports or firewall rules.
Verification checklist
A successful test has unique presenter credentials, a stable source connection, audible live audio, correct or acceptable metadata, an external listener test and automatic return to scheduled programming after disconnect. 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.