<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Lurcast</title>
    <description>The latest articles on DEV Community by Lurcast (@lurcast).</description>
    <link>https://dev.to/lurcast</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4254525%2F708b068c-b674-4c43-b590-c52a869f0f6a.png</url>
      <title>DEV Community: Lurcast</title>
      <link>https://dev.to/lurcast</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/lurcast"/>
    <language>en</language>
    <item>
      <title>Build a Raspberry Pi Icecast Server That Survives</title>
      <dc:creator>Lurcast</dc:creator>
      <pubDate>Thu, 19 Nov 2026 21:45:36 +0000</pubDate>
      <link>https://dev.to/lurcast/build-a-raspberry-pi-icecast-server-that-survives-2f3</link>
      <guid>https://dev.to/lurcast/build-a-raspberry-pi-icecast-server-that-survives-2f3</guid>
      <description>&lt;p&gt;&lt;em&gt;This article was first published on the &lt;a href="https://www.lurcast.com/blog/raspberry-pi-icecast-server-setup" rel="noopener noreferrer"&gt;Lurcast blog&lt;/a&gt;. It was written with AI assistance.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Key takeaways
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;A Pi 4 comfortably serves a single 128 kbps Icecast mount to a few hundred listeners, but upstream home bandwidth is usually the real ceiling.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Change the default source password (hackme) in icecast.xml before forwarding port 8000, and set hostname to your public domain.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Boot from a USB SSD or log to tmpfs, because 24/7 Icecast and Liquidsoap writes wear out SD cards.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Use systemd Restart=always and network-online ordering for source clients so a power cut causes seconds of dead air, not hours.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;When you outgrow one station per Pi, move mounts to a VPS; source clients, fallbacks and stats scripts carry over unchanged.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A Raspberry Pi Icecast server works well for small stations: a Pi 4 can serve a few hundred listeners on low bitrates, costs pennies a day to run, and takes about an hour to set up. This guide covers the install, source clients, port forwarding, and the honest limits: SD card wear, thermals, and when to move to a VPS.&lt;/p&gt;

&lt;h2&gt;
  
  
  What do you need before setting up Icecast on a Raspberry Pi?
&lt;/h2&gt;

&lt;p&gt;You need a Pi that can sustain encoding for days, storage that survives 24/7 writes, and a network setup that keeps the server reachable. Get these right before touching icecast.xml, because most dead-air problems on a Pi trace back to hardware or power, not the Icecast2 config (see the &lt;a href="https://icecast.org/docs/" rel="noopener noreferrer"&gt;official Icecast documentation&lt;/a&gt; for mount and configuration reference).&lt;/p&gt;

&lt;h3&gt;
  
  
  Which Pi model makes sense
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Model&lt;/th&gt;
&lt;th&gt;Verdict for Icecast&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Pi 3 B+&lt;/td&gt;
&lt;td&gt;Works for one mount, low bitrate, few listener slots&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pi 4 (2–4GB)&lt;/td&gt;
&lt;td&gt;Comfortable for one station plus AutoDJ&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pi 5&lt;/td&gt;
&lt;td&gt;Headroom for multiple mounts and fallback streams&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Older models like the Pi Zero 2 can serve a single low-bitrate mount, but sustained encoding plus listener traffic leaves little margin.&lt;/p&gt;

&lt;h3&gt;
  
  
  SD card vs SSD boot
&lt;/h3&gt;

&lt;p&gt;SD cards wear out under constant logging and AutoDJ reads. Boot from a USB SSD, or at minimum point Icecast's logs at a tmpfs mount and log to RAM. If you stay on SD, use a high-endurance card and expect to replace it.&lt;/p&gt;

&lt;h3&gt;
  
  
  Static local IP and network prep
&lt;/h3&gt;

&lt;p&gt;Set a static IP via DHCP reservation on your router so port forwarding rules survive reboots. You will need port 8000 forwarded later, and a stable hostname makes WHMCS-style provisioning or player URLs predictable. Note that if you later outgrow the Pi, the same mount and source-client config carries over to a multi-station server like &lt;a href="https://www.lurcast.com/" rel="noopener noreferrer"&gt;Lurcast&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you install and configure Icecast2 on Raspberry Pi OS?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Install the package
&lt;/h3&gt;

&lt;p&gt;Update your package list and install Icecast2 with &lt;code&gt;sudo apt update &amp;amp;&amp;amp; sudo apt install icecast2&lt;/code&gt;. On current Raspberry Pi OS, the package pulls in everything needed, including an init script. Skip the debconf prompts about setting an initial password; you will edit the config directly next.&lt;/p&gt;

&lt;h3&gt;
  
  
  Edit /etc/icecast2/icecast.xml
&lt;/h3&gt;

&lt;p&gt;The single most important thing to understand in &lt;code&gt;/etc/icecast2/icecast.xml&lt;/code&gt; is that the passwords you set here are what your source clients and your admin panel use, so treat them like real credentials. Open the file as root and change &lt;code&gt;&amp;lt;source-password&amp;gt;&lt;/code&gt;, which is what your encoder (Icecast's &lt;code&gt;ices&lt;/code&gt;, Liquidsoap, or even a DJ's broadcasting software) must present to open a mount point. Change &lt;code&gt;&amp;lt;admin-password&amp;gt;&lt;/code&gt;, which protects the web admin pages. If you want a separate relay credential, set &lt;code&gt;&amp;lt;relay-password&amp;gt;&lt;/code&gt; too, though a single-station Pi usually leaves it alone.&lt;/p&gt;

&lt;p&gt;The &lt;code&gt;&amp;lt;hostname&amp;gt;&lt;/code&gt; value should be the public name listeners will use, such as &lt;code&gt;radio.example.com&lt;/code&gt;, not &lt;code&gt;localhost&lt;/code&gt;, or player-side redirects and stats can behave oddly. The default &lt;code&gt;&amp;lt;listen-socket&amp;gt;&lt;/code&gt; port is 8000; you can keep it, but note that any change must match what your source client connects to and what your router forwards later. Save the file, then run &lt;code&gt;icecast2 -c /etc/icecast2/icecast.xml -b&lt;/code&gt; style checks or simply start the service and watch &lt;code&gt;journalctl -u icecast2&lt;/code&gt; for config errors.&lt;/p&gt;

&lt;h3&gt;
  
  
  Enable the service and verify the status page
&lt;/h3&gt;

&lt;p&gt;Run &lt;code&gt;sudo systemctl enable --now icecast2&lt;/code&gt; so it survives reboots. Confirm it is listening with &lt;code&gt;sudo ss -tlnp | grep 8000&lt;/code&gt;, then open &lt;code&gt;http://&amp;lt;pi-ip&amp;gt;:8000/&lt;/code&gt; in a browser. You should see the Icecast status page with zero active mounts, which is correct, since no source client is connected yet.&lt;/p&gt;

&lt;p&gt;Once your mount is live and you are adding stations, a single Pi running plain Icecast2 gets cramped fast. &lt;a href="https://www.lurcast.com/" rel="noopener noreferrer"&gt;Lurcast&lt;/a&gt; is built for that next step: multiple stations in one process on the same box.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you get audio into your Icecast server from a source client?
&lt;/h2&gt;

