icecastv2Independent technical reference

Independent, unofficial information portal

Guides

How an Icecast stream reaches its listeners

Understand source clients, mountpoints and listeners, choose a stream format, and locate faults along the complete Icecast signal path.

Version scope: Icecast 2.5.0Source review: 2026-10-23
On this page
  1. Follow one signal path
  2. Choose the media before the URL
  3. Find the broken connection

Icecast distributes a continuous media stream. It does not select music, mix a microphone or turn an audio file into several bitrates. Those jobs belong to a source client. Keeping this boundary clear makes both setup and troubleshooting much easier.

Follow one signal path

  1. A source client reads a file or capture device, encodes the media and opens a connection to Icecast.
  2. Icecast associates that incoming stream with a mountpoint such as /live.ogg.
  3. A listener requests the mountpoint. Icecast delivers the stream to that connection while the source continues sending data.

One server can carry several mountpoints. Two qualities of the same programme are still two streams and usually need two encoded feeds. A mountpoint is a URL path, not necessarily a file on disk. A <mount> configuration block adjusts its behaviour; it does not create an audio source.

Choose the media before the URL

Container, codec and MIME type must agree. Ogg can carry Vorbis or Opus; these are not names for the same encoding. The 2.5.0 README lists Ogg and WebM support, and describes MP3/AAC/NSV handling as legacy. Test the exact encoder and target players rather than interpreting a familiar filename extension as a compatibility guarantee.

IceS is a separate source application. Its version number does not identify the Icecast server release. libshout is a library used by source applications, not a replacement for either component.

Find the broken connection

If the administration statistics show no source for the expected mountpoint, investigate the encoder connection, credentials and source limit first. If the source exists but listeners cannot connect, check the requested path, listening address, network reachability and authentication. If audio starts and then stalls, inspect the source feed and listener delivery separately.

The server’s status page proves that an HTTP service responded. Only an active source plus actual playback proves that the complete media path works. Start with one local stream, then add relays or access controls after that baseline works.

Sources