
You want your own internet radio station on a rented server: music around the clock, live DJs when they are on air, and a stream URL your listeners can open anywhere. AzuraCast is the usual answer, because it bundles the AutoDJ, the streaming server and a web panel into one install. This guide covers what the VPS really needs, the install commands from AzuraCast's own docs, the ports to open, how many listeners your monthly transfer carries, live DJs, backups and the music licences you need.
Quick answer: AzuraCast is free, open-source radio software that installs on a Linux VPS with Docker in five shell commands. Its docs set the minimum at 2 GB RAM and 20 GB disk and recommend 4 CPU cores, 4 GB RAM and 40 GB disk. Bandwidth decides your listener count: 100 listeners at 128 kbps use 12.8 Mbps, about 4.1 TB a month around the clock, so a plan with 10 TB of monthly transfer carries about 241 listeners at once, all month. Playing other people's music on a public stream needs licences from the music rights societies in your country.
What AzuraCast Is
AzuraCast is a web radio management suite. According to its station management docs, every station has two parts that AzuraCast starts and keeps running for you:
| Part | Software | Job |
|---|---|---|
| AutoDJ ("broadcasting backend") | Liquidsoap | Mixes your playlists and live DJ input into one signal and encodes it into each stream format |
| Broadcasting frontend | Icecast, Shoutcast or RSAS | Serves that signal to your listeners; built for very many connections at low load |
Icecast works out of the box. Shoutcast and RSAS are not shipped with AzuraCast: you download the Linux binary from the vendor and upload it on the "Install Shoutcast" or "Install RSAS" page in the admin panel. If you are still choosing between the two servers, read our Icecast vs Shoutcast comparison.
Around those two parts you get a web panel for media, playlists, DJ accounts and listener statistics, plus a JSON REST API for now-playing data, song history, song requests and starting or stopping stations. AzuraCast's install page says it is "completely free for you to install and use, even for commercial purposes."
VPS Requirements
These figures come straight from AzuraCast's requirements page:
| Minimum | Recommended | |
|---|---|---|
| CPU | 64-bit x86 (amd64) or ARM64 | 4 CPU cores |
| RAM | 2 GB | 4 GB |
| Disk | 20 GB or more | 40 GB or more |
| Other | Can run Docker; sudo, curl and git installed | Can run Docker |
The docs call the minimum "the barest of minimum" with no guarantee it runs perfectly, and say the recommended spec runs "a few stations with ease", aimed at hobby use with 5 to 10 stations. So a 1 GB VPS is below what AzuraCast supports, and a 2 GB one leaves no headroom.
On an internet radio VPS, three resources decide the size you need:
| Resource | What uses it (per AzuraCast's docs) |
|---|---|
| CPU | Each mount point, remote relay with AutoDJ and HLS stream is one more constant encode. ReplayGain calculated on the fly, AutoCue and audio post-processing (Stereo Tool most, then master_me, then basic compression) add more. |
| Disk | Your music library, recorded live shows, backups and playback history. Setting "Days of Playback History to Keep" to a large value or "Indefinitely" fills the disk quickly. |
| Monthly transfer | Listeners multiplied by bitrate, worked out in the next section. |
Operating system: the requirements page tells you to start from a fresh minimal install without Docker or Docker Compose already on it, and strongly recommends Ubuntu or Debian LTS. Its version list is old (Ubuntu 22.04 LTS is the newest named), so pick the newest of those your host offers. The docs also warn that OpenVZ and LXC containers sometimes cannot run Docker; a KVM virtual server avoids that. Every Space-Node VPS plan is KVM in an EU data center; Standard VPS-S (3 vCores, 4 GB RAM, 60 GB NVMe, 10 TB transfer) meets the recommended RAM and disk, and VPS-M (4 vCores, 8 GB RAM, 80 GB NVMe) the full recommended spec.
Bandwidth: How Many Listeners a VPS Carries
Every listener downloads the stream at its bitrate for as long as they listen. The sum:
- 128 kbps is 16,000 bytes per second.
- A 30 day month has 2,592,000 seconds.
- One listener, connected the whole month: 16,000 x 2,592,000 = 41.5 GB.
| Bitrate | Transfer per listener per month (non-stop) | 100 listeners, non-stop | Listeners a 10 TB plan carries non-stop | Listeners a 20 TB plan carries non-stop |
|---|---|---|---|---|
| 64 kbps | 20.7 GB | 2.1 TB | 482 | 964 |
| 96 kbps | 31.1 GB | 3.1 TB | 321 | 643 |
| 128 kbps | 41.5 GB | 4.1 TB | 241 | 482 |
| 192 kbps | 62.2 GB | 6.2 TB | 160 | 321 |
| 320 kbps | 103.7 GB | 10.4 TB | 96 | 192 |
Read the listener columns as the average number of people connected over the whole month, not your peak. A station with 500 listeners in the evening and 50 at night averages far fewer than 500. Leave a margin for protocol overhead, the web panel and DJ uploads. The port speed is rarely the limit: a 1 Gbps port fits about 7,800 listeners at 128 kbps at the same moment, far more than 10 TB a month can feed around the clock.
Every extra mount point at a different bitrate splits listeners between streams; it does not add transfer by itself, but it adds CPU.
Step 1: Prepare Your VPS
Connect as root or as a user with sudo:
ssh root@YOUR_VPS_IP
apt update && apt upgrade -y
apt install -y sudo curl git
Most distributions already include sudo, curl and git; the last line makes sure. Do not install Docker yourself: the AzuraCast installer installs matching versions of Docker and Docker Compose.
Step 2: Install AzuraCast
These are the commands from AzuraCast's Docker install guide, using the recommended directory:
mkdir -p /var/azuracast
cd /var/azuracast
curl -fsSL https://raw.githubusercontent.com/AzuraCast/AzuraCast/main/docker.sh > docker.sh
chmod a+x docker.sh
./docker.sh install
The installer asks a few questions on screen:
- Release channel: the script asks "Your current release channel is 'Rolling Release'. Switch to 'Stable' release channel?" The default answer is No, which keeps Rolling Release; answer Y if you want the Stable channel.
- Customize settings: answer Yes if you need different ports, for example because port 80 or 443 is taken.
If your VPS image shipped an old Docker version and the install fails, the guide's fix is:
cd /var/azuracast
./docker.sh install-docker
./docker.sh install-docker-compose
./docker.sh install
Step 3: First Login and Your First Station
When the installer finishes, open http://YOUR_VPS_IP in your browser. On that first visit you create your super administrator account and finish the initial setup.
Create a station and pick:
- Name and URL stub: the stub (for example
myradio) becomes part of your stream URLs. - Broadcasting frontend: Icecast, unless you have uploaded a Shoutcast or RSAS binary.
- AutoDJ: Liquidsoap.
The station's Profile page then shows its now-playing status, the AutoDJ and frontend status, and a list of its mount points.
Step 4: Mount Points and Stream URLs
A mount point is one stream of your station in one format and bitrate. Per the mount point docs, the default listen URL has this form:
https://your-domain/listen/<station URL stub>/<mount point>
For a station with the stub myradio and a mount named radio.mp3, that is https://radio.example.com/listen/myradio/radio.mp3. Two format notes from the same page:
- iOS users cannot play Ogg streams in Safari, so keep an MP3 mount.
- Ogg Opus and FLAC streams do not send the current song, artist or title to Icecast.
Every mount point costs a small, steady amount of CPU, so add a second bitrate only when listeners need it.
Step 5: Upload Your Music
Web uploader: in the station's Media Manager, select files or drag them in.
SFTP for big libraries: AzuraCast's Docker install includes an SFTP server on port 2022. Under the station's Media menu, open SFTP Users, create a user and copy the connection details into FileZilla, WinSCP or Cyberduck. To use another port, set AZURACAST_SFTP_PORT=2022 (with your value) in the .env file in /var/azuracast, not in azuracast.env.
One rule catches many new stations: a file only plays once it is in at least one playlist. You can assign a whole folder to a playlist with "Set Playlists" in the Media Manager, and new files in that folder join the playlist automatically.
Step 6: Set Up the AutoDJ
Playlists decide what the AutoDJ plays. Any playlist type can be limited to time blocks or a date range, which is how you run scheduled shows. When two playlists can both play, the higher priority wins. The defaults:
| Item | Default priority |
|---|---|
| Song requests | Always top |
| Once per X hours, scheduled | 7 |
| Once per X hours, unscheduled | 6 |
| Once per X songs, scheduled | 5 |
| Once per X songs, unscheduled | 4 |
| Once per X minutes, scheduled | 3 |
| Once per X minutes, unscheduled | 2 |
| General rotation | 0 |
A simple station can start with three playlists: a general rotation with the main library, a "once per X songs" playlist with station IDs and jingles, and scheduled playlists for recorded shows. Versions released after 1 September 2024 let you set priorities by hand, including the priority of listener requests.
Step 7: Enable Live DJs
Make sure "Enable Streamers" is turned on for the station, then create an account per DJ on the Streamers/DJ Accounts page. That page also shows the connection information each DJ needs: server, port and mount name. DJs connect to Liquidsoap, not to Icecast, so the AutoDJ hands over to the live show and back without a gap. The streamers docs say Liquidsoap accepts any software that can stream to an Icecast or Shoutcast server.
Settings from the streaming software docs:
| Software | Settings |
|---|---|
| BUTT (free) | Type Icecast; Address, Port, user and password from the DJ page; mountpoint from "Mount Name", usually / |
| Mixxx (free) | "Icecast 2" mode; set the format to Ogg Vorbis, because Mixxx ships without the LAME MP3 encoder |
| SAM Cast | MP3 (LAME_ENC) encoder, server type Icecast, then Icecast 2, details from "Icecast Clients" on the DJ page |
| RadioBOSS | Icecast mode; live broadcasting needs the Standard or Advanced edition |
If your domain runs through Cloudflare, it blocks the DJ ports: give DJs the server's IP address instead of the domain. You can also record live shows in the station profile and download them per DJ.
Step 8: Domain and HTTPS
Point an A record (and an AAAA record if you use IPv6) for a subdomain such as radio.example.com at your VPS. Then, per the SSL docs:
- Open System Administration, then System Settings, then the Services tab.
- Fill in the LetsEncrypt fields and save. The certificate is created within minutes, or straight away with "Create/Renew Certificate".
Let's Encrypt needs a domain (an IP address does not work) and AzuraCast on the default ports 80 and 443. Renewal is automatic. Once HTTPS works, turn on "Always Use HTTPS" in the Security & Privacy tab. If you ever lose HTTPS with that on, switch it off from SSH:
cd /var/azuracast
bash docker.sh cli azuracast:settings:set always_use_ssl 0
If listeners on an HTTPS page still get no audio, enable "Use Web Proxy for Radio" in System Settings, so the streams are served through ports 80 and 443.
Behind Cloudflare
The Cloudflare docs add three rules: enable "Use Web Proxy for Radio" (Cloudflare does not forward the station ports), add Page Rules with Cache Level "Bypass" for /radio/*, /listen/* and /hls/*, and turn off Rocket Loader.
Step 9: Get Listed in Directories
From AzuraCast's promotion docs:
- TuneIn AIR, Radio.de and GetMeRadio: contact the directory for API access first, then add a Web Hook in the station sidebar to send now-playing updates.
- Xiph Icecast directory (dir.xiph.org) and internet-radio.com: turn on "Enable Advanced Settings" in System Settings, then add a
<directory>block to the station's Custom Configuration (Profile, Edit Profile, Broadcasting tab). Icecast only. For Xiph:
<directory>
<yp-url-timeout>15</yp-url-timeout>
<yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url>
</directory>
- radio-browser.info: add custom
icy-HTTP headers in each mount point's advanced configuration; the station-wide field does not work for this.
internet-radio.com needs your description and profile fields at 255 characters or fewer.
Embed the Player and Use the API
A plain HTML5 player works with any MP3 mount:
<audio controls>
<source src="https://radio.example.com/listen/myradio/radio.mp3" type="audio/mpeg">
</audio>
For your own site or app, the Now Playing API returns the now-playing data and recent song history per station at https://radio.example.com/api/nowplaying/myradio. Listeners can also open the stream URL directly in VLC or most media players.
Multiple Stations on One Server
You can run any number of stations, limited by the server's resources. By default the Docker install only opens radio ports 8000 to 8500, which covers 50 stations, and AzuraCast assigns each new station free ports from that range. For more, the Docker docs add the range in /var/azuracast/docker-compose.override.yml:
services:
web:
ports:
- "8500-8999:8500-8999"
Then set AUTO_ASSIGN_PORT_MIN and AUTO_ASSIGN_PORT_MAX in azuracast.env and restart with docker-compose down and docker-compose up -d. Remember the recommended 4 cores and 4 GB are sized for 5 to 10 hobby stations.
Keep CPU and Disk Use Down
To see what your station uses, open the Administration page: its Server Status section shows CPU load, memory and disk space. To check the stream from outside, request the stream URL or the station's Now Playing API (see above) from another machine on a schedule; the API also reports the current listener count and whether a live DJ is connected.
AzuraCast's optimizing page lists the cheapest wins:
- Turn off ReplayGain in the AutoDJ tab, or tag your files beforehand with loudgain.
- Turn off audio post-processing on small servers.
- Turn off AutoCue or precompute its values if a station with long tracks or many playlists stalls at startup.
- Remove mount points nobody uses.
- Lower "Days of Playback History to Keep".
- Move media or backups to remote storage (S3-compatible or Dropbox) if the disk is small.
- Disable Docker's userland proxy: put
"userland-proxy": falsein/etc/docker/daemon.jsonand restart the server. The docs say it can use huge amounts of resources because of the many ports AzuraCast forwards.
Backups and Updates
Web panel: System Administration has a Backup page for scheduled automatic backups, one-off backups and downloads. Backups from the panel do not interrupt your broadcast.
Command line, per the backup docs:
cd /var/azuracast
./docker.sh backup /root/azuracast-backup.zip
./docker.sh backup /root/azuracast-config.tar.gz --exclude-media
./docker.sh restore /root/azuracast-backup.zip
--exclude-media leaves the music out, which keeps the file small; then back up your music somewhere else. A restore replaces the current database and media, so test it on a spare server. Keep at least one copy off the VPS: on Space-Node VPS plans backups are not part of the plan price (they are available on request through a ticket), so set up AzuraCast's own backups to remote storage.
Updates take your stations briefly offline, so back up first and pick a quiet hour (update docs):
cd /var/azuracast
./docker.sh update-self
./docker.sh update
Firewall
ufw allow 22/tcp
ufw enable
Allow SSH before you enable UFW, or you lock yourself out. AzuraCast uses 80 and 443 (web panel, HTTPS, proxied streams), the station port range 8000 to 8500 (listeners and DJs connect to the ports each station shows) and 2022 (SFTP). Note what Docker's own docs say: ports that Docker publishes are routed "before the firewall rules can be applied", so UFW does not block them. UFW still guards everything else on the host, such as SSH.
Troubleshooting: The Errors You Will Actually See
| Message or symptom | Cause and fix (from AzuraCast's troubleshooting and Docker docs) |
|---|---|
bind: address already in use | Another program, often Apache or nginx, holds port 80 or 443. Find it with netstat -tulpn, stop it or move it, or change AzuraCast's ports. Port 8080 is left free on purpose for such software. |
Client version x.xx is too old/new | Docker and Docker Compose versions do not match. Run ./docker.sh update-self, ./docker.sh install-docker and ./docker.sh install-docker-compose. |
Invalid interpolation format | Docker Compose is too old. Run ./docker.sh update-self and ./docker.sh install-docker-compose. |
We must catchup x.xx seconds in the Liquidsoap log, audio crackles | The AutoDJ lacks CPU. Turn off High CPU features (AutoCue, master_me), cut mount points, relays or HLS streams, or move to a bigger server. |
| AutoDJ plays nothing | The files are not in any playlist. |
Allowed memory size of 268435456 bytes exhausted | Raise PHP_MEMORY_LIMIT (for example to 512M) in azuracast.env, then docker-compose down and docker-compose up -d. |
Logs: System Administration has System Logs, and each station has a Logs page for Icecast, Shoutcast and Liquidsoap. From SSH, docker-compose logs -f web in /var/azuracast shows the container log, ./docker.sh cli cache:clear clears stale caches and ./docker.sh cli azuracast:radio:restart restarts every station (this disconnects your listeners).
FAQ
Is AzuraCast really free?
Yes. AzuraCast's install page says it is "completely free for you to install and use, even for commercial purposes." The project runs on donations. You pay for the server, an optional domain and your music licences.
How many listeners can my internet radio VPS handle?
Usually your monthly transfer decides it, not the CPU. One listener at 128 kbps uses 41.5 GB in a 30 day month of non-stop listening, so a 10 TB plan carries about 241 listeners connected around the clock, and a 20 TB plan about 482. At 64 kbps those numbers double. Your peak can be higher than that average, because few stations keep their evening audience all night.
Can AzuraCast run on a 1 GB VPS?
No. AzuraCast's documented minimum is 2 GB of RAM and 20 GB of disk, and the docs say even that comes with no guarantee. For several stations or CPU-heavy features, use the recommended 4 cores, 4 GB RAM and 40 GB disk. If you only need one stream on a very small server, a plain Icecast and Liquidsoap setup without the web panel is lighter: see our Icecast and Liquidsoap guide.
Do I need a music licence for internet radio?
Yes, as soon as you stream music you did not make or license yourself to the public. Your VPS host does not license music, and AzuraCast's requirements page says it is not liable for music licences and royalties and that the rules differ per country. In the Netherlands, for example, the rights are split between two collecting bodies: BumaStemra for composers, lyricists and publishers (authors' rights) and Sena for performers and producers (neighbouring rights). Sena's radio licences page lists "Online Radio" as its own licence category, says radio stations pay both Sena and BumaStemra, and says local or non-commercial stations and short jingles with music need a licence too. Our Dutch guide on webradio licences from BumaStemra and Sena (in Dutch) lists their current tariffs. Ask the societies in your country which licence covers webcasting; this is not legal advice. Using only music you own, or royalty-free music for 24/7 streams whose licence allows public streaming, avoids most of this.
Can I schedule pre-recorded shows?
Yes. Upload the show, put it in a playlist and limit that playlist to a time block, for example Monday 20:00 to 22:00. Any playlist type can be scheduled. If other playlists can also play in that slot, give the show's playlist a higher priority, which versions released after 1 September 2024 let you set by hand.
Which DJ software works with AzuraCast?
Anything that can stream to an Icecast or Shoutcast server, because DJs connect to Liquidsoap, which accepts both. AzuraCast's docs give setup steps for Mixxx, BUTT, BUTTM, SAM Cast, RadioBOSS, PlayIt Live and Rocket Broadcaster. Use the server, port and mount name from your station's Streamers/DJ Accounts page.
Related Guides
- 24/7 Music Streaming Server
- Icecast vs Shoutcast Comparison
- Icecast and Liquidsoap on a VPS
- Royalty-Free Music for 24/7 Streams
- 24/7 Live Stream VPS Setup
- Radio with video visuals through OBS on YouTube or Twitch: streaming VPS plans
Sources
All opened on 4 November 2026:
- AzuraCast: Requirements, Install AzuraCast, Install with Docker, Docker, Updates, SSL and Let's Encrypt, Cloudflare, Backup and Restore, Station Management, Mount Points, Playlists, Media Management, SFTP Server, Streamers and DJs, Streaming Software, Promoting Your Station, Optimizing, Troubleshooting, Logs, Storage Locations, APIs, Now Playing Data, Command-Line Interface
- AzuraCast on GitHub: docker.sh (installer prompts), sample.env
- Docker: Packet filtering and firewalls
- Sena: Radiolicenties