&lt;p&gt;Icecast serves whatever a source client pushes to it. Each stream lives on a mount point such as &lt;code&gt;/radio.mp3&lt;/code&gt;, and the source client authenticates with the &lt;code&gt;source&lt;/code&gt; password from your &lt;code&gt;icecast.xml&lt;/code&gt; before connecting to &lt;code&gt;http://your-pi:8000/radio.mp3&lt;/code&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Mount points and source passwords
&lt;/h3&gt;

&lt;p&gt;Define per-mount settings like bitrate caps and a fallback mount in &lt;code&gt;/etc/icecast2/icecast.xml&lt;/code&gt;. A fallback stream pointing at a silent or looped mount means a dropped source never leaves dead air. Change the default &lt;code&gt;hackme&lt;/code&gt; source password before exposing port 8000.&lt;/p&gt;

&lt;h3&gt;
  
  
  Liquidsoap as a playlist AutoDJ
&lt;/h3&gt;

&lt;p&gt;Liquidsoap runs on the Pi itself, crossfades a playlist, inserts scheduled shows, and streams to your mount. A minimal &lt;code&gt;radio.liq&lt;/code&gt; with &lt;code&gt;playlist()&lt;/code&gt; and &lt;code&gt;output.icecast(%mp3)&lt;/code&gt; is enough for 24/7 playout. If you later move to a multi-station setup, &lt;a href="https://www.lurcast.com/docs" rel="noopener noreferrer"&gt;Lurcast's docs&lt;/a&gt; cover running many mounts in one process.&lt;/p&gt;

&lt;h3&gt;
  
  
  ffmpeg or darkice from a line-in or external encoder
&lt;/h3&gt;

&lt;p&gt;For a live mic or mixer, pipe line-in with ffmpeg (&lt;code&gt;-f alsa -i hw:0&lt;/code&gt;) or run darkice, both re-encoding to mp3 or aac before pushing to the same mount. Store playlist and log files on USB or SSD rather than the SD card; the Raspberry Pi documentation warns that SD cards wear out under constant writes (&lt;a href="https://www.raspberrypi.com/documentation/" rel="noopener noreferrer"&gt;Raspberry Pi documentation&lt;/a&gt;).&lt;/p&gt;

&lt;h2&gt;
  
  
  How many listeners can a Raspberry Pi realistically handle?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  What limits capacity: CPU, RAM, or upload bandwidth
&lt;/h3&gt;

&lt;p&gt;Icecast2 barely touches RAM; a Pi 4 with 2 GB will never run out serving streams. CPU cost is per-listener relay work: every connected listener gets its own copy of the stream, so a 100-listener mount costs roughly 100 times the relay CPU of a single one. Encoding is not the problem, since your source client (Liquidsoap, ezstream, an AutoDJ) does that work and sends one copy upstream.&lt;/p&gt;

&lt;h3&gt;
  
  
  Rough capacity by Pi model and bitrate
&lt;/h3&gt;

&lt;p&gt;These are illustrative planning numbers, not benchmarks. A Pi 3B+ comfortably serves a single 128 kbps mount to a few dozen listeners. A Pi 4 handles a few hundred listeners across two or three mounts before relay CPU saturates a core. A Pi 5 adds headroom, but the pattern holds: each mount and each listener adds linear work.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why upstream bandwidth is usually the real ceiling
&lt;/h3&gt;

&lt;p&gt;Bandwidth kills the Pi server before CPU does. Twenty listeners on a 128 kbps mount pull about 2.5 Mbps sustained upload, and home connections rarely give you that reliably. If you outgrow your upload, move the listener-facing side off the Pi: a VPS running Lurcast can relay your Pi's mount as its source, and its &lt;a href="https://www.lurcast.com/docs/api" rel="noopener noreferrer"&gt;provisioning API&lt;/a&gt; lets you scale listener slots without touching your home connection.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you expose your Pi stream to listeners outside your home network?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Port forward 8000 to the Pi
&lt;/h3&gt;

&lt;p&gt;Icecast2 listens on port 8000 by default. In your router's admin panel, forward external port 8000 to the Pi's local IP, and give the Pi a static local address or a DHCP reservation so the rule survives reboots. Check your ISP isn't using carrier-grade NAT; if your WAN IP starts with 100.64.x.x or the router's WAN interface never matches what sites like whatismyip report, port forwarding cannot work and you need the VPS route below.&lt;/p&gt;

&lt;h3&gt;
  
  
  Dynamic DNS for changing home IPs
&lt;/h3&gt;

&lt;p&gt;Home IPs change, so point listeners at a hostname instead. Most routers support DDNS providers natively, or you can run a small update client on the Pi itself. Keep the firewall tight: allow 8000 inbound, allow outbound, and drop everything else you don't specifically need.&lt;/p&gt;

&lt;h3&gt;
  
  
  VPS in front of the Pi as an alternative
&lt;/h3&gt;

&lt;p&gt;If forwarding is blocked or unstable, rent a cheap VPS, run Icecast there, and have your Pi push a mount to it as the source client. Listeners hit the VPS; your home connection only carries one upstream encode. This also sidesteps the reliability question entirely: a Pi under sustained load can throttle if it overheats or sags on an underpowered supply, per the &lt;a href="https://www.raspberrypi.com/documentation/computers/raspberry-pi.html" rel="noopener noreferrer"&gt;Raspberry Pi hardware documentation&lt;/a&gt;, and a VPS removes your home internet from the uptime equation. If you later outgrow a single box, Lurcast runs many stations in one process on a VPS with per-station caps (&lt;a href="https://www.lurcast.com/docs/licensing" rel="noopener noreferrer"&gt;licensing and renewal&lt;/a&gt;).&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you keep the Pi and stream running after a reboot or crash?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  systemd restart and dependency ordering
&lt;/h3&gt;

&lt;p&gt;Create a unit file for your source client (Liquidsoap, Ezstream, or whatever feeds your mount) with &lt;code&gt;Restart=always&lt;/code&gt; and &lt;code&gt;RestartSec=5&lt;/code&gt;. Add &lt;code&gt;After=network-online.target&lt;/code&gt; and &lt;code&gt;Wants=network-online.target&lt;/code&gt; so it never starts before the Pi has an IP. Icecast2 installed from the package repo already ships its own unit; check it with &lt;code&gt;systemctl status icecast2&lt;/code&gt; and enable both services so dead air after a power cut lasts seconds, not until you notice.&lt;/p&gt;

&lt;h3&gt;
  
  
  Logging to RAM and reducing SD writes
&lt;/h3&gt;

&lt;p&gt;SD cards die from constant writes, and a stream server writing access logs 24/7 accelerates that. Mount &lt;code&gt;/var/log&lt;/code&gt; as &lt;code&gt;tmpfs&lt;/code&gt; in &lt;code&gt;/etc/fstab&lt;/code&gt;, or set Icecast's loglevel to 1 and point logs at RAM. Add &lt;code&gt;Storage=volatile&lt;/code&gt; under &lt;code&gt;[Journal]&lt;/code&gt; in &lt;code&gt;/etc/systemd/journald.conf&lt;/code&gt; to cap journald in memory. Run &lt;code&gt;logrotate&lt;/code&gt; configs with &lt;code&gt;size&lt;/code&gt; triggers rather than daily rotation so nothing writes unless it must.&lt;/p&gt;

&lt;h3&gt;
  
  
  Temperature, throttling and power supply checks
&lt;/h3&gt;

