[Icecast] multiple instances?
Thomas B. Rücker
thomas at ruecker.fi
Mon Sep 9 12:33:55 UTC 2019
On 9/9/19 11:35 AM, wilderzone.radio.2 wrote:
> Hello, unosonic,
> Okay, we'll do it this way as it appears to be the only sane way...
> THIS is the xml config file that I've been using for ONE STREAM ONLY.
> No more than one stream nor any other port on that single stream, for that matter, has ever worked to date.
> There also seems to be alot of clutter but as I've NEVER had to use these oddball format files before (in any of my 30 plus years in computers),
XML is not really a very human friendly format, despite being
"readable". Unfortunately this is what was chosen for the Icecast
configuration. Also I have yet to see a configuration file format that
satisfies "human readable", "easy", "allows defining complex use cases".
> I can't tell what is a working line and what is just geek-babble.
I'd strongly recommend installing notepad++ for editing the file. It's a
simple but very helpful editor. It will give you color hilighting for
the sections. That makes it easy to see which parts will be ignored
(instead of looking for <!-- --> bracketing manually)
> <!-- This is the hostname other people will use to connect to your server.
> It affects mainly the urls generated by Icecast for playlists and yp
> listings. You MUST configure it properly for YP listings to work!
> <!-- location and admin are two arbitrary strings that are e.g. visible
> on the server info page of the icecast web interface
> (server_version.xsl). -->
> <location>Sol III</location>
> <admin>icemaster at localhost</admin>
> <!-- You may have multiple <listener> elements -->
> <!-- <bind-address>127.0.0.1</bind-address> -->
> <!-- <shoutcast-mount>/rock</shoutcast-mount> -->
> <!-- IMPORTANT!
> Especially for inexperienced users:
> Start out by ONLY changing all passwords and restarting Icecast.
> For detailed setup instructions please refer to the documentation.
> It's also available here: http://icecast.org/docs/
Beware, you are limiting the Icecast server to TWO active mountpoints.
If you try a third connection it will fail.
> <!-- If enabled, this will provide a burst of data when a client
> first connects, thereby significantly reducing the startup
> time for listeners that do substantial buffering. However,
> it also significantly increases latency between the source
> client and listening client. For low-latency setups, you
> might want to disable this. -->
> <!-- same as burst-on-connect, but this allows for being more
> specific on how much to burst. Most people won't need to
> change from the default 64k. Applies to all mountpoints -->
> <!-- Sources log in with username 'source' -->
> <!-- Relays log in with username 'relay' -->
> <!-- Admin logs in with the username given below -->
I hope that's not your real password. In case it is, please change it.
> <!-- set the mountpoint for a shoutcast source to use, the default if not
> specified is /stream but you can change it here if an alternative is
> wanted or an extension is required
> <!-- Uncomment this if you want directory listings -->
> <!-- Global header settings
> Headers defined here will be returned for every HTTP request to Icecast.
> The ACAO header makes Icecast public content/API by default
> This will make streams easier embeddable (some HTML5 functionality needs it).
> Also it allows direct access to e.g. /status-json.xsl from other sites.
> If you don't want this, comment out the following line or read up on CORS.
> <header name="Access-Control-Allow-Origin" value="*" />
> <!-- Relaying
> You don't need this if you only have one server.
> Please refer to the config for a detailed explanation.
> <!-- setting this makes all relays on-demand unless overridden, this is
> useful for master relays which do not have <relay> definitions here.
> The default is 0 -->
> <!-- Mountpoints
> Only define <mount> sections if you want to use advanced options,
> like alternative usernames or passwords
> <!-- Default settings for all mounts that don't have a specific <mount type="normal">.
> <mount type="default">
> <authentication type="url">
> <option name="mount_add" value="http://auth.example.org/stream_start.php"/>
> <header name="foo" value="bar" />
> <!-- Normal mounts -->
> <mount type="normal">
> <authentication type="htpasswd">
> <option name="filename" value="myauth"/>
> <option name="allow_duplicate_users" value="0"/>
> <header name="Access-Control-Allow-Origin" value="http://webplayer.example.org" />
> <header name="baz" value="quux" />
> <mount type="normal">
> <authentication type="url">
> <option name="mount_add" value="http://myauthserver.net/notify_mount.php"/>
> <option name="mount_remove" value="http://myauthserver.net/notify_mount.php"/>
> <option name="listener_add" value="http://myauthserver.net/notify_listener.php"/>
> <option name="listener_remove" value="http://myauthserver.net/notify_listener.php"/>
> <option name="headers" value="x-pragma,x-token"/>
> <option name="header_prefix" value="ClientHeader."/>
> <!-- Aliases: treat requests for 'source' path as being for 'dest' path
> May be made specific to a port or bound address using the "port"
> and "bind-address" attributes.
> <alias source="/foo" destination="/bar"/>
> <!-- Aliases: can also be used for simple redirections as well,
> this example will redirect all requests for http://server:port/ to
> the status page
> <alias source="/" destination="/status.xsl"/>
> <!-- The certificate file needs to contain both public and private part.
> Both should be PEM encoded.
> <!-- <playlistlog>playlist.log</playlistlog> -->
> <loglevel>3</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
> <logsize>10000</logsize> <!-- Max size of a logfile -->
> <!-- If logarchive is enabled (1), then when logsize is reached
> the logfile will be moved to [error|access|playlist].log.DATESTAMP,
> otherwise it will be moved to [error|access|playlist].log.old.
> Default is non-archive mode (i.e. overwrite)
> <!-- <logarchive>1</logarchive> -->
As already pointed out by Unosonic, there is currently no defined
<mount>. Connecting using the source-password will make it appear on the
fly, but there are no special settings applied.
You can create mountpoints by adding the earlier mentioned sections. The
only important thing is that this must be outside of sections enclosed
by <!-- -->.
More information about the Icecast