What this guide helps you do
Configure a station, media, playlists, mount points and a first listening test without mixing up the web panel and stream endpoints. AzuraCast combines station management, AutoDJ, streaming services and public pages in one radio-focused platform. The exact labels can change between releases, but the operating model is consistent: create the station, confirm its frontend/backend choices, add media, build playlists, verify mount points, then test the public listening URL. 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 the station with a clear internal name and public-facing station name. Review timezone settings before schedules are created because timing mistakes are much easier to prevent than diagnose later.
Create the station with a clear internal name and public-facing station name. Review timezone settings before schedules are created because timing mistakes are much easier to prevent than diagnose later.
Step 2: Open the station profile and review the enabled broadcasting frontend and AutoDJ/backend options. Leave defaults in place unless you understand why a different Icecast/SHOUTcast or Liquidsoap configuration is needed.
Open the station profile and review the enabled broadcasting frontend and AutoDJ/backend options. Leave defaults in place unless you understand why a different Icecast/SHOUTcast or Liquidsoap configuration is needed.
Step 3: Upload a small set of known-good audio files, allow media processing to complete, then create a general rotation playlist and assign media to it.
Upload a small set of known-good audio files, allow media processing to complete, then create a general rotation playlist and assign media to it.
Step 4: Review Mount Points and the public page. A mount is part of the listening URL, while the source connection used by a live DJ is a different concept. Do not publish private source credentials.
Review Mount Points and the public page. A mount is part of the listening URL, while the source connection used by a live DJ is a different concept. Do not publish private source credentials.
Step 5: Start or restart the station only through supported panel controls, then listen from an external browser or player. Watch the Now Playing screen to confirm metadata advances as expected.
Start or restart the station only through supported panel controls, then listen from an external browser or player. Watch the Now Playing screen to confirm metadata advances as expected.
Verification checklist
Verify the station service is running, AutoDJ produces audio, the public mount URL is reachable over HTTPS where configured, metadata changes between tracks, and the public player works outside your administrator session. 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.