similar to: Icecast Digest, Vol 175, Issue 6

Thanks for your offer to help. Do you mind if I email you at 0turn1 at gmail.com instead?... as I am no longer on facebook. > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190112/cadadb48/attachment-0001.html> > > ------------------------------ > > Message: 2 > Date:

Hi, thanks for your reply. So does that then mean that there is no inbuilt mechanism for forcing stream-name to display over mount-name? I run Liquidsoap with iceacst, and I know Liquidsoap is responsible for the artist and title metadata, but I thought that icecast handled the stream name side of things. Any clarification on this would be helpful. D On Tue Jan 8 14:29:21 UTC 2019 0turn1 at

Hi, This thread seems to have stalled. Would anyone still be able to help me with this one? I?ve posted my log as requested. Any advice would be a great help. > > Message: 1 > Date: Tue, 29 Jan 2019 20:00:21 +1000 > From: Damian <db76 at riseup.net> > To: icecast at xiph.org > Subject: Re: [Icecast] Icecast Digest, Vol 175, Issue 11 > Message-ID:

Hi, I apologise if this question has been asked and discussed before. If so, please just refer me to the relevant thread, as I am having a hard time finding the answer. I have noticed that on most Shoutcast streams that I have listened to using iTunes, the stream-name is displayed above the artist - title information. The artist - title information then rotates with the url of the stream. I

Good morning, On Sun, 2020-10-11 at 10:24 +1000, Damian wrote: > Can I also ask, which is the recommended course of action? Sure, just keep in mind that we had weekend, so people were off. ;) > Should I rebuild icecast with OpenSSL or is there now a fixed version > via backports that I can use? Based on... On Sat, 2020-10-10 at 23:06 +1000, Damian wrote: > Edit (apologies for the

Hi, I have been digging through the icecast mailing list archives trying to find out the meaning of this recurring message in my error.log [2018-05-01 19:50:16] EROR connection/_handle_connection Wrong request type from client [2018-05-01 19:50:16] EROR connection/_handle_connection Wrong request type from client [2018-05-01 19:50:16] INFO source/source_main listener count on /Systrum now 1

Apologies, one more question. With the edited icecast configuration I provided in my previous reply, netstat now shows the IPV6 binds but not the IPV4 binds. To your knowledge, does this seem correct? The Icecast server seems to be working properly and is accepting listener connections with IPV4 addresses. Just trying to understand why I don?t see 0.0.0.0:8000 for instance. -------------- next

Hi Philipp, Edit (apologies for the repeated emails) Thanks for the quick response. I’ve run the command and you can find the output by following this link https://systrum.net/output.txt <https://systrum.net/output.txt> I'm running icecast with SSL enabled. I needed a a version of Icecast with SSL support which is why I am using the backports version. Regards Damian -------------- next

Hi, needing some advice. I am running a backports version of icecast for Debian 10. I have found that with this version, the icecast server will usually run for about 7 days before it crashes. I found in the syslog that icecast gets terminated because it?s 'out of memory'. This never happened on the standard (stable) version of icecast that I ran on Debian 9 installed via apt. I?ve added

I would like to know how I can setup icecast with autodj? On Tue, 17 Jan 2023, 21:51 Damian, <db76 at riseup.net> wrote: > Hi, > > I would like to know whether Icecast version 2.4.4 supports IPV6 listener > connections? I have some mobile phone users that connect to my web server > with an IPV6 address but then connect to the Icecast server via IPV4. I > assume that IPV6

Thanks for clarifying that Philipp. Yeah, I compared the time stamps in the error.log and access.log (below) and saw the corresponding HEAD requests. I've been getting a lot of these so I thought that there was something I could do to allow these clients to connect to the stream. I guess I just need to ignore them. Thanks Damian Snippet from error.log [2018-05-04 00:28:17] EROR

I see. However, it is often pretty easy to see that a duplicate connection is the same listener because the time connected to the server of the two connections is the same. In that case, I am wondering which would be the one to kick. > On 22 Dec 2019, at 23:39, Gavin Stephens <gavin at stephens.net.nz> wrote: > > With NAT, also with carrier grade NAT becoming more poplular with

Good morning, On Fri, 2023-01-20 at 12:28 +0000, Coolvibes Reloaded wrote: > I would like to know how I can setup icecast with autodj? How is that related to this thread? > On Tue, 17 Jan 2023, 21:51 Damian, <db76 at riseup.net> wrote: > > Hi, > > > > I would like to know whether Icecast version 2.4.4 supports IPV6 > > listener connections? I have some

Because it's icecast I would like to know how to use icecast with autodj please On Fri, 20 Jan 2023, 12:33 Philipp Schafft, <phschafft at de.loewenfelsen.net> wrote: > Good morning, > > On Fri, 2023-01-20 at 12:28 +0000, Coolvibes Reloaded wrote: > > I would like to know how I can setup icecast with autodj? > > How is that related to this thread? > > >

On 20 Jul 2020, at 1:12, Damian wrote: > I solved the issue by adding my own m3u files to > /usr/share/icecast/web but I am not sure if this is icecast > best-practice. This also raises a few other issues as well… http > stream links don’t appear on the icecast stream directory and stream > titles and track metadata does not display when opening m3u files > created in this

Hi again, I apologise for my persistence with this. Perhaps my last question has already been answered in another thread. If so, could anyone please point me to it. Just needing to know how to enable Icecast as a service on Debian when installed from source. The option to enable it isn?t in the same directory (/etc/default/icecast) as when using apt-get install D > On 7 Feb 2019, at 10:28

With NAT, also with carrier grade NAT becoming more poplular with ISP's yet to move to IPv6, if you have a very popular stream you could end up kicking valid listners behind the same IP. On 23 December 2019 2:18:35 AM NZDT, Damian <db76 at riseup.net> wrote: >Hello fellow mailing list readers, > >My question relates to multiple / duplicate connections to the ice cast

I solved the issue by adding my own m3u files to /usr/share/icecast/web but I am not sure if this is icecast best-practice. This also raises a few other issues as well… http stream links don’t appear on the icecast stream directory and stream titles and track metadata does not display when opening m3u files created in this way. I assume that there are various reasons for this…mainly that https

Actually, I think I found the answer. On Linux, binding to [::] (IPv6) results in receiving both IPv6 and IPv4 traffic (by default). These are referred to as IPv4-mapped IPv6 addresses. Netstat simply shows the IPv6 entry only, because there's technically only a single bind, that happens to support both IPv4 and IPv6. > On 20 Jan 2023, at 21:47, Damian <db76 at riseup.net> wrote:

Good morning, first of all, thank you for your nice report. :) On Sat, 2020-10-10 at 20:32 +1000, Damian wrote: > Hi, needing some advice. > I am running a backports version of icecast for Debian 10. I have > found that with this version, the icecast server will usually run for > about 7 days before it crashes. I found in the syslog that icecast > gets terminated because it?s