&lt;p&gt;Sustained encoding keeps the CPU warm; throttling causes dropped listener connections that look like network faults. Check &lt;code&gt;vcgencmd get_throttled&lt;/code&gt; (a non-zero value means trouble) and &lt;code&gt;vcgencmd measure_temp&lt;/code&gt; under load. A heatsink and a proper 5V/3A supply, not a phone charger, keep the Pi stable for months unattended.&lt;/p&gt;

&lt;h2&gt;
  
  
  When does a Raspberry Pi Icecast server stop being enough?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Signs you have outgrown one station on a Pi
&lt;/h3&gt;

&lt;p&gt;A Pi handles one mount and a handful of listener slots fine. The signals you have outgrown it are operational, not audio: you are running several stations per box, reselling listener-count tiers, and hand-building royalty reports and WHMCS provisioning scripts because no panel fits. If you also track tuning hours per customer and need per-station bitrate caps, a single Icecast2 install becomes a pile of shell scripts you alone can maintain.&lt;/p&gt;

&lt;h3&gt;
  
  
  Hosting multiple stations: panels and single-process servers
&lt;/h3&gt;

&lt;p&gt;Stream hosts typically move up to Centova Cast or MediaCP, or to AzuraCast, which bundles Icecast behind a web panel. AzuraCast's maintainers have documented that upstream Icecast and the icecast-kh fork have seen no releases in years, with segfaults and metadata bugs piling up (&lt;a href="https://github.com/AzuraCast/AzuraCast/issues/7633" rel="noopener noreferrer"&gt;AzuraCast issue tracker&lt;/a&gt;). Lurcast takes a different route: every station you host runs in one process, with a provisioning API, per-station listener caps and royalty CSVs, shipped as a Linux download, Docker image, systemd unit or AGPL-3.0 source.&lt;/p&gt;

&lt;h3&gt;
  
  
  Running the same criteria against Lurcast honestly
&lt;/h3&gt;

&lt;p&gt;Lurcast does not replace your WHMCS billing stack; it provisions stations into it. Under sustained load, supervise it the way you would any service: systemd's Restart= and watchdog directives are the documented mechanisms for automatic recovery, and the &lt;a href="https://www.lurcast.com/docs" rel="noopener noreferrer"&gt;Lurcast docs&lt;/a&gt; cover deployment as a systemd unit or Docker image.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pi Icecast vs a VPS: which should you host your stream on?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Cost and control
&lt;/h3&gt;

&lt;p&gt;A Pi costs its hardware price and a few watts, and you keep full control of the mount points, bitrate caps and fallback configuration. A €4–10/month VPS buys the same control with better connectivity. Managed panels like Centova Cast or MediaCP trade control for convenience, and a hosting-provider setup like Lurcast's €29 or €59 editions sits between: you still own the box, but provisioning, per-station caps and royalty CSVs are handled for you.&lt;/p&gt;

&lt;h3&gt;
  
  
  Uptime and bandwidth
&lt;/h3&gt;

&lt;p&gt;A home Pi depends on your residential connection, your router's port forwarding and your household's power. A VPS gives you data-centre uptime and upload bandwidth you don't have to share with Netflix night. If dead air costs you listeners, the VPS wins on uptime alone.&lt;/p&gt;

&lt;h3&gt;
  
  
  Migration path
&lt;/h3&gt;

&lt;p&gt;Start on the Pi to learn the stack, then move mounts to a VPS when tuning hours grow. Your source clients, fallbacks and stats scripts carry over unchanged, so the switch is a config copy, not a rebuild.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  How do I stream my Pi's Icecast server to directories like the Icecast public directory?
&lt;/h3&gt;

&lt;p&gt;Set &amp;lt;public&amp;gt;1&amp;lt;/public&amp;gt; on your mount in icecast.xml and give the mount a real name and genre. Icecast then exposes a YP listing endpoint, and directory services like dir.xiph.org poll your status page and list the stream automatically. Make sure &amp;lt;hostname&amp;gt; is your public domain, or the directory will publish an unreachable address.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can a Raspberry Pi run Icecast and Liquidsoap on the same SD card?
&lt;/h3&gt;

&lt;p&gt;Technically yes, but it is the fastest way to kill the card. Liquidsoap reads playlist files constantly and both services write logs around the clock, which wears SD storage out. Boot from a USB SSD, or at minimum mount logs as tmpfs and use a high-endurance card, expecting to replace it eventually.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do I need to change the default Icecast passwords before going live?
&lt;/h3&gt;

&lt;p&gt;Yes. The default source password is hackme, and anyone who guesses it can push audio to your mounts or take them over. Change &amp;lt;source-password&amp;gt; and &amp;lt;admin-password&amp;gt; in icecast.xml before forwarding port 8000, then use the new source password in every encoder that connects.&lt;/p&gt;

&lt;h3&gt;
  
  
  What does the Icecast status page show when no source is connected?
&lt;/h3&gt;

&lt;p&gt;It shows the server version, uptime and zero active mounts, which is exactly what you should see right after installation. If the page loads but stays empty after your encoder starts, the source password or mount path is wrong; check journalctl -u icecast2 and your Liquidsoap or darkice logs for authentication errors.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Lurcast is an open-source (AGPL-3.0) internet radio streaming server, compatible with Icecast and SHOUTcast: &lt;a href="https://www.lurcast.com" rel="noopener noreferrer"&gt;lurcast.com&lt;/a&gt; · &lt;a href="https://github.com/Lurcast/lurcast" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>icecast</category>
      <category>raspberrypi</category>
      <category>selfhosted</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Icecast Server Download: Safe Sources and Setup</title>
      <dc:creator>Lurcast</dc:creator>
      <pubDate>Thu, 19 Nov 2026 21:37:17 +0000</pubDate>
      <link>https://dev.to/lurcast/icecast-server-download-safe-sources-and-setup-3m9h</link>
      <guid>https://dev.to/lurcast/icecast-server-download-safe-sources-and-setup-3m9h</guid>
      <description>&lt;p&gt;&lt;em&gt;This article was first published on the &lt;a href="https://www.lurcast.com/blog/icecast-server-download" rel="noopener noreferrer"&gt;Lurcast blog&lt;/a&gt;. It was written with AI assistance.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Key takeaways
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Download Icecast only from the official icecast.org downloads page; third-party binaries have no verifiable provenance.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Verify tarballs with sha256sum or GPG signatures, while apt and dnf packages are checked automatically against repository signing keys.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Choose the package that matches your deployment: Windows installer for testing, apt for hands-off VPS nodes, source builds for RHEL, Docker for multi-station hosts.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The icecast-kh fork and upstream Icecast have both gone years without new releases, so hosts carry the maintenance risk themselves.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A bare Icecast install lacks per-station caps, provisioning APIs and royalty reporting that a reseller hosting business needs.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Get your Icecast server download from the official Xiph project at icecast.org, pick the package for your OS (Windows installer, Debian/Ubuntu, RHEL, Docker, or source tarball), verify the checksum or signature, then run the binary with its default config to confirm your first mount serves audio. This guide walks through each step, then covers the maintenance risk you inherit when you build a hosting business on upstream Icecast.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where do I download the official Icecast server safely?
&lt;/h2&gt;

&lt;p&gt;The only safe source for an Icecast server download is the official downloads page on icecast.org, which lists the current release and the package formats Xiph maintains for each platform. Anything else is a copy of unknown provenance.&lt;/p&gt;

&lt;h3&gt;
  
  
  The only source you should trust: icecast.org and Xiph
