AzuraCast

Deploy AzuraCast, a free self-hosted web radio station and management suite for creating, managing, and broadcasting online radio stations without needing complex configuration.

1. Deploy AzuraCast

Estimated deployment time: 5–10 minutes

Follow the deployment instructions from the Get started section to configure the app, deploy it, and verify software installation.

For information on the app-specific configurations, see the Configuration options section.

Software included

Software installed on your Linode when deploying the app.

Package	Description
AzuraCast	An all-in-one web radio management suite. It includes Liquidsoap, Icecast, NGINX, PHP, and all radio streaming components.
MariaDB	An open source relational database for data storage.
Redis	An in-memory data structure store for caching and session management.
Docker	A container runtime for application deployment.
Docker Compose	A tool for defining and running multi-container Docker applications.

Base distribution and plan

Supported distribution: Ubuntu 24.04 LTS
Recommended plans: All plan types and sizes can be used.

Configuration options

Configure the required options to deploy your instance. For additional customization, add advanced options.

The table maps the Cloud Manager UI fields to their corresponding API/CLI keys (stackscript_data) required for automated deployments.

StackScript ID: 662118

UI field	API/CLI key	Description
Required options
Limited sudo user	`user_name`	Your preferred username for the limited sudo user, entered without any capital letters, spaces, or special characters. When adding a limited sudo user, the user is created with a strong generated password for your new Linode instance, and the account is assigned to the `sudo` group, which provides elevated permissions when running commands with the `sudo` prefix. Note: For easier and more secure access with the sudo user, add an account SSH key for the Cloud Manager user during deployment and select that user as an `authorized_user`. Their SSH pubkey will be assigned to both the root and limited sudo users.
Email address (for the Let's Encrypt SSL certificate)	`soa_email_address`	The email used for generating the Let's Encrypt SSL certificate and to receive notifications about the certificate renewal.
Administrator Email Address	`azuracast_admin_email`	Your administrator email address used to access the AzuraCast UI.
Advanced options
Disable root access over SSH	`disable_root`	Applies to a limited sudo user. To block the root user from logging in over SSH, select Yes. Defaults to No. Note: When you disable the root user from logging in over SSH and don't provide a valid Account SSH Key assigned to the `authorized_user`, you can still switch to the root user. To do that, log in as root via the Lish console and run `cat /home/$USERNAME/.credentials` to view the generated password for the limited sudo user.
Linode API token	`token_password`	Applies to a custom domain. The Linode API token if you want to use Linode's DNS Manager to manage DNS records for your custom domain. Follow Manage personal access tokens to get your token on your account with `Read/Write` access to `Domains`. If you provide the token along with the subdomain and domain, the installation attempts to create DNS records via the Linode API. If you don't provide the token, you need to manually configure your DNS records through your DNS provider and point them to the IP address of the new instance.
Subdomain	`subdomain`	Applies to a custom domain. The subdomain you want to use, like `blog` for `blog.example.com`. Use it only if you specify a Domain.
Domain	`domain`	Applies to a custom domain. The domain name you want to use, like `example.com`. Use it only if you specify a Linode API token.
Optional data exporter Add-ons	`add_ons`	An option to include add-ons for your deployment. Possible values are: none (default) node_exporter mysqld_exporter newrelic

Notes:

After the app deployment completes, the password for your limited sudo user is generated and stored in the .credentials file in the home directory, along with application-specific passwords. Log in to your instance as root through the Lish console or SSH, then run cat /home/$USERNAME/.credentials to view its contents.

You can automatically configure a custom domain (optional) during deployment. To do that:

First, configure your domain to use Linode’s name servers via your registrar. See Configure your domain's authoritative name servers for details.

Once you complete that, specify the Linode API token, subdomain, and domain for the app in Cloud Manager or via API/CLI/Terraform.

Use API, CLI, or Terraform

In addition to deploying the app to a new Linode instance via Cloud Manager, you can also use the Linode API, CLI, or Terraform. When running the operation, you need to provide the StackScript ID, supported Linux distribution, and app-specific fields along with the standard Linode deployment configurations.

Note: Generate a personal access token to authenticate your API, CLI, or Terraform requests.

curl --location 'https://api.linode.com/v4/linode/instances' \
    --header 'Content-Type: application/json' \
    --header 'Accept: application/json' \
    --header 'Authorization: Bearer abc123def456hij789klm' \
    --data-raw '{
        "region": "us-east",
        "type": "g6-standard-2",
        "image": "linode/ubuntu24.04",
        "label": "my-azuracast-one-click-app",
        "root_pass": "@C0mpl3x#P@ssw0rd",
        "stackscript_id": 662118,
        "stackscript_data": {
            "user_name": "jsmith",
            "soa_email_address": "jsmith@example.com",
            "azuracast_admin_email": "jsmith-admin@example.com"
        }
    }'

linode-cli linodes create \
    --region us-east \
    --type g6-standard-2 \
    --label my-azuracast-one-click-app \
    --image linode/ubuntu24.04 \
    --root_pass @C0mpl3x#P@ssw0rd \
    --stackscript_id 662118 \
    --stackscript_data '{"user_name":"jsmith" "soa_email_address":"jsmith@example.com", "azuracast_admin_email":"jsmith-admin@example.com"}'

resource "linode_instance" "my-linode" {
    region         = "us-east"
    type           = "g6-standard-2"
    label          = "my-azuracast-one-click-app"
    image          = "linode/ubuntu24.04"
    root_pass      = "@C0mpl3x#P@ssw0rd"
    stackscript_id = 662118
    stackscript_data = {
        "user_name"             = "jsmith"
        "soa_email_address"     = "jsmith@example.com"
        "azuracast_admin_email" = "jsmith-admin@example.com"
    }
}

2. Access AzuraCast

Once the app is deployed, you can access the AzuraCast UI. To do that:

Open your web browser and navigate to http://[domain]/admin, where [domain] is the custom domain you entered during deployment or your Linode Instance’s rDNS domain, for example, 192-0-2-1.ip.linodeusercontent.com. To learn more about viewing IP addresses and rDNS, see Manage IP addresses on a Linode.
Log in with your Super Administrator email address and password. This account has system-wide permissions and was set up during the installation when you entered your Administrator Email Address.

To get the credentials, log in to your instance as root through the Lish console or SSH, then run cat /home/$USERNAME/.credentials to view its contents.
Once logged in, on the Create a New Radio Station page, fill out the required fields to configure the station's settings, like its name, description, custom URL, and more.

If you've already set up a custom domain, you can use it with Linode DNS. See DNS Manager for more details.

Make sure the Public Pages and On-Demand Streaming options are enabled.
To adjust other station settings, go to the other tabs on the same page, like Broadcasting, AutoDJ, HLS, and more.
Click Create and Continue.
On the next page, Customize AzuraCast Settings, add more customizations, including the site base URL, security and privacy, and debugging settings.
Click Create and Continue again. This completes the station's configuration, and you can start broadcasting.
To manage the created station, click Manage Stations in the Dashboard section. This opens the station's dashboard that you can use to control your station, upload music, add DJs, take requests, and more.

Additional resources

For more information about the installed packages, see their official documentation.

📘
Note that we can't vouch for the accuracy or timeliness of externally hosted resources.