icecastv2Independent technical reference

Independent, unofficial information portal

Guides

Install Icecast and identify the actual version

Choose a distribution package or official source release, identify the installed Icecast version and locate its configuration and service files.

Version scope: Icecast 2.5.0Source review: 2026-10-23
On this page
  1. Use a distribution package
  2. Build a specific upstream release
  3. Prove the installation, then configure it

Choose the installation route before copying configuration paths. Distribution packages integrate with their operating system; a build installed under a private prefix has different files and a different maintenance path. Neither route guarantees the same version as an upstream download.

Use a distribution package

For Debian, inspect the package offered by the configured repositories before installing it:

sh · Code example
apt-cache policy icecast2
sudo apt install icecast2
dpkg-query -W icecast2
dpkg -L icecast2

These are Debian commands, not portable instructions for every Linux distribution. At the source check, Debian stable’s package page listed 2.4.4 while upstream offered 2.5.0. Distribution patches and upstream support are separate facts. Use the article examples for the version actually installed and read the distribution’s service configuration.

The package file list tells you where icecast.xml, web assets and administration transforms were installed. Do not assume /usr/local/etc when the package uses /etc/icecast2. If a service already runs, inspect it before launching a second process on the same port.

Build a specific upstream release

Download the desired archive from the official project. Record its name and checksum, extract it into a working directory, and read its README. For 2.5.0 the prerequisites include libxml2, libxslt, libogg/libvorbis, libigloo and librhash. Development headers are needed when compiling; runtime libraries alone may not suffice. curl enables URL authentication and directory interaction.

From the extracted release directory, this is the upstream build sequence with a deliberately private installation prefix:

sh · Code example
./configure --prefix="$HOME/icecast-local"
make
make install

Here $HOME/icecast-local is your own chosen test location, not a system-wide installation. A release archive already contains configure; a Git checkout has an additional bootstrap and submodule workflow. Do not mix files from these routes or run the server as root merely because an old example used a privileged install command.

Prove the installation, then configure it

Check the selected executable’s help/version information and the startup log. Record the package or archive origin together with the runtime version. A successful compile does not prove TLS support, a running service or working audio. Next, prepare a bounded first-stream test.

Sources