&lt;/h3&gt;

&lt;p&gt;Binaries scraped from forums or third-party mirrors can be outdated, miscompiled, or tampered with, and you have no checksum to compare against. The downloads page also links the source tarball, so you can build it yourself on Debian, Ubuntu, or RHEL if no package fits.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why the icecast-kh fork complicates 'official'
&lt;/h3&gt;

&lt;p&gt;Many hosts run icecast-kh, the fork long maintained by Karl Heyes, because it adds features upstream lacks. It is not an Xiph release, so "official" verification steps do not apply to it. If that maintenance gap worries you, Lurcast keeps your existing encoders, players, and stats scripts while running every station in one process (&lt;a href="https://www.lurcast.com/" rel="noopener noreferrer"&gt;Lurcast: streaming server for radio hosting companies&lt;/a&gt;).&lt;/p&gt;

&lt;h2&gt;
  
  
  Which Icecast package should I choose for my OS (Windows, Debian/Ubuntu, RHEL, Docker)?
&lt;/h2&gt;

&lt;p&gt;Pick the artifact that matches how you run your VPS. The same server ships as a Windows installer, Linux packages, a Docker image, and source you compile yourself. If you resell listener-slot tiers, Docker or a distro package is usually the right call because upgrades stay scripted.&lt;/p&gt;

&lt;h3&gt;
  
  
  Windows installer
&lt;/h3&gt;

&lt;p&gt;Use the installer only for testing or a single-station box. It gets you a working mount fast, but production stream hosts rarely run Windows.&lt;/p&gt;

&lt;h3&gt;
  
  
  Debian/Ubuntu packages
&lt;/h3&gt;

&lt;p&gt;On Debian or Ubuntu, install the distro package with apt, or add a third-party repository if you need a newer build. Distro packages lag upstream but receive security patches automatically, which suits a set-and-forget AutoDJ node.&lt;/p&gt;

&lt;h3&gt;
  
  
  RHEL/CentOS and building from source
&lt;/h3&gt;

&lt;p&gt;RHEL-family repos rarely carry Icecast, so expect to build from source. That gives you control over the configure flags, but you own every future rebuild, including the icecast-kh fork if you use it.&lt;/p&gt;

&lt;h3&gt;
  
  
  Docker image
&lt;/h3&gt;

&lt;p&gt;A Docker image pins the version and makes per-station caps and restarts predictable across hosts.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Platform&lt;/th&gt;
&lt;th&gt;Artifact&lt;/th&gt;
&lt;th&gt;Best for&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Windows&lt;/td&gt;
&lt;td&gt;Installer&lt;/td&gt;
&lt;td&gt;Testing, single station&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Debian/Ubuntu&lt;/td&gt;
&lt;td&gt;apt package&lt;/td&gt;
&lt;td&gt;Hands-off VPS nodes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;RHEL/CentOS&lt;/td&gt;
&lt;td&gt;Source build&lt;/td&gt;
&lt;td&gt;Custom flags, older distros&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Docker&lt;/td&gt;
&lt;td&gt;Image&lt;/td&gt;
&lt;td&gt;Multi-station hosts, scripted deploys&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;If you run a hosting panel under WHMCS, check the &lt;a href="https://www.lurcast.com/terms" rel="noopener noreferrer"&gt;terms&lt;/a&gt; of any packaged distribution before reselling stations on it.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do I verify my Icecast download with checksums or signatures?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Verifying a tarball or source release
&lt;/h3&gt;

&lt;p&gt;Download the &lt;code&gt;.sha256&lt;/code&gt; sum or signature file published alongside the release, then run &lt;code&gt;sha256sum icecast-*.tar.gz&lt;/code&gt; and compare the output by eye or with &lt;code&gt;sha256sum -c checksums.txt&lt;/code&gt;. If the project publishes a GPG signature, verify it with &lt;code&gt;gpg --verify icecast-*.tar.gz.sig icecast-*.tar.gz&lt;/code&gt; after importing the maintainer's key. The GnuPG manual documents the full key-import and verification workflow: &lt;a href="https://www.gnupg.org/documentation/manuals.html" rel="noopener noreferrer"&gt;GnuPG verification steps&lt;/a&gt;. A mismatched hash means the file never reaches your production VPS.&lt;/p&gt;

&lt;h3&gt;
  
  
  Verifying distro packages via apt/dnf signatures
&lt;/h3&gt;

&lt;p&gt;On Debian or Ubuntu, distro packages are verified automatically against the repository signing key, so &lt;code&gt;apt-get install icecast2&lt;/code&gt; needs no manual checksum work. On RHEL-family systems, &lt;code&gt;dnf install icecast&lt;/code&gt; checks the package against the repo's GPG key; confirm the key fingerprint listed in the repo file matches what the repository publishes. Only tarballs you fetch by hand need the manual steps above.&lt;/p&gt;

&lt;p&gt;If you would rather skip manual builds and run stations in one process, Lurcast ships a Docker image and source you can audit the same way, keeping your existing Icecast encoders and stats scripts (see the &lt;a href="https://www.lurcast.com/docs" rel="noopener noreferrer"&gt;Lurcast docs&lt;/a&gt;).&lt;/p&gt;

&lt;h2&gt;
  
  
  What versions of Icecast are current, and should I use stable or development builds?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Release cadence and what it means for your uptime
&lt;/h3&gt;

&lt;p&gt;Upstream Icecast from Xiph has gone years without a new release, and the AzuraCast maintainers report segfaults, mishandled metadata and crashes with no log output on the builds they ship. When the server your customers stream through stops getting fixes, every bug becomes your bug. For a host reselling listener-slot tiers, a stalled release cadence means you patch around problems yourself or eat dead air.&lt;/p&gt;

&lt;h3&gt;
  
  
  The icecast-kh question for hosting providers
&lt;/h3&gt;

&lt;p&gt;The &lt;code&gt;icecast-kh&lt;/code&gt; fork, originally maintained by Karl Heyes, added features hosts relied on, but it has also gone years without new versions. Running a fork with no upstream is a bet that nothing breaks. If you are provisioning stations through WHMCS and need per-station caps, a provisioning API and royalty CSVs, an alternative that keeps your existing Icecast encoders, players and stats scripts may be the safer base. Lurcast documents its integrations, including plugin support, in the &lt;a href="https://www.lurcast.com/docs/plugins" rel="noopener noreferrer"&gt;Plugins · Lurcast docs&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What do I do immediately after downloading Icecast to get it running?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Minimum viable icecast.xml
&lt;/h3&gt;

&lt;p&gt;The tarball ships an &lt;code&gt;icecast.xml&lt;/code&gt; you can edit in place. Change three things before first start: the &lt;code&gt;&amp;lt;source-password&amp;gt;&lt;/code&gt; your encoders will use, the &lt;code&gt;&amp;lt;admin-password&amp;gt;&lt;/code&gt; for the web admin, and the &lt;code&gt;&amp;lt;hostname&amp;gt;&lt;/code&gt; to your server's public name. Leave the default &lt;code&gt;&amp;lt;listen-socket&amp;gt;&lt;/code&gt; port of 8000 unless something else claims it.&lt;/p&gt;

