The signal chain, end to end
A mount point is the address of a single stream inside an Icecast server. The project documentation describes it as a unique name that looks like a filename, and notes that a listener can only follow one mount at a time. Your encoder pushes encoded audio to that name; Icecast relays it to everyone who opens the matching address.
Read a listen link from left to right and every part has a job:
| Part | Example | What it does |
|---|---|---|
| Scheme | http:// or https:// | How the player connects |
| Host | 192.0.2.23 | The Icecast server |
| Port | 8000 | The listen socket set in the server config |
| Mount | /mystream.ogg | Which stream on that server |
| Playlist suffix | .m3u | Optional; Icecast answers with a playlist file that opens most media players |
Because the mount is part of the address, one server can hold a talk channel, a music channel, or the same programme at two bitrates, each under its own name.
Settings to copy into your encoder
Your encoder needs the same five values every time, whichever program you use. Copy them exactly; one mistyped character can keep you off air.
| Encoder field | What goes in it | Notes |
|---|---|---|
| Server or address | The host name or IP | From the listen socket or your panel |
| Port | The listen port | Same number listeners use |
| Mount or mountpoint | The stream name | Type it exactly as the server or panel shows it |
| User | Usually source | Icecast's default unless the mount sets its own username |
| Password | The source password | Never the admin password |
Then set the audio side. The codec and bitrate you choose in the encoder decide what the mount carries, so pick them before you connect. In BUTT, for example, codec and bitrate sit in the Audio settings, apart from the server entry, and a Use SSL/TLS option connects only if the server supports it.
On a hosted station you do not invent these values: the control panel lists them for you.
Naming a mount so players behave
Icecast does not need to know a mount in advance: the first source to connect with a name creates it. A mount block in the config is only for giving that name its own limits, credentials or fallback. The naming rules come from how players guess the stream type:
- Ogg Vorbis streams should end in
.ogg, as in/mystream.ogg. - MP3 streams usually carry no extension, as in
/mystream. - No spaces and no unusual characters; many players handle them badly.
- One name per stream. A second bitrate is a second mount, not a setting on the first.
Fallback mounts: where listeners go when the source drops
A fallback mount is a second stream that Icecast moves listeners to when the source on their mount stops, or is not streaming when they arrive. Without one, those listeners are disconnected. Four settings govern it, all inside the mount's block:
| Setting | Effect |
|---|---|
fallback-mount | The mount (or a file in webroot) listeners move to; one per mount |
fallback-override | When enabled, a returning source pulls listeners back from the fallback |
fallback-when-full | Set to 1 to send new listeners to the fallback once max-listeners is reached |
max-listeners | The cap that triggers the line above |
The fallback must stream in the same format as the mount it covers. A fallback can name its own fallback, so listeners cascade down a chain. It can also be a pre-recorded file in webroot that repeats until the live stream returns; the documentation warns that such a file is not timed, so keep it off a master stream that relays feed from.
If the fallback is MP3 and the live mount is Ogg, listeners can run into playback problems at the handover. The Icecast documentation asks for the fallback to stream in the same format as the mount it covers, so encode them alike.
A mount block for your own server
If you run Icecast yourself, on a cloud server for instance, mount settings live in icecast.xml. This excerpt is taken from the mount example in the Icecast 2.4.1 configuration reference:
<mount type="normal">
<mount-name>/example-complex.ogg</mount-name>
<username>othersource</username>
<password>hackmemore</password>
<max-listeners>1</max-listeners>
<fallback-mount>/example2.ogg</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>1</fallback-when-full>
</mount>
Swap the sample password for a strong secret before the server faces the internet, and raise max-listeners from the example's 1. Only set a custom username if every encoder that uses the mount can send it.
- Make a backup copy of the working
icecast.xmlbefore you edit it, as the documentation advises. - Add or change the mount block.
- Check the syntax with
xmllint icecast.xmlin the folder that holds the file; a malformed file is the usual reason Icecast refuses to start. Go on only when it reports no errors. - Only then restart Icecast, at a quiet hour because a restart disconnects every listener and the encoder, and read
error.logfor the server-started line. If it does not start, put the backup copy back and restart again. - Connect the encoder, then open
/admin/stats.xmlwith the admin login: the mount should appear with its source attached.
Checks before you go live
- The mount in the encoder matches the panel or config character for character, including case.
- The username is
sourceunless the mount was given another. - The encoder holds the source password, not the admin password.
- Codec and bitrate in the encoder match what the mount and any fallback expect.
- The listen link plays in a browser on a phone and on a desktop.
- Disconnect the encoder once on purpose: listeners should land on the fallback, and if
fallback-overrideis on they return when you reconnect.
Confirm it worked by watching the listener count for the mount in the statistics while you play the link yourself; it should rise by one.
When it goes wrong
| Symptom | Likely cause | Fix |
|---|---|---|
| Encoder refused at login | Wrong user or password, or the admin password used | Use source and the source password |
| Encoder connects, link stays silent | Mount typed differently in encoder and link | Copy the name from one place to the other |
| Listeners cut off when the DJ leaves | No fallback, or the fallback is not streaming | Set fallback-mount and keep it fed |
| Playback fails or misbehaves on handover | Fallback in another format | Encode both in the same codec |
| Source removed after a stall | Encoder or its network sent no data within source-timeout | Check the encoder's connection; the limit sits in the limits section |
| New listeners sent elsewhere at peak | fallback-when-full with max-listeners reached | Raise the cap or accept the overflow stream |
Mount-level admin actions help here: /admin/listclients?mount=/mystream.ogg lists who is on a mount, and /admin/moveclients moves them to another. Both accept the admin login or that mount's own credentials, so keep the admin interface behind authentication.
How a hosted station handles this for you
On Get Stream Hosting SSL radio streaming the server side is ours: we run the servers, you run the programme. Every station broadcasts over HTTPS, so the player embeds on secure websites without warnings, and older players get a plain-http version of the same listen link. BUTT, Mixxx, SAM Broadcaster, RadioBOSS, OBS for audio and any Icecast or SHOUTcast source can feed it.
- Free: a single live stream, fed by whichever Icecast or SHOUTcast encoder you already use.
- Premium: AutoDJ steps aside when a live DJ connects and takes back over when they leave, while a fallback playlist covers any gap when nobody is connected, plus dead-air alerts.
- Platinum: three streams, letting phone listeners take a lighter bitrate, a backup source, and an encoder that connects to the nearest of five cities. Its encoder settings are in the control panel's Radio section.
Stuck on a field at the encoder? Support answers on live chat at any hour, and a human steps in when you request one; tickets work too.