Icecast-Server issueshttps://gitlab.xiph.org/xiph/icecast-server/-/issues2018-03-06T12:49:48Zhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1421RFE: Optional IceCast Authenticator Assistant2018-03-06T12:49:48ZianRFE: Optional IceCast Authenticator AssistantIn status.xsl, present the authenticator login link (the lock) based on need for authentication. Otherwise, present the usual M3U, XSPF links.
If authentication uses htpasswd, always show the lock.
If authentication uses URL, only show...In status.xsl, present the authenticator login link (the lock) based on need for authentication. Otherwise, present the usual M3U, XSPF links.
If authentication uses htpasswd, always show the lock.
If authentication uses URL, only show the lock if the listener_add option is defined.Michael SmithMichael Smithhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1417icecast server binds to random ports2018-03-06T12:49:48ZGitlab Boticecast server binds to random portsIcecast version 2.3.2, compiled for Linux, x86_64 on Fedora 9 (from the src rpm supplied on icecast.org)
Every time icecast is started, the server binds to a random port. Port 8090 is specified in icecast.xml (see attached file).
[Ou...Icecast version 2.3.2, compiled for Linux, x86_64 on Fedora 9 (from the src rpm supplied on icecast.org)
Every time icecast is started, the server binds to a random port. Port 8090 is specified in icecast.xml (see attached file).
[Output is attached as a file to circumvent aggressive "too many external links" trac submission problem]
Icecast 2.3Karl HeyesKarl Heyeshttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1416icecast server binds to random ports2018-03-06T12:49:48ZGitlab Boticecast server binds to random portsIcecast version 2.3.2, compiled for Linux, x86_64 on Fedora 9 (from the src rpm supplied on icecast.org)
Every time icecast is started, the server binds to a random port. Port 8090 is specified in icecast.xml (see attached file).
Sam...Icecast version 2.3.2, compiled for Linux, x86_64 on Fedora 9 (from the src rpm supplied on icecast.org)
Every time icecast is started, the server binds to a random port. Port 8090 is specified in icecast.xml (see attached file).
Sample output:
```
[root@chrome ~]# service icecast restart
Shutting down icecast streaming daemon: [ OK ]
Starting icecast streaming daemon: [ OK ]
[root@chrome ~]# netstat -tlp | grep icecast
tcp 0 0 chrome.hoover.:8090 *:* LISTEN 30033/icecast
tcp 0 0 chrome.hoover.:8091 *:* LISTEN 30033/icecast
[root@chrome ~]# service icecast restart
Shutting down icecast streaming daemon: [ OK ]
Starting icecast streaming daemon: [ OK ]
[root@chrome ~]# netstat -tlp | grep icecast
tcp 0 0 chrome.hoover.:8090 *:* LISTEN 30119/icecast
tcp 0 0 chrome.hoover.:8091 *:* LISTEN 30119/icecast
```
Icecast 2.3Michael SmithMichael Smithhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1388Report the mountpoint in log lines2018-03-06T12:49:48Zrich_d_thomasReport the mountpoint in log linesHi,
This enhancement request is as a result of discussion thread http://icecast.imux.net/viewtopic.php?t=5336&highlight=
Please could icecast be enhanced, so the lines that are written to the log file include the relevant mountpoint na...Hi,
This enhancement request is as a result of discussion thread http://icecast.imux.net/viewtopic.php?t=5336&highlight=
Please could icecast be enhanced, so the lines that are written to the log file include the relevant mountpoint name (where available) that is being logged.
Thank you.Icecast 2.5.0Thomas B. RückerThomas B. Rückerhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1359[PATCH] <stream-name> config to completely override stream name2018-03-06T12:49:48Zrich_d_thomas[PATCH] <stream-name> config to completely override stream nameHi,
This enhancement request is as a result of discussion thread http://icecast.imux.net/viewtopic.php?t=5033
Please could the code be changed so that all aspects of the "stream name" is overwritten by the contents of the <stream-name>...Hi,
This enhancement request is as a result of discussion thread http://icecast.imux.net/viewtopic.php?t=5033
Please could the code be changed so that all aspects of the "stream name" is overwritten by the contents of the <stream-name> tag in the config.xml file.
Currently, <stream-name> sets what appears in the displayed status.xsl page. The stream name that appears in the listener's player is still what is set in the source client and not what is set in <stream-name>
Thank you.
rich_d_thomas@hotmail.com
Icecast 2.4.0Thomas B. RückerThomas B. Rückerhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1354pass stream_name and stream_description to on-dis/connect scripts2018-03-06T12:49:48Zrich_d_thomaspass stream_name and stream_description to on-dis/connect scriptsHi,
I notice that the name of the mount point is already passed as an argument to the <on-disconnect> and <on-connect> scripts.
Please could the stream_name and stream_description be passed as additional arguments to these scripts.
Th...Hi,
I notice that the name of the mount point is already passed as an argument to the <on-disconnect> and <on-connect> scripts.
Please could the stream_name and stream_description be passed as additional arguments to these scripts.
Thanks in advance.
rich_d_thomas@hotmail.comIcecast 2.5.0Thomas B. RückerThomas B. Rückerhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1345icecast 2x crashes sometimes no y pages2018-03-06T12:49:48ZGitlab Boticecast 2x crashes sometimes no y pagesicecast crashes now and then have to reboot somes that donot work
xiph y pages not working
icecast crashes now and then have to reboot somes that donot work
xiph y pages not working
Icecast 2.3Karl HeyesKarl Heyeshttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1337dump-file based on meta-data/timestamp info2018-03-06T12:49:48ZGitlab Botdump-file based on meta-data/timestamp infoHi,
This enhancement request is as a result of discussion thread http://icecast.imux.net/viewtopic.php?t=1140
There are a number of users, myself included, that would like the dump filename to be set to the "Stream Title" and "Stream D...Hi,
This enhancement request is as a result of discussion thread http://icecast.imux.net/viewtopic.php?t=1140
There are a number of users, myself included, that would like the dump filename to be set to the "Stream Title" and "Stream Description" of what is being dumped. Each time a source disconnects and re-connects, the dump file is re-opened, so upon re-connection, if the source has a different title or description, the dump filename will be different.
This is similar to Ticket #663 "Icecast dump-file trigger", as I believe that if the dump name follows the stream title and description, the user that raised that enhancement would achieve what he wanted too.
What would be even better once that has been done, is to write ID3 tags into mp3 dump files each time a new mp3 dump file is created.
Please could this enhancement be considered.
Thanks in advance,
rich_d_thomas@hotmail.comIcecast 2.3Michael SmithMichael Smithhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1325WTF?2018-03-06T12:49:48ZGitlab BotWTF?error message sucks because it doesn't provide any hint about what the user should do to fix it..
hence:
configure: error: XSLT configuration could not be found <--- Could you please give me an idea of what I need to do here?error message sucks because it doesn't provide any hint about what the user should do to fix it..
hence:
configure: error: XSLT configuration could not be found <--- Could you please give me an idea of what I need to do here?Icecast 2.3Michael SmithMichael Smithhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1323Incorrect build instructions in icecast README2018-03-06T12:49:48ZMonty MontgomeryIncorrect build instructions in icecast README...don't forget to update the Icecast README to reflect proper build instruction now that it's automake'd. It's confused a few users this week....don't forget to update the Icecast README to reflect proper build instruction now that it's automake'd. It's confused a few users this week.Michael SmithMichael Smithhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1310fallback-override not honored for fallback defined via HTTP request2018-03-06T12:49:48Zleefallback-override not honored for fallback defined via HTTP requestIcecast 2.3.1 Debian Etch.
fallback-override not honored for fallback defined via HTTP request
"/" is defined in server XML as a static mountpoint with a fallback of "/live-2.mp3" and fallback-override enabled. If source disconnects, c...Icecast 2.3.1 Debian Etch.
fallback-override not honored for fallback defined via HTTP request
"/" is defined in server XML as a static mountpoint with a fallback of "/live-2.mp3" and fallback-override enabled. If source disconnects, clients are moved to "/live-2.mp3" as expected. When source reconnects, clients are moved to "/", also as expected.
When a HTTP request is given to change the fallback of "/" to "/live-1.mp3", server reports success. When source is disconnected, clients are moved to "/live-1.mp3". When new clients connect to "/", they are moved to "/live-2.mp3", when the expectation is to move them to "/live-1.mp3". When source reconnects clients are not moved back to "/". Clients must be manually moved back to "/" via a HTTP request.Icecast 2.3Michael SmithMichael Smithhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1309Server does not move new listeners to fallback source if specified via HTTP r...2018-03-06T12:49:48ZleeServer does not move new listeners to fallback source if specified via HTTP requestIcecast server 2.3.1 in Debian Etch
Server does not move new listeners to fallback source if specified via HTTP request. I have two examples of this not functioning as expected:
1) Listeners are connected to a mountpoint named "/". "/"...Icecast server 2.3.1 in Debian Etch
Server does not move new listeners to fallback source if specified via HTTP request. I have two examples of this not functioning as expected:
1) Listeners are connected to a mountpoint named "/". "/" has no fallback defined in server XML. An HTTP request to define a fallback is issued, in my case it looks like this:
http://ash.rockingtiger.com:8000/admin/fallbacks?mount=/&fallback=/live-1.mp3
When source disconnects, current listeners are moved to "/live-1.mp3" as expected. When a new listener connects to "/" the client (in this case iTunes) is given a 404. My expectation was the new clients that connect to "/" be moved to "/live-1.mp3" the same way the old clients were moved.
2) Listeners are connected to "/". "/" has a fallback of "/live-2.mp3" defined. An HTTP request to define a fallback is issued, in my case it looks like this:
http://ash.rockingtiger.com:8000/admin/fallbacks?mount=/&fallback=/live-1.mp3
When source disconnects, current listeners are moved to "/live-1.mp3" as expected. New clients that connect to "/" are moved to "/live-2.mp3", not "/live-1.mp3" as expected.Karl HeyesKarl Heyeshttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1296Freeze Metadata2018-11-08T14:02:57ZGitlab BotFreeze Metadatait will be cool if i can myself determine artist or title that will be seen in winamp while streaming it can be done for example
<mount>
<mount-name>/Mount</mount-name>
<password>password</password>
<artist-name>...it will be cool if i can myself determine artist or title that will be seen in winamp while streaming it can be done for example
<mount>
<mount-name>/Mount</mount-name>
<password>password</password>
<artist-name> Artist name </artist-name>
</mount>
and in winamp i will see "Artist name" (current song that is playing) it is very usefull when u don`t want listeners to see names of tracks and ur streaming program can`t off sending metadata for example virtual dj or tractor
Icecast 2.5.0Thomas B. RückerThomas B. Rückerhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1276Windows server crashed by auth users2018-03-06T12:49:49ZaluigiWindows server crashed by auth users
Hey,
seems to exist a problem in the Windows version.
In short the GUI is not able to handle a number of events/stats (those visible in the right list in "Source Level Stats") major or equal than 15.
Only the authenticated SOURCE users...
Hey,
seems to exist a problem in the Windows version.
In short the GUI is not able to handle a number of events/stats (those visible in the right list in "Source Level Stats") major or equal than 15.
Only the authenticated SOURCE users can exploit this problem which has the only effect of a crash (access to the address pointed by EAX which is 1).
For testing the problem is enough to send the following pre-build request (the source password here is sourcepass) to port 8000 of the server:
SOURCE /stream.ogg ICE/1.0
content-type: application/ogg
Authorization: Basic c291cmNlOnNvdXJjZXBhc3M=
ice-audio-info: 0=a;1=a;2=a;3=a;4=a;5=a;6=a;7=a;8=a;9=a;10=a;11=a;12=a;13=a;14=a;15=a
Icecast 2.3Michael SmithMichael Smithhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1273<relay> ignores <authentication> elements2018-03-06T12:49:48Zmuelli<relay> ignores <authentication> elementsIf you just relay streams and want users to authenticate in order to get the stream, I'd expect to extend my <relay> definition by a `<authentication type="">` stanza. However, this does not work.
A rather counter-intuitive solution is...If you just relay streams and want users to authenticate in order to get the stream, I'd expect to extend my <relay> definition by a `<authentication type="">` stanza. However, this does not work.
A rather counter-intuitive solution is to set up a `<mount>` with the same name and define authentication there.
I'd expect an `<authentication>` inside a `<relay>` to work.
Example configuration which I expected to work:
```
<relay>
<server>some.server.net</server>
<port>8000</port>
<mount>/remotemount</mount>
<local-mount>/relay-auth</local-mount>
<on-demand>1</on-demand>
<relay-shoutcast-metadata>1</relay-shoutcast-metadata>
<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="auth_header" value="icecast-auth-user: 1"/>
<option name="listener_remove" value="http://myauthserver.net/notify_listener.php"/>
</authentication>
</relay>
```Michael SmithMichael Smithhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1272Moving clients on authentication failure2020-10-18T16:15:17ZmuelliMoving clients on authentication failureI want to move a client if she didn't pass my url authentication.
e.g.
```
<mount>
<mount-name>/mount</mount-name>
<authentication type="url">
<option name="mount_add" value="http://some/url"/>
...I want to move a client if she didn't pass my url authentication.
e.g.
```
<mount>
<mount-name>/mount</mount-name>
<authentication type="url">
<option name="mount_add" value="http://some/url"/>
<option name="mount_remove" value="http://some/url"/>
<option name="listener_add" value="http://some/url"/>
<option name="listener_remove" value="http://some/url"/>
<option name="auth_header" value="icecast-auth-user: 1"/>
</authentication>
<!-- 1st example. Moving to other mount -->
<on-authentication-failure>/othermount</on-authentication-failure>
<!-- 2nd example. Playing pre-recorded file -->
<on-authentication-failure>/sorry.ogg</on-authentication-failure>
<!-- 3rd example. Firstplaying pre-recorded file, then play the stream anyway (or move to other mount) -->
<on-authentication-failure>sorry.ogg+/othermount</on-authentication-failure>
</mount>
```
Especially the 3rd example looks difficult, but I'd say it's a legitimate use-case to tell the listener that she didn't authenticate properly and is now getting e.g. a lower quality stream.Philipp SchafftPhilipp Schaffthttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1271missing comprehensive list of configuration directives2018-03-06T12:49:48Zmuellimissing comprehensive list of configuration directivesI just wanted to lookup the semantic of a configuration directive and couldn't find it easily. A comprehensive list like on http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives would be nice.I just wanted to lookup the semantic of a configuration directive and couldn't find it easily. A comprehensive list like on http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives would be nice.Karl HeyesKarl Heyeshttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1249Misleading documentation2018-03-06T12:49:48ZmarkusMisleading documentationThe installation documentation (e.g. "basicsetup") should make clear that it does not apply to icecast server packaged by different distributions. For example the binary name in Debian (and variants) is not icecast but icecast2, and pref...The installation documentation (e.g. "basicsetup") should make clear that it does not apply to icecast server packaged by different distributions. For example the binary name in Debian (and variants) is not icecast but icecast2, and preferred way to start it is to use packaged init scripts instead of the binary name. Distribution specific documentation doesn't need to be supplied by you, but imo you should modify the documentation so that it clearly states that the documentation found on icecast web pages is not directly applicable on most commonly used linux distributions where the software is installed through package management software.Icecast 2.3Thomas B. RückerThomas B. Rückerhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1246Icecast Server enforcing case sensitivity on HTTP header Range "bytes" units2018-03-06T12:49:48ZGitlab BotIcecast Server enforcing case sensitivity on HTTP header Range "bytes" unitsClients making requests from Icecast 2.3.1 server with HTTP Range header using units "bytes" with any casing other then all lowercase fail request with:
```
HTTP/1.0 416 Request Range Not Satisfiable
```
It is expected that the HTTP Ra...Clients making requests from Icecast 2.3.1 server with HTTP Range header using units "bytes" with any casing other then all lowercase fail request with:
```
HTTP/1.0 416 Request Range Not Satisfiable
```
It is expected that the HTTP Range header should be case insensitive on "bytes"
W3C rfc2616 HTTP 1.1 sec 2.1 (http://www.w3.org/Protocols/rfc2616/rfc2616-sec2.html#sec2.1) states about BNF literals "Unless stated otherwise, the text is case-insensitive."
Section 3.12 (http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.12) which defines the Range units defines "bytes", but does not specify case sensitivity.
Here is an example localhost request/response against an icecast 2.3.1 server with Range units as "Bytes":
```
REQUEST: **************\n
GET /TheBeginning.mp3 HTTP/1.1\r\n
Range: Bytes=0-\r\n
Host: localhost\r\n
Accept: */*\r\n
\r\n
RESPONSE: **************\n
HTTP/1.0 416 Request Range Not Satisfiable\r\n
\r\n
```
Here is an example localhost request/response against an icecast 2.3.1 server with Range units as "bytes" (data truncated):
```
REQUEST: **************\n
GET /TheBeginning.mp3 HTTP/1.1\r\n
Range: bytes=0-\r\n
Host: localhost\r\n
Accept: */*\r\n
\r\n
RESPONSE: **************\nHTTP/1.1 206 Partial Content\r\n
Date: Wed, 10-Oct-2007 19:29:28 GMT\r\n
Content-Length: 7064799\r\n
Content-Range: bytes 0-7064798/7064799\r\n
Content-Type: audio/mpeg\r\n
\r\n
ID3\x002\x000\x000\x000\x000\x010BTT2\x000\x000\x00F\x000The Beginning
```
Here is an example localhost request/response against an Apache 1.3.37 (Unix) server with Range units as "Bytes" (data truncated):
```
REQUEST: **************\n
GET http://www.foldedspace.org:80/files/vintage/Nipper's%20Greatest%20Hits_%201901-1920/17%20Come%20Josephine%20In%20My%20Flying%20Machine.mp3 HTTP/1.1\r\n
Range: Bytes=0-\r\n
Host: www.foldedspace.org\r\n
Accept: */*\r\n
\r\n
RESPONSE: **************\nHTTP/1.1 206 Partial Content\r\n
Connection: Keep-Alive\r\n
Content-Length: 2411015\r\n
Date: Wed, 10 Oct 2007 23:31:58 GMT\r\n
Content-Range: bytes 0-2411014/2411015\r\n
Content-Type: audio/mpeg\r\n
ETag: "63dc404-24ca07-4459501b"\r\n
Server: Apache/1.3.37 (Unix) mod_throttle/3.1.2 DAV/1.0.3 mod_fastcgi/2.4.2 mod_gzip/1.3.26.1a PHP/4.4.7 mod_ssl/2.8.22 OpenSSL/0.9.7e\r\n
Last-Modified: Thu, 04 May 2006 00:51:39 GMT\r\n
Accept-Ranges: bytes\r\n
Keep-Alive: timeout=2, max=100\r\n
\r\n
ID3\x002\x000\x000\x000\x000\x012\x002TT2\x000\x000%\x000Come Josephine In My Flying Machine
```
Here is an example localhost request/response against an IIS 6.0 server with Range units as "Bytes" (data truncated):
```
REQUEST: **************\n
GET http://kuow.org:80/mp3high/mp3/WeekdayA/WeekdayA20071010.mp3 HTTP/1.1\r\n
Range: Bytes=0-\r\n
Host: kuow.org\r\n
Accept: */*\r\n
\r\n
RESPONSE: **************\n
HTTP/1.1 206 Partial Content\r\n
Connection: Keep-Alive\r\n
Content-Length: 25918483\r\n
Date: Wed, 10 Oct 2007 23:26:17 GMT\r\n
Content-Range: bytes 0-25918482/25918483\r\n
Content-Type: audio/mpeg\r\n
ETag: "449237ff5ebc81:2a4"\r\n
Server: Microsoft-IIS/6.0\r\n
Last-Modified: Wed, 10 Oct 2007 17:00:01 GMT\r\n
Accept-Ranges: bytes\r\n
X-Powered-By: ASP.NET\r\n
\r\n
√P╚\x000\x000\x000\x000\x000\x000\x000\x000\x000\x000\x000\x000\x000\x000\x000\x000\x000Info
```
Icecast 2.3Michael SmithMichael Smithhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1233icecast loops listener count to full2018-03-06T12:49:48ZGitlab Boticecast loops listener count to fullThe broblem occurs when streaming theora video with ffmpeg2theora and ezstream. Ezstream connects to icecast, but ffmpeg2theora don't send headers.(?) Status page shows only mountpoint information, nothing other.
After this like stream...The broblem occurs when streaming theora video with ffmpeg2theora and ezstream. Ezstream connects to icecast, but ffmpeg2theora don't send headers.(?) Status page shows only mountpoint information, nothing other.
After this like stream goes up and someone opens stream (ie. relaying icecast) this bug is activating. Same listener is added to clients list untill server is full.
Error log is like this:
```
[2007-08-30 01:34:34] DBUG source/source_main Client added
[2007-08-30 01:34:34] DBUG source/source_main Client added
[2007-08-30 01:34:34] DBUG source/source_main Client added
[2007-08-30 01:34:34] DBUG source/source_main Client added
[2007-08-30 01:34:34] DBUG source/source_main Client added
[2007-08-30 01:34:34] DBUG source/source_main Client added
[2007-08-30 01:34:34] DBUG source/source_main Client added
```
.... and continues to max listeners count of server.
Karl HeyesKarl Heyes