&lt;p&gt;The passwords are the part hosts get burned on. A stream host running dozens of stations on one box should give every customer a distinct source password, because anyone holding a valid source credential can push audio to a mount, replace a fallback stream, or push metadata that your royalty reports then record. Shared credentials across stations mean one leaked password takes down or contaminates every mount on the server, and you will have no way to tell which customer it was. Set per-station source credentials in &lt;code&gt;icecast.xml&lt;/code&gt; before you hand anything to a payer, and rotate them when a customer cancels.&lt;/p&gt;

&lt;h3&gt;
  
  
  Open the firewall and start the service
&lt;/h3&gt;

&lt;p&gt;Open TCP 8000 (or your configured port) in &lt;code&gt;ufw&lt;/code&gt; or &lt;code&gt;firewalld&lt;/code&gt;, then run &lt;code&gt;icecast -c /etc/icecast.xml&lt;/code&gt; in the foreground first so you see config errors directly. Once it starts clean, move to a systemd unit so it survives reboots. If you want a checklist for running it as a long-lived service on a host box, our &lt;a href="https://www.lurcast.com/docs/operations" rel="noopener noreferrer"&gt;operations docs&lt;/a&gt; cover that path.&lt;/p&gt;

&lt;h3&gt;
  
  
  Confirm your first mount is serving
&lt;/h3&gt;

&lt;p&gt;Open &lt;code&gt;http://your-server:8000/status.xsl&lt;/code&gt; in a browser. You should see the server version and, once a source connects, the mount with its bitrate and listener count. Point an encoder or AutoDJ at the source password you set, connect, then test the player URL from outside your network to rule out a firewall that only passes local traffic.&lt;/p&gt;

&lt;h2&gt;
  
  
  What are common download and installation errors on Windows and Linux?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Linux: package and permission errors
&lt;/h3&gt;

&lt;p&gt;If Icecast won't start after an apt or yum install, check what's holding port 8000 first: &lt;code&gt;ss -tlnp | grep 8000&lt;/code&gt;. Another listener process, an old Icecast instance, or your existing panel's fallback stream will block the bind. Stop it or change the port in the config.&lt;/p&gt;

&lt;p&gt;"Permission denied" on the config usually means the service user can't read it. If you run Icecast as its own user, &lt;code&gt;chown icecast:icecast /etc/icecast2/icecast.xml&lt;/code&gt; and keep the config at 640. Missing shared libraries after a source build show up as errors at launch, not compile time; run &lt;code&gt;ldd&lt;/code&gt; on the binary and install the listed dev packages.&lt;/p&gt;

&lt;h3&gt;
  
  
  Windows: service and firewall errors
&lt;/h3&gt;

&lt;p&gt;A Windows service that starts and immediately stops almost always points to a config error. Run &lt;code&gt;icecast.exe -c icecast.xml&lt;/code&gt; from a terminal instead: the console output shows the exact line that fails, which the service log hides.&lt;/p&gt;

&lt;p&gt;If the server runs but no player connects, add a Windows Defender Firewall inbound rule for the port, not the executable. Listeners outside your network hitting connection timeouts after a fresh install are almost always blocked here.&lt;/p&gt;

&lt;h2&gt;
  
  
  Is a plain Icecast server download enough if you host stations for customers?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  What one Icecast process does not give a reseller
&lt;/h3&gt;

&lt;p&gt;A single Icecast install serves mounts fine, but a hosting business needs three things a bare server has no concept of: per-station listener-slot and bitrate caps, an API so WHMCS can provision and suspend packages automatically, and per-station royalty CSVs and tuning-hour reports. Stitching those from shell scripts around Icecast works until you hit a segfault or a crash with no log information, which is exactly what hosts report upstream: &lt;a href="https://github.com/AzuraCast/AzuraCast/issues/7633" rel="noopener noreferrer"&gt;AzuraCast's maintainers describe Icecast maintenance as effectively dormant, with segfaults and mishandled metadata piling up&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Running the same checklist over Icecast, panels and Lurcast
&lt;/h3&gt;

&lt;p&gt;Icecast: free, battle-tested, but you build caps, provisioning and reporting yourself, and you carry the maintenance risk above. Centova Cast and MediaCP: commercial panels that bundle provisioning and billing hooks, at licence cost per server. AzuraCast: free and web-based, but heavier per station and, per its own issue tracker, exposed to the same upstream Icecast problems. Lurcast: every customer station in one Linux process or Docker container, with a provisioning API, per-station caps and royalty CSVs, at €29 or €59 for the Hosting edition, while keeping your existing Icecast encoders, players and stats scripts. The honest trade-off: Lurcast is AGPL-3.0 source you run yourself, so you own the uptime.&lt;/p&gt;

&lt;h2&gt;
  
  
  When should a radio host choose a managed Icecast solution instead of self-hosting?
&lt;/h2&gt;

&lt;p&gt;Managed hosting like &lt;a href="https://radio.co/" rel="noopener noreferrer"&gt;Radio.co&lt;/a&gt; makes sense when you have no sysadmin time, no WHMCS stack to feed, and only a handful of stations. You trade control of the mount for someone else handling uptime, encoder updates, and dead-air monitoring. If you bill customers per listener slot, though, a panel plus a VPS usually costs less and keeps your royalty reports and stats scripts under your own roof.&lt;/p&gt;

&lt;p&gt;If you self-host, Lurcast runs every station you host in one Linux process or Docker container, keeps your existing Icecast and SHOUTcast encoders and players, and adds per-station caps, a provisioning API, and royalty CSVs aimed at WHMCS hosts. The Hosting edition starts at €29. Source is on &lt;a href="https://github.com/lurcast/lurcast" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; under AGPL-3.0.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Is Icecast free to download and use for a commercial radio host?
&lt;/h3&gt;

&lt;p&gt;Yes. Icecast is free software released by the Xiph project, and there is no licence fee for running it commercially, whether you stream one station or resell listener slots. The costs you take on are operational: VPS or dedicated hardware, your time maintaining builds, and the tooling for per-station caps, provisioning and royalty reporting that a bare server does not include.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I run Icecast and SHOUTcast mounts on the same VPS?
&lt;/h3&gt;

&lt;p&gt;Yes, as long as they listen on different ports. Icecast defaults to TCP 8000, so give SHOUTcast a different port in its config and open both in your firewall with ufw or firewalld. Watch memory and bandwidth, since every mount's listeners count against the same box. Check with ss -tlnp before starting either service to avoid a port-bind conflict.&lt;/p&gt;

&lt;h3&gt;
  
  
  How do I download Icecast on Ubuntu without adding a PPA?
&lt;/h3&gt;

&lt;p&gt;Run sudo apt-get install icecast2. Ubuntu's own repositories carry an Icecast package, and apt verifies it automatically against the repository signing key, so no manual checksum work is needed. The trade-off is version lag: distro packages can trail the current upstream release, but they receive security patches through your normal update cycle, which suits a set-and-forget AutoDJ node.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does the Icecast download include AutoDJ, or do I need a separate source client?
&lt;/h3&gt;

&lt;p&gt;The download includes only the server. AutoDJ is a source client, a separate program that connects to Icecast using the source password from your icecast.xml and pushes audio to a mount. Common choices include Liquidsoap, Ezstream and the AutoDJ bundled with panels like AzuraCast or Centova Cast. Until a source connects, your mount exists but status.xsl shows no listeners.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is the icecast-kh build and why do some hosts prefer it?
&lt;/h3&gt;

&lt;p&gt;The icecast-kh build is a fork of Icecast long maintained by Karl Heyes. It added features hosts relied on that upstream lacked, which is why many stream hosts still run it. It is not an Xiph release, so official verification steps do not apply, and it has also gone years without new versions. Running it means betting that nothing breaks.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Lurcast is an open-source (AGPL-3.0) internet radio streaming server, compatible with Icecast and SHOUTcast: &lt;a href="https://www.lurcast.com" rel="noopener noreferrer"&gt;lurcast.com&lt;/a&gt; · &lt;a href="https://github.com/Lurcast/lurcast" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>icecast</category>
      <category>linux</category>
      <category>docker</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>How to Start an Icecast Server on a Linux VPS</title>
      <dc:creator>Lurcast</dc:creator>
      <pubDate>Thu, 19 Nov 2026 21:37:06 +0000</pubDate>
      <link>https://dev.to/lurcast/how-to-start-an-icecast-server-on-a-linux-vps-3o2k</link>
      <guid>https://dev.to/lurcast/how-to-start-an-icecast-server-on-a-linux-vps-3o2k</guid>
      <description>&lt;p&gt;&lt;em&gt;This article was first published on the &lt;a href="https://www.lurcast.com/blog/start-icecast-server-linux-vps" rel="noopener noreferrer"&gt;Lurcast blog&lt;/a&gt;. It was written with AI assistance.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Key takeaways
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Install Icecast on Ubuntu or Debian with sudo apt install icecast2, then enable it with systemctl enable --now icecast2.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Edit /etc/icecast2/icecast.xml to change the source, admin and relay passwords from hackme, set hostname, and add a mount with a fallback stream.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Open tcp/8000 in both ufw and your VPS provider's cloud security group, then test with curl -I &lt;a href="http://localhost:8000/status.xsl" rel="noopener noreferrer"&gt;http://localhost:8000/status.xsl&lt;/a&gt; before going remote.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Connect a source client like Liquidsoap or ezstream using the source password, server IP and mount name; a 401 in the logs means a password mismatch.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;At 128 kbps, listener capacity is bitrate times listeners, so a Radio 100 tier needs roughly 12.8 Mbps of sustained outbound bandwidth.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To start an Icecast server, install the icecast2 package on Ubuntu or Debian, replace the default config with a working icecast.xml, open port 8000 in your firewall, and connect a source client like Liquidsoap or ezstream to your mount. This walkthrough gives you every command and config line, plus fixes for the three failures that kill most first attempts.&lt;/p&gt;

&lt;h2&gt;
  
  
  What do you need before you start an Icecast server?
&lt;/h2&gt;

&lt;p&gt;Four things: a VPS with a public IP address, one free TCP port (8000 by default), a source client or AutoDJ to feed audio into the mount, and enough upstream bandwidth to carry your listener slots. Icecast itself is lightweight, so 1 GB of RAM is plenty for a first run; the network is what usually bites people. The server's behaviour is controlled entirely by one XML file, so it is worth skimming the &lt;a href="https://icecast.org/docs/" rel="noopener noreferrer"&gt;official Icecast documentation on icecast.xml configuration&lt;/a&gt; before you edit anything.&lt;/p&gt;

&lt;h3&gt;
  
  
  Bandwidth math for Radio 100/250/500 style listener tiers
&lt;/h3&gt;

&lt;p&gt;Multiply bitrate by listeners. A Radio 100 tier at 128 kbps needs roughly 100 × 128 kbps ≈ 12.8 Mbps of sustained outbound capacity; a Radio 500 tier at the same bitrate needs about 64 Mbps. Leave headroom above the raw math, because rebuffering and dead air cost you listeners faster than any config mistake. If you plan to resell tiers later through WHMCS, note that per-station caps and royalty reports become the next problem; that is where a panel or a self-hosted alternative like Lurcast (AGPL-3.0, &lt;a href="https://www.lurcast.com/terms" rel="noopener noreferrer"&gt;https://www.lurcast.com/terms&lt;/a&gt;) enters the picture, but plain Icecast is fine to start.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you install Icecast on Ubuntu or Debian?
&lt;/h2&gt;

&lt;p&gt;The fastest way to start an Icecast server on Ubuntu or Debian is one command: &lt;code&gt;sudo apt install icecast2&lt;/code&gt;. The package pulls in the daemon, a default &lt;code&gt;/etc/icecast2/icecast.xml&lt;/code&gt;, and log directories under &lt;code&gt;/var/log/icecast2&lt;/code&gt;. On Debian-family installers you may be prompted to set the source and admin passwords; if you skip them, edit the XML directly before going live.&lt;/p&gt;

&lt;h3&gt;
  
  
  Enabling the service with systemd
&lt;/h3&gt;

&lt;p&gt;Start and persist the daemon with &lt;code&gt;sudo systemctl enable --now icecast2&lt;/code&gt;. Confirm it is running with &lt;code&gt;systemctl status icecast2&lt;/code&gt;, then check the listener port with &lt;code&gt;ss -tlnp | grep 8000&lt;/code&gt;. A 404 or the default status page at &lt;code&gt;http://your-vps-ip:8000&lt;/code&gt; means the daemon is up and you are ready to edit config. If you later outgrow a single Icecast instance, a self-hosted alternative like &lt;a href="https://www.lurcast.com/" rel="noopener noreferrer"&gt;Lurcast&lt;/a&gt; runs many stations in one process on the same VPS.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you configure icecast.xml for your first stream?
&lt;/h2&gt;

&lt;p&gt;The default config file shipped with the Icecast package on Ubuntu or Debian lives at &lt;code&gt;/etc/icecast2/icecast.xml&lt;/code&gt; and works after three edits: passwords, hostname, and a mount block. Package availability differs per distro, so check the &lt;a href="https://icecast.org/download/" rel="noopener noreferrer"&gt;Icecast download page&lt;/a&gt; if your repo ships an old build.&lt;/p&gt;

&lt;h3&gt;
  
  
  The authentication block: source, admin and relay passwords
&lt;/h3&gt;

&lt;p&gt;Three passwords matter. &lt;code&gt;source&lt;/code&gt; authenticates encoder connections to mounts, &lt;code&gt;admin&lt;/code&gt; unlocks the web admin at &lt;code&gt;/admin&lt;/code&gt;, and &lt;code&gt;relay&lt;/code&gt; lets other Icecast servers pull your streams. Change all three from &lt;code&gt;hackme&lt;/code&gt; before anything else:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight xml"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;authentication&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;source-password&amp;gt;&lt;/span&gt;pick-a-long-source-pass&lt;span class="nt"&gt;&amp;lt;/source-password&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;relay-password&amp;gt;&lt;/span&gt;pick-a-relay-pass&lt;span class="nt"&gt;&amp;lt;/relay-password&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;admin-user&amp;gt;&lt;/span&gt;admin&lt;span class="nt"&gt;&amp;lt;/admin-user&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;admin-password&amp;gt;&lt;/span&gt;pick-an-admin-pass&lt;span class="nt"&gt;&amp;lt;/admin-password&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/authentication&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;hostname&amp;gt;&lt;/span&gt;radio.example.com&lt;span class="nt"&gt;&amp;lt;/hostname&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;listen-socket&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;port&amp;gt;&lt;/span&gt;8000&lt;span class="nt"&gt;&amp;lt;/port&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/listen-socket&amp;gt;&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Set &lt;code&gt;hostname&lt;/code&gt; to the public DNS name of your VPS, not &lt;code&gt;localhost&lt;/code&gt;, or generated playlist URLs will point nowhere.&lt;/p&gt;

&lt;h3&gt;
  
  
  Defining a mount point with a fallback stream
&lt;/h3&gt;

&lt;p&gt;A default mount is what keeps dead air off your station. The &lt;code&gt;fallback-mount&lt;/code&gt; sends listeners to a 24/7 AutoDJ or loop file whenever your live source disconnects, and &lt;code&gt;fallback-override&lt;/code&gt; moves them back automatically when the live stream returns:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight xml"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;mount&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;mount-name&amp;gt;&lt;/span&gt;/live&lt;span class="nt"&gt;&amp;lt;/mount-name&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;fallback-mount&amp;gt;&lt;/span&gt;/autodj&lt;span class="nt"&gt;&amp;lt;/fallback-mount&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;fallback-override&amp;gt;&lt;/span&gt;1&lt;span class="nt"&gt;&amp;lt;/fallback-override&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;max-listeners&amp;gt;&lt;/span&gt;250&lt;span class="nt"&gt;&amp;lt;/max-listeners&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;bitrate&amp;gt;&lt;/span&gt;128&lt;span class="nt"&gt;&amp;lt;/bitrate&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/mount&amp;gt;&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Define a second mount for &lt;code&gt;/autodj&lt;/code&gt; and point your AutoDJ source client at it. This one block is the difference between a listener staying tuned through a DJ logout and closing the player. It also mirrors what panels like Centova Cast and MediaCP generate for you under the hood, so writing it by hand once teaches you what those panels actually do. If you later outgrow hand-edited XML and want every customer station provisioned this way in one process, Lurcast handles mounts, fallbacks and per-station caps for you (see &lt;a href="https://www.lurcast.com/docs/getting-started" rel="noopener noreferrer"&gt;getting started&lt;/a&gt;).&lt;/p&gt;

&lt;h3&gt;
  
  
  Limits: clients, sources and burst size
&lt;/h3&gt;

&lt;p&gt;In the &lt;code&gt;&amp;lt;limits&amp;gt;&lt;/code&gt; block, set &lt;code&gt;&amp;lt;clients&amp;gt;&lt;/code&gt; to your listener-slot total plus headroom, &lt;code&gt;&amp;lt;sources&amp;gt;&lt;/code&gt; to the number of mounts you will actually run, and leave &lt;code&gt;&amp;lt;burst-size&amp;gt;&lt;/code&gt; at its default 65535 unless listeners on slow links report stutter. &lt;code&gt;&amp;lt;queue-size&amp;gt;&lt;/code&gt; and &lt;code&gt;&amp;lt;client-timeout&amp;gt;&lt;/code&gt; can stay at defaults for a first run.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you open the firewall and test that Icecast is running?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Testing with curl before opening a browser
&lt;/h3&gt;

&lt;p&gt;On Ubuntu or Debian with ufw, allow the port you bound in icecast.xml: &lt;code&gt;sudo ufw allow 8000/tcp&lt;/code&gt;, then &lt;code&gt;sudo ufw status&lt;/code&gt; to confirm. If you run raw iptables instead, add an ACCEPT rule for tcp/8000 on the INPUT chain before any DROP rule. Cloud VPS providers add a second layer: check the security group or firewall panel in your provider's dashboard and open 8000 there too, or local rules will not matter.&lt;/p&gt;

&lt;p&gt;Test locally first with &lt;code&gt;curl -I http://localhost:8000/status.xsl&lt;/code&gt;. A &lt;code&gt;200 OK&lt;/code&gt; means Icecast is up and binding correctly. Then repeat from your machine against the VPS public IP. If local works but remote fails, the problem is firewall or security group, not Icecast.&lt;/p&gt;

&lt;p&gt;When something breaks, read the logs: &lt;code&gt;/var/log/icecast2/error.log&lt;/code&gt; shows bind failures and config errors, and &lt;code&gt;access.log&lt;/code&gt; records every listener and source connection. If you outgrow hand-editing configs, Lurcast runs every station in one process and keeps your existing encoders and stats scripts (&lt;a href="https://www.lurcast.com/docs" rel="noopener noreferrer"&gt;https://www.lurcast.com/docs&lt;/a&gt;).&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you connect a source client like Liquidsoap or ezstream to your mount point?
&lt;/h2&gt;

&lt;p&gt;Icecast sits idle until a source client authenticates and pushes audio. Both clients need three values from your &lt;code&gt;icecast.xml&lt;/code&gt;: the source password, the server IP, and the mount name.&lt;/p&gt;

&lt;h3&gt;
  
  
  ezstream minimal config
&lt;/h3&gt;

&lt;p&gt;The &lt;a href="https://icecast.org/ezstream/" rel="noopener noreferrer"&gt;ezstream documentation&lt;/a&gt; shows the minimal shape: an &lt;code&gt;ezstream&lt;/code&gt; element with a &lt;code&gt;url&lt;/code&gt; of &lt;code&gt;http://127.0.0.1:8000/radio.mp3&lt;/code&gt;, a &lt;code&gt;sourcepassword&lt;/code&gt; matching your source password, a &lt;code&gt;format&lt;/code&gt; of MP3, and a &lt;code&gt;filename&lt;/code&gt; pointing at a playlist. Run &lt;code&gt;ezstream -c ezstream.xml&lt;/code&gt; and it streams on loop.&lt;/p&gt;

&lt;h3&gt;
  
  
  Liquidsoap output.liq example
&lt;/h3&gt;

&lt;p&gt;In Liquidsoap, one line does it: &lt;code&gt;output.icecast(%mp3, host="127.0.0.1", port=8000, password="hackme", mount="radio.mp3", playlist)&lt;/code&gt;. Reload the script and Liquidsoap reconnects automatically if the server drops.&lt;/p&gt;

&lt;p&gt;A successful connection shows &lt;code&gt;source&lt;/code&gt; entries in &lt;code&gt;/var/log/icecast2/error.log&lt;/code&gt; and your mount appearing at &lt;code&gt;http://your-ip:8000/radio.mp3&lt;/code&gt;. Failed auth logs a 401, which almost always means the source password, not the admin password.&lt;/p&gt;

&lt;p&gt;If you later host many stations, the same mount model applies; Lurcast documents its own integrations in &lt;a href="https://www.lurcast.com/docs/plugins" rel="noopener noreferrer"&gt;its plugin docs&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why is your Icecast server not reachable and how do you fix it?
&lt;/h2&gt;

&lt;p&gt;Three failures account for almost every dead first-run: the port is taken, the source password is wrong, or a firewall eats the traffic. Each one leaves a distinct fingerprint in the logs.&lt;/p&gt;

&lt;h3&gt;
  
  
  Port 8000 already in use
&lt;/h3&gt;

&lt;p&gt;If Icecast exits on startup or the status page never loads, check what holds the port with &lt;code&gt;ss -tlnp | grep 8000&lt;/code&gt;. Another Icecast instance, a panel-managed stream, or an unrelated service may already be bound. Either stop that process or change &lt;code&gt;&amp;lt;port&amp;gt;&lt;/code&gt; in &lt;code&gt;icecast.xml&lt;/code&gt; and restart.&lt;/p&gt;

&lt;h3&gt;
  
  
  401 on mount: source password mismatch
&lt;/h3&gt;

&lt;p&gt;A &lt;code&gt;401&lt;/code&gt; in the access log, or Liquidsoap and ezstream retrying in a loop, means the source client's password does not match &lt;code&gt;&amp;lt;source-password&amp;gt;&lt;/code&gt; in &lt;code&gt;icecast.xml&lt;/code&gt;. Remember the client sends &lt;code&gt;source:password&lt;/code&gt; as basic auth on the mount, so the username field in your source client is usually ignored. Fix the password, restart the client, and watch the log for the mount appearing.&lt;/p&gt;

&lt;h3&gt;
  
  
  Firewall and cloud security group blocks
&lt;/h3&gt;

&lt;p&gt;If the log shows Icecast listening but &lt;code&gt;curl http://YOUR_IP:8000&lt;/code&gt; times out from outside, packets are being dropped.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Symptom&lt;/th&gt;
&lt;th&gt;Likely cause&lt;/th&gt;
&lt;th&gt;Fix&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Connection refused locally&lt;/td&gt;
&lt;td&gt;Port already bound&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;ss -tlnp&lt;/code&gt;, stop or rebind&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;401 in access log&lt;/td&gt;
&lt;td&gt;Wrong source password&lt;/td&gt;
&lt;td&gt;Match &lt;code&gt;&amp;lt;source-password&amp;gt;&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Timeout from outside&lt;/td&gt;
&lt;td&gt;ufw or security group&lt;/td&gt;
&lt;td&gt;Open the port in both&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Check ufw with &lt;code&gt;sudo ufw status&lt;/code&gt;, and remember most VPS providers also apply a cloud security group you must edit separately.&lt;/p&gt;

&lt;h2&gt;
  
  
  What should you change from the default config before going live?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Passwords and hostname
&lt;/h3&gt;

&lt;p&gt;The stock icecast.xml ships with &lt;code&gt;hackme&lt;/code&gt; as the source and relay password and &lt;code&gt;changeme&lt;/code&gt;-style admin credentials. Replace all of them before you accept a single listener, and set &lt;code&gt;&amp;lt;hostname&amp;gt;&lt;/code&gt; to the DNS name your listeners will actually see, since it appears in generated playlist files and redirects. Change the &lt;code&gt;&amp;lt;admin&amp;gt;&lt;/code&gt; username too, and bind to your public IP rather than leaving &lt;code&gt;&amp;lt;listen-socket&amp;gt;&lt;/code&gt; on defaults if you run multiple services on the box.&lt;/p&gt;

&lt;h3&gt;
  
  
  Per-mount listener caps and fallbacks
&lt;/h3&gt;

&lt;p&gt;Set &lt;code&gt;&amp;lt;max-listeners&amp;gt;&lt;/code&gt; on every mount so a misbehaving source cannot eat all your listener slots, and configure &lt;code&gt;&amp;lt;fallback-mount&amp;gt;&lt;/code&gt; so a source dropout hands listeners to a dead-air file instead of an error page. If you resell slots by tier, caps per mount are the mechanism that keeps a 100-slot package from consuming a 500-slot server's capacity.&lt;/p&gt;

&lt;p&gt;For Liquidsoap sources, the Liquidsoap documentation documents the &lt;code&gt;output.icecast&lt;/code&gt; parameters you need: host, port, password, and mount.&lt;/p&gt;

&lt;p&gt;Finally, Icecast writes access and error logs that grow without limit. Add a logrotate rule for &lt;code&gt;access.log&lt;/code&gt; and &lt;code&gt;error.log&lt;/code&gt;, or a busy host will fill its disk within weeks.&lt;/p&gt;

&lt;h2&gt;
  
  
  When does plain Icecast stop being enough for a hosting provider?
&lt;/h2&gt;

&lt;p&gt;One Icecast process per customer station works until you are reselling Radio 100/250/500 listener-slot packages. Then provisioning, per-station caps, and monthly royalty reports become the job, and panel glue around Icecast becomes the fragile part.&lt;/p&gt;

&lt;h3&gt;
  
  
  A criteria checklist applied honestly to Icecast, AzuraCast and Lurcast
&lt;/h3&gt;

&lt;p&gt;Judge any alternative on four things: a provisioning API your WHMCS stack can call, per-station caps on listener slots and bitrate, royalty CSVs you can hand to accounting, and compatibility with the Icecast and SHOUTcast encoders, players and stats scripts you already run.&lt;/p&gt;

&lt;p&gt;Plain Icecast scores zero on the first three; it is a streaming server, not a host panel. AzuraCast gives you a full station stack but is built per-station, not as a multi-tenant host backend. Lurcast runs every station you host in one process, keeps your existing mounts, fallback streams and AutoDJ tooling, and ships the Hosting edition (€29 Growth, €59 Unlimited) for exactly this case. Run all three through the same checklist before you migrate anything.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Can I run Icecast and SHOUTcast on the same VPS?
&lt;/h3&gt;

&lt;p&gt;Yes, as long as each daemon binds to a different port. Icecast defaults to 8000, so give SHOUTcast another port like 8001 and open both in ufw and your provider's security group. Check for conflicts with ss -tlnp | grep 8000 before starting either service, and set &amp;lt;sources&amp;gt; in your limits block high enough to cover both.&lt;/p&gt;

&lt;h3&gt;
  
  
  How many listeners can Icecast handle on a 1 Gbps VPS?
&lt;/h3&gt;

&lt;p&gt;Do the bandwidth math: bitrate times listeners. At 128 kbps, 1 Gbps carries roughly 7,800 listeners in theory, so a 1 Gbps VPS is rarely the bottleneck for typical Radio 100/250/500 tiers. CPU and RAM are negligible; leave headroom above the raw number, since rebuffering and dead air cost you listeners faster than any config mistake.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does Icecast cost anything or need a license?
&lt;/h3&gt;

&lt;p&gt;No. Icecast is free open-source software, so the icecast2 package on Ubuntu or Debian costs nothing to run and has no license fees. What you pay for is the VPS itself and its bandwidth. Royalties for the music you stream are a separate obligation from the server software and are not handled by Icecast.&lt;/p&gt;

&lt;h3&gt;
  
  
  How do I put an AutoDJ behind Icecast so the stream never goes silent?
&lt;/h3&gt;

&lt;p&gt;Define two mounts: /autodj fed by a 24/7 source client like Liquidsoap or ezstream, and /live with a fallback-mount pointing at /autodj plus fallback-override set to 1. When your live DJ disconnects, listeners drop to AutoDJ automatically and move back when the live source returns. Point the AutoDJ client at the server IP, source password, and mount name.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why does my stream connect locally but not from outside the server?
&lt;/h3&gt;

&lt;p&gt;If curl &lt;a href="http://localhost:8000/status.xsl" rel="noopener noreferrer"&gt;http://localhost:8000/status.xsl&lt;/a&gt; returns 200 but the public IP times out, packets are being dropped, not misrouted by Icecast. Check ufw with sudo ufw status, and remember most VPS providers apply a separate cloud security group you must open in their dashboard. Both layers need tcp/8000 allowed before remote listeners can reach the mount.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Lurcast is an open-source (AGPL-3.0) internet radio streaming server, compatible with Icecast and SHOUTcast: &lt;a href="https://www.lurcast.com" rel="noopener noreferrer"&gt;lurcast.com&lt;/a&gt; · &lt;a href="https://github.com/Lurcast/lurcast" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>icecast</category>
      <category>linux</category>
      <category>selfhosted</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
