From ross at stationplaylist.com  Sun Mar  1 00:02:45 2020
From: ross at stationplaylist.com (Ross Levis)
Date: Sun, 1 Mar 2020 13:02:45 +1300
Subject: [Icecast] Chrome not allowing mixed content anymore
In-Reply-To: <CAOx_OQ8t6rfdfX0ng_6OSuGhnQEvPnJVrmkW-whLh-X2d-PLJA@mail.gmail.com>
References: <CACg6BWLz7FE4Vc9rCnqZDARsLFfY002hbOmUGac=RACxqpnPRg@mail.gmail.com>
 <CAOx_OQ8t6rfdfX0ng_6OSuGhnQEvPnJVrmkW-whLh-X2d-PLJA@mail.gmail.com>
Message-ID: <006b01d5ef5c$bdb7d9b0$39278d10$@com>

The Icecast KH branch has supported it for years and works well.

https://karlheyes.github.io/

 

From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Mikel Sanz | 20 Comunicaci?n
Sent: Sunday, 1 March 2020 2:57 a.m.
To: Icecast streaming server user discussions
Subject: Re: [Icecast] Chrome not allowing mixed content anymore

 

Yes, I also think that 6 years of Beta is too much and now it's too late...

 

El s?b., 29 feb. 2020 14:25, Alexandru Matei <alexandru.ort at gmail.com> escribi?:

Hi.

 

With its 80th version, Chrome stopped serving non-secure resources on https pages. This affected the icecast server I run also. I enabled SSL, the issue with Chrome not playing audio got fixed, but I noticed a major drop in the number of listeners. As far as I figured out, the listeners that have the http url in a playlist - listening in winamp, vlc etc. - could listen no more. Those using internet radio devices were affected also.

 

Does icecast support streaming both http and https on the same port?

Is there such a feature in the version 4.5beta2?

Is there a release date planned for the new version of icecast?

 

This will affect many listeners and the administrators of those radios servers. What would you do?

 

Thank you.

 

Alex G.

_______________________________________________
Icecast mailing list
Icecast at xiph.org
http://lists.xiph.org/mailman/listinfo/icecast

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200301/47eb1372/attachment.htm>

From gavin at stephens.net.nz  Fri Mar  6 18:08:08 2020
From: gavin at stephens.net.nz (Gavin Stephens)
Date: Sat, 7 Mar 2020 07:08:08 +1300
Subject: [Icecast] SSL Question
Message-ID: <c5504692-aef8-7cae-741b-469e1b067133@stephens.net.nz>

So as I've just found out last week, Chrome no longer will open an http 
audio stream from an https website.

I've un-remarked and enabled ssl on port 443. I've configured the path 
and I've used OpenSSL to generate a cert and key. I've then combined the 
private key in to the cert and called it icecast.pem and un-remarked the 
path to get it to read the file in the Icecast directory. I've made sure 
Icecast is running as Administrator (previously wasn't, so did this for 
further testing and privileges) and file permissions on the icecast.pem 
file are all set correctly for anyone to read and write.

However, when when I view Icecast on port 80 all is fine, when I switch 
to https no go. It is definitely alive on port 443 as I can connect to 
port 443 just using http. Triple checked the config file, the listen 
socket, port and <SSL>1</SSL> is definitely not rem'd out.

Am I missing something or is it not compiled for SSL for Win32?

Cheers,

Gavin.




From gavin at stephens.net.nz  Fri Mar  6 18:16:51 2020
From: gavin at stephens.net.nz (Gavin Stephens)
Date: Sat, 7 Mar 2020 07:16:51 +1300
Subject: [Icecast] SSL Question
In-Reply-To: <c5504692-aef8-7cae-741b-469e1b067133@stephens.net.nz>
References: <c5504692-aef8-7cae-741b-469e1b067133@stephens.net.nz>
Message-ID: <621064da-5469-178d-b2e8-e9fcc45424d2@stephens.net.nz>


On 7/03/2020 7:08 am, Gavin Stephens wrote:
> So as I've just found out last week, Chrome no longer will open an 
> http audio stream from an https website.
>
> I've un-remarked and enabled ssl on port 443. I've configured the path 
> and I've used OpenSSL to generate a cert and key. I've then combined 
> the private key in to the cert and called it icecast.pem and 
> un-remarked the path to get it to read the file in the Icecast 
> directory. I've made sure Icecast is running as Administrator 
> (previously wasn't, so did this for further testing and privileges) 
> and file permissions on the icecast.pem file are all set correctly for 
> anyone to read and write.
>
> However, when when I view Icecast on port 80 all is fine, when I 
> switch to https no go. It is definitely alive on port 443 as I can 
> connect to port 443 just using http. Triple checked the config file, 
> the listen socket, port and <SSL>1</SSL> is definitely not rem'd out.
>
> Am I missing something or is it not compiled for SSL for Win32?
>
> Cheers,
>
> Gavin.
>
>

FYI Chrome just sits there saying establishing secure connection. I've 
just installed Ice on another machine and copied over the icecast.pem 
file and un-remarked the port and path areas for SSL on port 443 (not 
8443).? Same result.

Gavin.




From railgun.michael at gmail.com  Fri Mar  6 23:09:23 2020
From: railgun.michael at gmail.com (Railgun)
Date: Sat, 7 Mar 2020 00:09:23 +0100
Subject: [Icecast] need a config help
Message-ID: <73a105a8-9997-29a9-ca7e-3f1786440b46@gmail.com>

hello my name ist michael,

because the administrator we had cant do the work anymore (bus factor=0)
and we need to setup and reconfigurate all things around the stream
settings, it would be glad if you can help me with the settings.

what works:

mount point for auto dj

mount point for moderators to overide the dj.

ssl conection (todo crome not suport it without anymore)


what does not work?:

at the old settings we could send "aim", "icq" and "irc" settings to the
stream, and could catch them at the status-json.xsl.

to announce the name of the broadcaster, the e-mail adress of the
moderator for music wishes and other things, and the name of the curent
show programm, to put them on twitter, and on the website.


if somone have a documentation how this works, it would be realy glad, i
have search all the web and only found things for darkice but not how to
catch those information.


best regards




From pm at nowster.me.uk  Sun Mar  8 15:03:00 2020
From: pm at nowster.me.uk (Paul Martin)
Date: Sun, 8 Mar 2020 15:03:00 +0000
Subject: [Icecast] SSL Question
In-Reply-To: <621064da-5469-178d-b2e8-e9fcc45424d2@stephens.net.nz>
References: <c5504692-aef8-7cae-741b-469e1b067133@stephens.net.nz>
 <621064da-5469-178d-b2e8-e9fcc45424d2@stephens.net.nz>
Message-ID: <20200308150300.GC450684@thinkpad.nowster.org.uk>

On Sat, Mar 07, 2020 at 07:16:51AM +1300, Gavin Stephens wrote:
> FYI Chrome just sits there saying establishing secure connection. I've just
> installed Ice on another machine and copied over the icecast.pem file and
> un-remarked the port and path areas for SSL on port 443 (not 8443).? Same
> result.

I have:

    <listen-socket>
        <port>8443</port>
        <bind-address>::</bind-address>
        <ssl>1</ssl>
    </listen-socket>

    <paths>
        <ssl-certificate>/etc/icecast2/icecast.pem</ssl-certificate>
    </paths>

And it's definitely working with Chromium 80.0.3987.132.

Is there anything else listening on port 443/tcp on that server?

-- 
Paul Martin <pm at nowster.me.uk>


From gavin at stephens.net.nz  Sun Mar  8 15:24:35 2020
From: gavin at stephens.net.nz (Gavin Stephens)
Date: Mon, 09 Mar 2020 04:24:35 +1300
Subject: [Icecast] SSL Question
In-Reply-To: <20200308150300.GC450684@thinkpad.nowster.org.uk>
References: <c5504692-aef8-7cae-741b-469e1b067133@stephens.net.nz>
 <621064da-5469-178d-b2e8-e9fcc45424d2@stephens.net.nz>
 <20200308150300.GC450684@thinkpad.nowster.org.uk>
Message-ID: <CA5BDF2B-B687-4DD0-BB39-EA932EC20F38@stephens.net.nz>

 Sorry for the late update. I didn't realise the replies came and went off list regarding this.

 I had another suggestion made to me it could still be bad pem files and to try converting them to pfx then back to pem files, which I did, and fortunately this fixed it.

 The error message I was getting in the Icecast log was about no compatible ssl port.  I assumed this was something more complex than a bad certificate since an error message to that effect would have been easier to figure out.

 I took the certificate and private key .pem files, added them together but it didn't work until the conversion to pfx and back.

 Thanks for the reply though.

Cheers,
Gavin.









On 9 March 2020 4:03:00 AM NZDT, Paul Martin <pm at nowster.me.uk> wrote:
>On Sat, Mar 07, 2020 at 07:16:51AM +1300, Gavin Stephens wrote:
>> FYI Chrome just sits there saying establishing secure connection.
>I've just
>> installed Ice on another machine and copied over the icecast.pem file
>and
>> un-remarked the port and path areas for SSL on port 443 (not 8443).?
>Same
>> result.
>
>I have:
>
>    <listen-socket>
>        <port>8443</port>
>        <bind-address>::</bind-address>
>        <ssl>1</ssl>
>    </listen-socket>
>
>    <paths>
>        <ssl-certificate>/etc/icecast2/icecast.pem</ssl-certificate>
>    </paths>
>
>And it's definitely working with Chromium 80.0.3987.132.
>
>Is there anything else listening on port 443/tcp on that server?
>
>-- 
>Paul Martin <pm at nowster.me.uk>
>_______________________________________________
>Icecast mailing list
>Icecast at xiph.org
>http://lists.xiph.org/mailman/listinfo/icecast

-- 
Sent from Open Mail on Android.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200309/bd76ed07/attachment.htm>

From madsend at morningside.edu  Sun Mar  8 15:27:10 2020
From: madsend at morningside.edu (Dave Madsen)
Date: Sun, 8 Mar 2020 10:27:10 -0500
Subject: [Icecast] unsubscribe
Message-ID: <b63b3e6b03ecaf143a8a1d65dd7f2afb@mail.gmail.com>

Dave Madsen

Assistant Professor and Dept. Head, Mass Communication

Morningside College

1501 Morningside Ave.

Sioux City, IA 51106

Office: 712-274-5480

Cell: 712-490-3327

madsend at morningside.edu



*From:* Icecast <icecast-bounces at xiph.org> *On Behalf Of *Gavin Stephens
*Sent:* Sunday, March 8, 2020 10:25 AM
*To:* Icecast streaming server user discussions <icecast at xiph.org>
*Subject:* Re: [Icecast] SSL Question



Sorry for the late update. I didn't realise the replies came and went off
list regarding this.

I had another suggestion made to me it could still be bad pem files and to
try converting them to pfx then back to pem files, which I did, and
fortunately this fixed it.

The error message I was getting in the Icecast log was about no compatible
ssl port. I assumed this was something more complex than a bad certificate
since an error message to that effect would have been easier to figure out.

I took the certificate and private key .pem files, added them together but
it didn't work until the conversion to pfx and back.

Thanks for the reply though.

Cheers,
Gavin.








On 9 March 2020 4:03:00 AM NZDT, Paul Martin <pm at nowster.me.uk> wrote:

On Sat, Mar 07, 2020 at 07:16:51AM +1300, Gavin Stephens wrote:

FYI Chrome just sits there saying establishing secure connection. I've just
installed Ice on another machine and copied over the icecast.pem file and
un-remarked the port and path areas for SSL on port 443 (not 8443).  Same
result.


I have:

    <listen-socket>
        <port>8443</port>
        <bind-address>::</bind-address>
        <ssl>1</ssl>
    </listen-socket>

    <paths>
        <ssl-certificate>/etc/icecast2/icecast.pem</ssl-certificate>
    </paths>

And it's definitely working with Chromium 80.0.3987.132.

Is there anything else listening on port 443/tcp on that server?


-- 
Sent from Open Mail on Android.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200308/ca69d693/attachment.htm>

From jvoosten at bankai.nl  Mon Mar  9 15:43:03 2020
From: jvoosten at bankai.nl (Jeroen van Oosten)
Date: Mon, 9 Mar 2020 16:43:03 +0100
Subject: [Icecast] SSL Question
In-Reply-To: <CA5BDF2B-B687-4DD0-BB39-EA932EC20F38@stephens.net.nz>
References: <c5504692-aef8-7cae-741b-469e1b067133@stephens.net.nz>
 <621064da-5469-178d-b2e8-e9fcc45424d2@stephens.net.nz>
 <20200308150300.GC450684@thinkpad.nowster.org.uk>
 <CA5BDF2B-B687-4DD0-BB39-EA932EC20F38@stephens.net.nz>
Message-ID: <7c319c5f-4314-2450-258b-e7584e884aad@bankai.nl>

On 08/03/2020 16:24, Gavin Stephens wrote:
> Sorry for the late update. I didn't realise the replies came and went
> off list regarding this.
>
> I had another suggestion made to me it could still be bad pem files
> and to try converting them to pfx then back to pem files, which I did,
> and fortunately this fixed it.
>
> The error message I was getting in the Icecast log was about no
> compatible ssl port. I assumed this was something more complex than a
> bad certificate since an error message to that effect would have been
> easier to figure out.
>
> I took the certificate and private key .pem files, added them together
> but it didn't work until the conversion to pfx and back.

Interesting. Can you show us the difference in .pem files before and
after conversion (without revealing your private key, of course)?

Regards,

?- Jeroen


-- 
Bankai Software bv
Jeroen van Oosten
Telefoon: 088-2344999
E-mail: jvoosten at bankai.nl
KvK inschrijving: 67066267
PGP key: B2308F8E

"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." --Red Adair



From gavin at stephens.net.nz  Wed Mar 11 06:15:12 2020
From: gavin at stephens.net.nz (Gavin Stephens)
Date: Wed, 11 Mar 2020 19:15:12 +1300
Subject: [Icecast] SSL Question
In-Reply-To: <7c319c5f-4314-2450-258b-e7584e884aad@bankai.nl>
References: <c5504692-aef8-7cae-741b-469e1b067133@stephens.net.nz>
 <621064da-5469-178d-b2e8-e9fcc45424d2@stephens.net.nz>
 <20200308150300.GC450684@thinkpad.nowster.org.uk>
 <CA5BDF2B-B687-4DD0-BB39-EA932EC20F38@stephens.net.nz>
 <7c319c5f-4314-2450-258b-e7584e884aad@bankai.nl>
Message-ID: <a075aa0b-3065-c8f8-2409-0cc3984e1c0e@stephens.net.nz>


>> The error message I was getting in the Icecast log was about no
>> compatible ssl port. I assumed this was something more complex than a
>> bad certificate since an error message to that effect would have been
>> easier to figure out.
>>
>> I took the certificate and private key .pem files, added them together
>> but it didn't work until the conversion to pfx and back.
> Interesting. Can you show us the difference in .pem files before and
> after conversion (without revealing your private key, of course)?
>
> Regards,
>
>  ?- Jeroen
>
The only difference I can see, is that it has added the bag attributes, 
issuer, country etc... before the base64 begins in plain text. I'm 
wondering if it was in the way the ACME client made the .pem files. I 
used win-acme.

Gavin.



From un at aporee.org  Wed Mar 11 09:39:08 2020
From: un at aporee.org (unosonic)
Date: Wed, 11 Mar 2020 10:39:08 +0100
Subject: [Icecast] SSL Question
In-Reply-To: <a075aa0b-3065-c8f8-2409-0cc3984e1c0e@stephens.net.nz>
References: <c5504692-aef8-7cae-741b-469e1b067133@stephens.net.nz>
 <621064da-5469-178d-b2e8-e9fcc45424d2@stephens.net.nz>
 <20200308150300.GC450684@thinkpad.nowster.org.uk>
 <CA5BDF2B-B687-4DD0-BB39-EA932EC20F38@stephens.net.nz>
 <7c319c5f-4314-2450-258b-e7584e884aad@bankai.nl>
 <a075aa0b-3065-c8f8-2409-0cc3984e1c0e@stephens.net.nz>
Message-ID: <20200311093908.GA65418@aporee.net>


AFIK, pem is simply

1. private key
2. (most specific) certificate
3. intermediate certificates, if any

in this order. 
at least such a pem work for my icecast 2.4 w/o problems

--u





Gavin Stephens:
> 
> > > The error message I was getting in the Icecast log was about no
> > > compatible ssl port. I assumed this was something more complex than a
> > > bad certificate since an error message to that effect would have been
> > > easier to figure out.
> > > 
> > > I took the certificate and private key .pem files, added them together
> > > but it didn't work until the conversion to pfx and back.
> > Interesting. Can you show us the difference in .pem files before and
> > after conversion (without revealing your private key, of course)?
> > 
> > Regards,
> > 
> >  ?- Jeroen
> > 
> The only difference I can see, is that it has added the bag attributes,
> issuer, country etc... before the base64 begins in plain text. I'm wondering
> if it was in the way the ACME client made the .pem files. I used win-acme.
> 
> Gavin.
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From chiapas at aktivix.org  Wed Mar 11 10:47:16 2020
From: chiapas at aktivix.org (Chip)
Date: Wed, 11 Mar 2020 10:47:16 +0000
Subject: [Icecast] SSL Question
In-Reply-To: <20200311093908.GA65418@aporee.net>
References: <c5504692-aef8-7cae-741b-469e1b067133@stephens.net.nz>
 <621064da-5469-178d-b2e8-e9fcc45424d2@stephens.net.nz>
 <20200308150300.GC450684@thinkpad.nowster.org.uk>
 <CA5BDF2B-B687-4DD0-BB39-EA932EC20F38@stephens.net.nz>
 <7c319c5f-4314-2450-258b-e7584e884aad@bankai.nl>
 <a075aa0b-3065-c8f8-2409-0cc3984e1c0e@stephens.net.nz>
 <20200311093908.GA65418@aporee.net>
Message-ID: <CAKCymP0Dq_g-+27w8zgyGu96S0ANeqAbx75RRQJuMHJ8ROmo+Q@mail.gmail.com>

 If you are using LE then this, IMHO, is a good way to make the icecast.pem
file:

cat privkey.pem fullchain.pem > icecast.pem

The above creates a useful SSL cert format which, for example, a range of
devices are able to interpret.

Then you can check your SSL stream here:

   - https://check-your-website.server-daten.de/?q=

Thanks

Chip Scooter

On Wed, 11 Mar 2020 at 09:47, unosonic <un at aporee.org> wrote:

>
> AFIK, pem is simply
>
> 1. private key
> 2. (most specific) certificate
> 3. intermediate certificates, if any
>
> in this order.
> at least such a pem work for my icecast 2.4 w/o problems
>
> --u
>
>
>
>
>
> Gavin Stephens:
> >
> > > > The error message I was getting in the Icecast log was about no
> > > > compatible ssl port. I assumed this was something more complex than a
> > > > bad certificate since an error message to that effect would have been
> > > > easier to figure out.
> > > >
> > > > I took the certificate and private key .pem files, added them
> together
> > > > but it didn't work until the conversion to pfx and back.
> > > Interesting. Can you show us the difference in .pem files before and
> > > after conversion (without revealing your private key, of course)?
> > >
> > > Regards,
> > >
> > >   - Jeroen
> > >
> > The only difference I can see, is that it has added the bag attributes,
> > issuer, country etc... before the base64 begins in plain text. I'm
> wondering
> > if it was in the way the ACME client made the .pem files. I used
> win-acme.
> >
> > Gavin.
> >
> > _______________________________________________
> > Icecast mailing list
> > Icecast at xiph.org
> > http://lists.xiph.org/mailman/listinfo/icecast
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200311/9189f856/attachment.htm>

From brad at audiopump.co  Fri Mar 13 22:46:52 2020
From: brad at audiopump.co (Brad Isbell)
Date: Fri, 13 Mar 2020 17:46:52 -0500
Subject: [Icecast] Empty auth error message,
	URL auth problems on Windows Server
Message-ID: <CAELR-fCAi_QgYY=yj98B=TGwGUaS4bWBdHYZmqQrf5+76u7FAw@mail.gmail.com>

I'm having an issue with URL-based authentication on Windows Server that is
being aggravated by a separate logging issue.  In the server's error log:

[2020-03-13  16:59:46] DBUG connection/connection.c alias has made /player/
> into /player/index.html
> [2020-03-13  16:59:46] INFO auth/auth.c adding client for authentication
> [2020-03-13  16:59:46] DBUG auth/auth.c ...refcount on auth_t (default
> mount) is now 2
> [2020-03-13  16:59:46] INFO auth/auth.c auth on (default mount) has 1
> pending
> [2020-03-13  16:59:46] DBUG auth/auth.c 1 client(s) pending on (default
> mount)
> [2020-03-13  16:59:46] DBUG stats/stats.c update global clients (2)
> [2020-03-13  16:59:46] DBUG stats/stats.c update global connections (7)
> [2020-03-13  16:59:46] DBUG stats/stats.c update global client_connections
> (6)
>
> *[2020-03-13  16:59:46] WARN auth_url/auth_url.c auth to server
> https://auth.example.com/icecast/listenerAdd
> <https://auth.example.com/icecast/listenerAdd> failed with *[2020-03-13
>  16:59:46] DBUG auth/auth.c ...refcount on auth_t (default mount) is now 1
> [2020-03-13  16:59:46] DBUG fserve/fserve.c Adding client to file serving
> engine
> [2020-03-13  16:59:46] DBUG fserve/fserve.c fserve handler waking up
> [2020-03-13  16:59:46] DBUG fserve/fserve.c fserve handler exit
> [2020-03-13  16:59:46] DBUG stats/stats.c update global clients (1)


The key here is: *auth to server ... failed with [missing error message]*

It seems that at least in this particular case, the error message isn't
being logged.  Is this a bug with how Icecast is outputting the error
message, or an issue with libcurl?  I'm hoping if I can see the error
message, I can track down the main problem.

The main problem is that URL authentication with HTTPS doesn't seem to work
on Windows Server.  I can see that a TCP connection is being made to the
auth server, but the auth server says that the Icecast server resets the
connection before making a request.  I have not had this issue with Icecast
builds on Windows 10, nor Ubuntu.  I'm assuming there's some additional
security constraint preventing Icecast from using HTTPS for auth under
Windows Server.  The Windows Event Logs don't contain anything relevant.  I
have tested with proper public certificates from LetsEncrypt and DigiCert,
as well as self-signed certificates.

Any thoughts on either issue would be much appreciated.

Thanks,
*Brad Isbell // AudioPump, Inc.*
brad at audiopump.co
Skype: bradisbell
Phone: +1 312-488-4680
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200313/a3f08e5e/attachment.htm>

From asbesto at gmail.com  Mon Mar 16 10:04:20 2020
From: asbesto at gmail.com (Gabriele Zaverio)
Date: Mon, 16 Mar 2020 11:04:20 +0100
Subject: [Icecast] Zero listeners on icecast stats
Message-ID: <CANe_fbsDXGexz36mhNfKrPbPe7LRzVOcSLEowCrGbEcpdTTqJA@mail.gmail.com>

Hi there,

I just set up a system of fallback streams for our free radio station
here but I have this weird problem: it always show zero listeners.

Our setup is this:

We have a listening mount point for people - that fall back to a live
streaming from a cellular phone - that fall back to a live streaming
from a base station (a pc), that fall back to a 24/7 archive
streaming.

No matter what the sound source is (cellular phone, PC or historical
archive 24/7, our listening mount point always show zero listeners.
But we have listeners there, and they are listening our stream, and
everything works fine.

Any hint about this?

Server is icecast 2. we stream using mixxx from an Imac, darkice from
PC and liquidsoap for our mp3 archive, streaming 24/7.

Our fallback section setup is as follow:

<!-- historical 24/7 mp3 streaming -->
<mount>
        <mount-name>/radiocybernet-archive.mp3</mount-name>
        <hidden>0</hidden>
</mount>

<!-- live mountpoint streaming from a PC base station -->
<mount>
        <mount-name>/rcyblive.mp3</mount-name>
        <intro>./announce-radiocybernet.mp3</intro>
        <fallback-mount>/radiocybernet-archive.mp3</fallback-mount>
        <fallback-override>1</fallback-override>
        <hidden>1</hidden>
</mount>

<!-- Live mountpoint for a cellular phone streaming -->
<mount>
        <mount-name>/rcybcell.mp3</mount-name>
        <intro>./announce-radiocybernet.mp3</intro>
        <fallback-mount>/rcyblive.mp3</fallback-mount>
        <fallback-override>1</fallback-override>
        <hidden>1</hidden>
</mount>

<!-- this is where listeners connect to listen our station -->
<mount>
        <mount-name>/radiocybernet.mp3</mount-name>
        <intro>./announce-radiocybernet.mp3</intro>
        <fallback-mount>/rcybcell.mp3</fallback-mount>
        <fallback-override>1</fallback-override>
        <hidden>0</hidden>
</mount>

<!-- this is an old mountpoint we used for our transmission, for
      historical purpose, many links on internet point here -->
<mount>
        <mount-name>/rcyb.mp3</mount-name>
        <intro>./announce-radiocybernet.mp3</intro>
        <fallback-mount>/radiocybernet.mp3</fallback-mount>
        <fallback-override>1</fallback-override>
        <hidden>1</hidden>
</mount>


Thank you for any help!

-- 
73 de IW9HGS - Gabriele "Asbesto Molesto" Zaverio
Museo dell'Informatica funzionante - Freaknet Computer Museum
http://museum.freaknet.org || http://freaknet.org/asbesto
GPG Fingerprint: 8935 5586 7F2D 9C5E 51B6  BBC5 EA15 9A4E 613D 44D7


From artuch at speedy.com.ar  Mon Mar 16 11:02:00 2020
From: artuch at speedy.com.ar (=?ISO-8859-1?Q?Jos=E9?= Luis Artuch)
Date: Mon, 16 Mar 2020 08:02:00 -0300
Subject: [Icecast] Zero listeners on icecast stats
In-Reply-To: <CANe_fbsDXGexz36mhNfKrPbPe7LRzVOcSLEowCrGbEcpdTTqJA@mail.gmail.com>
References: <CANe_fbsDXGexz36mhNfKrPbPe7LRzVOcSLEowCrGbEcpdTTqJA@mail.gmail.com>
Message-ID: <f9c5f1e983224c1562a469f56cc164cfac8a96b9.camel@speedy.com.ar>

Hi Gabriele,

El lun, 16-03-2020 a las 11:04 +0100, Gabriele Zaverio escribi?:
> Hi there,
> 
> I just set up a system of fallback streams for our free radio station
> here but I have this weird problem: it always show zero listeners.
> 
> Our setup is this:
> 
> We have a listening mount point for people - that fall back to a live
> streaming from a cellular phone - that fall back to a live streaming
> from a base station (a pc), that fall back to a 24/7 archive
> streaming.
> 
> No matter what the sound source is (cellular phone, PC or historical
> archive 24/7, our listening mount point always show zero listeners.
> But we have listeners there, and they are listening our stream, and
> everything works fine.
> 
> Any hint about this?
> 
> Server is icecast 2. we stream using mixxx from an Imac, darkice from
> PC and liquidsoap for our mp3 archive, streaming 24/7.
> 
> Our fallback section setup is as follow:
> 
> <!-- historical 24/7 mp3 streaming -->
> <mount>
>         <mount-name>/radiocybernet-archive.mp3</mount-name>
>         <hidden>0</hidden>
> </mount>
> 
> <!-- live mountpoint streaming from a PC base station -->
> <mount>
>         <mount-name>/rcyblive.mp3</mount-name>
>         <intro>./announce-radiocybernet.mp3</intro>
>         <fallback-mount>/radiocybernet-archive.mp3</fallback-mount>
>         <fallback-override>1</fallback-override>
>         <hidden>1</hidden>
> </mount>
> 
> <!-- Live mountpoint for a cellular phone streaming -->
> <mount>
>         <mount-name>/rcybcell.mp3</mount-name>
>         <intro>./announce-radiocybernet.mp3</intro>
>         <fallback-mount>/rcyblive.mp3</fallback-mount>
>         <fallback-override>1</fallback-override>
>         <hidden>1</hidden>
> </mount>
> 
> <!-- this is where listeners connect to listen our station -->
> <mount>
>         <mount-name>/radiocybernet.mp3</mount-name>
>         <intro>./announce-radiocybernet.mp3</intro>
>         <fallback-mount>/rcybcell.mp3</fallback-mount>
>         <fallback-override>1</fallback-override>
>         <hidden>0</hidden>
> </mount>
> 
> <!-- this is an old mountpoint we used for our transmission, for
>       historical purpose, many links on internet point here -->
> <mount>
>         <mount-name>/rcyb.mp3</mount-name>
>         <intro>./announce-radiocybernet.mp3</intro>
>         <fallback-mount>/radiocybernet.mp3</fallback-mount>
>         <fallback-override>1</fallback-override>
>         <hidden>1</hidden>
> </mount>
> 
> 
> Thank you for any help!
> 
You could experiment with some format supported by Icecast2, for
example *opus*. Maybe you will get a different result ...
Best regards.
Jos? Luis



From epirat07 at gmail.com  Mon Mar 16 11:03:39 2020
From: epirat07 at gmail.com (Marvin Scholz)
Date: Mon, 16 Mar 2020 12:03:39 +0100
Subject: [Icecast] Zero listeners on icecast stats
In-Reply-To: <f9c5f1e983224c1562a469f56cc164cfac8a96b9.camel@speedy.com.ar>
References: <CANe_fbsDXGexz36mhNfKrPbPe7LRzVOcSLEowCrGbEcpdTTqJA@mail.gmail.com>
 <f9c5f1e983224c1562a469f56cc164cfac8a96b9.camel@speedy.com.ar>
Message-ID: <F93650DB-41C3-4B65-8719-A95858CDE02C@gmail.com>



On 16 Mar 2020, at 12:02, Jos? Luis Artuch wrote:

> Hi Gabriele,
>
> El lun, 16-03-2020 a las 11:04 +0100, Gabriele Zaverio escribi?:
>> Hi there,
>>
>> I just set up a system of fallback streams for our free radio station
>> here but I have this weird problem: it always show zero listeners.
>>
>> Our setup is this:
>>
>> We have a listening mount point for people - that fall back to a live
>> streaming from a cellular phone - that fall back to a live streaming
>> from a base station (a pc), that fall back to a 24/7 archive
>> streaming.
>>
>> No matter what the sound source is (cellular phone, PC or historical
>> archive 24/7, our listening mount point always show zero listeners.
>> But we have listeners there, and they are listening our stream, and
>> everything works fine.
>>
>> Any hint about this?
>>
>> Server is icecast 2. we stream using mixxx from an Imac, darkice from
>> PC and liquidsoap for our mp3 archive, streaming 24/7.
>>
>> Our fallback section setup is as follow:
>>
>> <!-- historical 24/7 mp3 streaming -->
>> <mount>
>>         <mount-name>/radiocybernet-archive.mp3</mount-name>
>>         <hidden>0</hidden>
>> </mount>
>>
>> <!-- live mountpoint streaming from a PC base station -->
>> <mount>
>>         <mount-name>/rcyblive.mp3</mount-name>
>>         <intro>./announce-radiocybernet.mp3</intro>
>>         <fallback-mount>/radiocybernet-archive.mp3</fallback-mount>
>>         <fallback-override>1</fallback-override>
>>         <hidden>1</hidden>
>> </mount>
>>
>> <!-- Live mountpoint for a cellular phone streaming -->
>> <mount>
>>         <mount-name>/rcybcell.mp3</mount-name>
>>         <intro>./announce-radiocybernet.mp3</intro>
>>         <fallback-mount>/rcyblive.mp3</fallback-mount>
>>         <fallback-override>1</fallback-override>
>>         <hidden>1</hidden>
>> </mount>
>>
>> <!-- this is where listeners connect to listen our station -->
>> <mount>
>>         <mount-name>/radiocybernet.mp3</mount-name>
>>         <intro>./announce-radiocybernet.mp3</intro>
>>         <fallback-mount>/rcybcell.mp3</fallback-mount>
>>         <fallback-override>1</fallback-override>
>>         <hidden>0</hidden>
>> </mount>
>>
>> <!-- this is an old mountpoint we used for our transmission, for
>>       historical purpose, many links on internet point here -->
>> <mount>
>>         <mount-name>/rcyb.mp3</mount-name>
>>         <intro>./announce-radiocybernet.mp3</intro>
>>         <fallback-mount>/radiocybernet.mp3</fallback-mount>
>>         <fallback-override>1</fallback-override>
>>         <hidden>1</hidden>
>> </mount>
>>
>>
>> Thank you for any help!
>>
> You could experiment with some format supported by Icecast2, for
> example *opus*. Maybe you will get a different result ...
> Best regards.
> Jos? Luis
>

The used format should have no effect whatsover on the mountpoint stats
stuff other than now playing track metadata and such.

> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From artuch at speedy.com.ar  Mon Mar 16 11:06:36 2020
From: artuch at speedy.com.ar (=?ISO-8859-1?Q?Jos=E9?= Luis Artuch)
Date: Mon, 16 Mar 2020 08:06:36 -0300
Subject: [Icecast] Zero listeners on icecast stats
In-Reply-To: <F93650DB-41C3-4B65-8719-A95858CDE02C@gmail.com>
References: <CANe_fbsDXGexz36mhNfKrPbPe7LRzVOcSLEowCrGbEcpdTTqJA@mail.gmail.com>
 <f9c5f1e983224c1562a469f56cc164cfac8a96b9.camel@speedy.com.ar>
 <F93650DB-41C3-4B65-8719-A95858CDE02C@gmail.com>
Message-ID: <1417b8cfe462b5708dfd332bd42272c04ebaaeb1.camel@speedy.com.ar>

Hi Marvin,

El lun, 16-03-2020 a las 12:03 +0100, Marvin Scholz escribi?:
> 
> On 16 Mar 2020, at 12:02, Jos? Luis Artuch wrote:
> 
> > Hi Gabriele,
> > 
> > El lun, 16-03-2020 a las 11:04 +0100, Gabriele Zaverio escribi?:
> > > Hi there,
> > > 
> > > I just set up a system of fallback streams for our free radio
> > > station
> > > here but I have this weird problem: it always show zero
> > > listeners.
> > > 
> > > Our setup is this:
> > > 
> > > We have a listening mount point for people - that fall back to a
> > > live
> > > streaming from a cellular phone - that fall back to a live
> > > streaming
> > > from a base station (a pc), that fall back to a 24/7 archive
> > > streaming.
> > > 
> > > No matter what the sound source is (cellular phone, PC or
> > > historical
> > > archive 24/7, our listening mount point always show zero
> > > listeners.
> > > But we have listeners there, and they are listening our stream,
> > > and
> > > everything works fine.
> > > 
> > > Any hint about this?
> > > 
> > > Server is icecast 2. we stream using mixxx from an Imac, darkice
> > > from
> > > PC and liquidsoap for our mp3 archive, streaming 24/7.
> > > 
> > > Our fallback section setup is as follow:
> > > 
> > > <!-- historical 24/7 mp3 streaming -->
> > > <mount>
> > >         <mount-name>/radiocybernet-archive.mp3</mount-name>
> > >         <hidden>0</hidden>
> > > </mount>
> > > 
> > > <!-- live mountpoint streaming from a PC base station -->
> > > <mount>
> > >         <mount-name>/rcyblive.mp3</mount-name>
> > >         <intro>./announce-radiocybernet.mp3</intro>
> > >         <fallback-mount>/radiocybernet-archive.mp3</fallback-
> > > mount>
> > >         <fallback-override>1</fallback-override>
> > >         <hidden>1</hidden>
> > > </mount>
> > > 
> > > <!-- Live mountpoint for a cellular phone streaming -->
> > > <mount>
> > >         <mount-name>/rcybcell.mp3</mount-name>
> > >         <intro>./announce-radiocybernet.mp3</intro>
> > >         <fallback-mount>/rcyblive.mp3</fallback-mount>
> > >         <fallback-override>1</fallback-override>
> > >         <hidden>1</hidden>
> > > </mount>
> > > 
> > > <!-- this is where listeners connect to listen our station -->
> > > <mount>
> > >         <mount-name>/radiocybernet.mp3</mount-name>
> > >         <intro>./announce-radiocybernet.mp3</intro>
> > >         <fallback-mount>/rcybcell.mp3</fallback-mount>
> > >         <fallback-override>1</fallback-override>
> > >         <hidden>0</hidden>
> > > </mount>
> > > 
> > > <!-- this is an old mountpoint we used for our transmission, for
> > >       historical purpose, many links on internet point here -->
> > > <mount>
> > >         <mount-name>/rcyb.mp3</mount-name>
> > >         <intro>./announce-radiocybernet.mp3</intro>
> > >         <fallback-mount>/radiocybernet.mp3</fallback-mount>
> > >         <fallback-override>1</fallback-override>
> > >         <hidden>1</hidden>
> > > </mount>
> > > 
> > > 
> > > Thank you for any help!
> > > 
> > You could experiment with some format supported by Icecast2, for
> > example *opus*. Maybe you will get a different result ...
> > Best regards.
> > Jos? Luis
> > 
> 
> The used format should have no effect whatsover on the mountpoint
> stats
> stuff other than now playing track metadata and such.
> 
Ah, ok, thanks !
Jos? Luis
> > _______________________________________________
> > Icecast mailing list
> > Icecast at xiph.org
> > http://lists.xiph.org/mailman/listinfo/icecast
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast



From asbesto at gmail.com  Mon Mar 16 12:03:07 2020
From: asbesto at gmail.com (Gabriele Zaverio)
Date: Mon, 16 Mar 2020 13:03:07 +0100
Subject: [Icecast] Zero listeners on icecast stats
In-Reply-To: <1417b8cfe462b5708dfd332bd42272c04ebaaeb1.camel@speedy.com.ar>
References: <CANe_fbsDXGexz36mhNfKrPbPe7LRzVOcSLEowCrGbEcpdTTqJA@mail.gmail.com>
 <f9c5f1e983224c1562a469f56cc164cfac8a96b9.camel@speedy.com.ar>
 <F93650DB-41C3-4B65-8719-A95858CDE02C@gmail.com>
 <1417b8cfe462b5708dfd332bd42272c04ebaaeb1.camel@speedy.com.ar>
Message-ID: <CANe_fbuARXUZx592QQ_qQekuZGBM3oQSYExkgeqyQQXSMvHwoQ@mail.gmail.com>

What I see are listeners shows in the "fallback stream" and not on
their connection mountpoint.

So, in the case of my config above, I have 0 listeners on
"radiocybernet.mp3" and my listeners are shown in "rcyblive.mp3", my
streaming source, that's hidden in our server list (radio.dyne.org if
someone want to see or listen a very weird radio ;) )


On 3/16/20, Jos? Luis Artuch <artuch at speedy.com.ar> wrote:
> Hi Marvin,
>
> El lun, 16-03-2020 a las 12:03 +0100, Marvin Scholz escribi?:
>>
>> On 16 Mar 2020, at 12:02, Jos? Luis Artuch wrote:
>>
>> > Hi Gabriele,
>> >
>> > El lun, 16-03-2020 a las 11:04 +0100, Gabriele Zaverio escribi?:
>> > > Hi there,
>> > >
>> > > I just set up a system of fallback streams for our free radio
>> > > station
>> > > here but I have this weird problem: it always show zero
>> > > listeners.
>> > >
>> > > Our setup is this:
>> > >
>> > > We have a listening mount point for people - that fall back to a
>> > > live
>> > > streaming from a cellular phone - that fall back to a live
>> > > streaming
>> > > from a base station (a pc), that fall back to a 24/7 archive
>> > > streaming.
>> > >
>> > > No matter what the sound source is (cellular phone, PC or
>> > > historical
>> > > archive 24/7, our listening mount point always show zero
>> > > listeners.
>> > > But we have listeners there, and they are listening our stream,
>> > > and
>> > > everything works fine.
>> > >
>> > > Any hint about this?
>> > >
>> > > Server is icecast 2. we stream using mixxx from an Imac, darkice
>> > > from
>> > > PC and liquidsoap for our mp3 archive, streaming 24/7.
>> > >
>> > > Our fallback section setup is as follow:
>> > >
>> > > <!-- historical 24/7 mp3 streaming -->
>> > > <mount>
>> > >         <mount-name>/radiocybernet-archive.mp3</mount-name>
>> > >         <hidden>0</hidden>
>> > > </mount>
>> > >
>> > > <!-- live mountpoint streaming from a PC base station -->
>> > > <mount>
>> > >         <mount-name>/rcyblive.mp3</mount-name>
>> > >         <intro>./announce-radiocybernet.mp3</intro>
>> > >         <fallback-mount>/radiocybernet-archive.mp3</fallback-
>> > > mount>
>> > >         <fallback-override>1</fallback-override>
>> > >         <hidden>1</hidden>
>> > > </mount>
>> > >
>> > > <!-- Live mountpoint for a cellular phone streaming -->
>> > > <mount>
>> > >         <mount-name>/rcybcell.mp3</mount-name>
>> > >         <intro>./announce-radiocybernet.mp3</intro>
>> > >         <fallback-mount>/rcyblive.mp3</fallback-mount>
>> > >         <fallback-override>1</fallback-override>
>> > >         <hidden>1</hidden>
>> > > </mount>
>> > >
>> > > <!-- this is where listeners connect to listen our station -->
>> > > <mount>
>> > >         <mount-name>/radiocybernet.mp3</mount-name>
>> > >         <intro>./announce-radiocybernet.mp3</intro>
>> > >         <fallback-mount>/rcybcell.mp3</fallback-mount>
>> > >         <fallback-override>1</fallback-override>
>> > >         <hidden>0</hidden>
>> > > </mount>
>> > >
>> > > <!-- this is an old mountpoint we used for our transmission, for
>> > >       historical purpose, many links on internet point here -->
>> > > <mount>
>> > >         <mount-name>/rcyb.mp3</mount-name>
>> > >         <intro>./announce-radiocybernet.mp3</intro>
>> > >         <fallback-mount>/radiocybernet.mp3</fallback-mount>
>> > >         <fallback-override>1</fallback-override>
>> > >         <hidden>1</hidden>
>> > > </mount>
>> > >
>> > >
>> > > Thank you for any help!
>> > >
>> > You could experiment with some format supported by Icecast2, for
>> > example *opus*. Maybe you will get a different result ...
>> > Best regards.
>> > Jos? Luis
>> >
>>
>> The used format should have no effect whatsover on the mountpoint
>> stats
>> stuff other than now playing track metadata and such.
>>
> Ah, ok, thanks !
> Jos? Luis
>> > _______________________________________________
>> > Icecast mailing list
>> > Icecast at xiph.org
>> > http://lists.xiph.org/mailman/listinfo/icecast
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org
>> http://lists.xiph.org/mailman/listinfo/icecast
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>


-- 
73 de IW9HGS - Gabriele "Asbesto Molesto" Zaverio
Museo dell'Informatica funzionante - Freaknet Computer Museum
http://museum.freaknet.org || http://freaknet.org/asbesto
GPG Fingerprint: 8935 5586 7F2D 9C5E 51B6  BBC5 EA15 9A4E 613D 44D7


From robert at megarockradio.net  Mon Mar 16 15:50:04 2020
From: robert at megarockradio.net (Robert)
Date: Mon, 16 Mar 2020 10:50:04 -0500
Subject: [Icecast] Zero listeners on icecast stats
In-Reply-To: <f9c5f1e983224c1562a469f56cc164cfac8a96b9.camel@speedy.com.ar>
References: <f9c5f1e983224c1562a469f56cc164cfac8a96b9.camel@speedy.com.ar>
Message-ID: <60C1A205-F46E-4445-AFC6-827E09C122CF@megarockradio.net>

Have you considered round robin DNS.. essentially you assign the same A record to two IPs. I do this and it distributes listeners for me without Icecast.

Sent from my iPhone

> On Mar 16, 2020, at 6:02 AM, Jos? Luis Artuch <artuch at speedy.com.ar> wrote:
> 
> ?Hi Gabriele,
> 
>> El lun, 16-03-2020 a las 11:04 +0100, Gabriele Zaverio escribi?:
>> Hi there,
>> 
>> I just set up a system of fallback streams for our free radio station
>> here but I have this weird problem: it always show zero listeners.
>> 
>> Our setup is this:
>> 
>> We have a listening mount point for people - that fall back to a live
>> streaming from a cellular phone - that fall back to a live streaming
>> from a base station (a pc), that fall back to a 24/7 archive
>> streaming.
>> 
>> No matter what the sound source is (cellular phone, PC or historical
>> archive 24/7, our listening mount point always show zero listeners.
>> But we have listeners there, and they are listening our stream, and
>> everything works fine.
>> 
>> Any hint about this?
>> 
>> Server is icecast 2. we stream using mixxx from an Imac, darkice from
>> PC and liquidsoap for our mp3 archive, streaming 24/7.
>> 
>> Our fallback section setup is as follow:
>> 
>> <!-- historical 24/7 mp3 streaming -->
>> <mount>
>>        <mount-name>/radiocybernet-archive.mp3</mount-name>
>>        <hidden>0</hidden>
>> </mount>
>> 
>> <!-- live mountpoint streaming from a PC base station -->
>> <mount>
>>        <mount-name>/rcyblive.mp3</mount-name>
>>        <intro>./announce-radiocybernet.mp3</intro>
>>        <fallback-mount>/radiocybernet-archive.mp3</fallback-mount>
>>        <fallback-override>1</fallback-override>
>>        <hidden>1</hidden>
>> </mount>
>> 
>> <!-- Live mountpoint for a cellular phone streaming -->
>> <mount>
>>        <mount-name>/rcybcell.mp3</mount-name>
>>        <intro>./announce-radiocybernet.mp3</intro>
>>        <fallback-mount>/rcyblive.mp3</fallback-mount>
>>        <fallback-override>1</fallback-override>
>>        <hidden>1</hidden>
>> </mount>
>> 
>> <!-- this is where listeners connect to listen our station -->
>> <mount>
>>        <mount-name>/radiocybernet.mp3</mount-name>
>>        <intro>./announce-radiocybernet.mp3</intro>
>>        <fallback-mount>/rcybcell.mp3</fallback-mount>
>>        <fallback-override>1</fallback-override>
>>        <hidden>0</hidden>
>> </mount>
>> 
>> <!-- this is an old mountpoint we used for our transmission, for
>>      historical purpose, many links on internet point here -->
>> <mount>
>>        <mount-name>/rcyb.mp3</mount-name>
>>        <intro>./announce-radiocybernet.mp3</intro>
>>        <fallback-mount>/radiocybernet.mp3</fallback-mount>
>>        <fallback-override>1</fallback-override>
>>        <hidden>1</hidden>
>> </mount>
>> 
>> 
>> Thank you for any help!
>> 
> You could experiment with some format supported by Icecast2, for
> example *opus*. Maybe you will get a different result ...
> Best regards.
> Jos? Luis
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast



From asbesto at gmail.com  Mon Mar 16 18:57:32 2020
From: asbesto at gmail.com (Gabriele Zaverio)
Date: Mon, 16 Mar 2020 19:57:32 +0100
Subject: [Icecast] Zero listeners on icecast stats
In-Reply-To: <60C1A205-F46E-4445-AFC6-827E09C122CF@megarockradio.net>
References: <f9c5f1e983224c1562a469f56cc164cfac8a96b9.camel@speedy.com.ar>
 <60C1A205-F46E-4445-AFC6-827E09C122CF@megarockradio.net>
Message-ID: <CANe_fbt4ZnT1201isBosm7HFhCdrUcW5MHFSqUmeZF4R845xbQ@mail.gmail.com>

I don't get it. I'm asking why listeners does not show in the
mountpoint they're listening. What's the matter with DNS?


On 3/16/20, Robert <robert at megarockradio.net> wrote:
> Have you considered round robin DNS.. essentially you assign the same A
> record to two IPs. I do this and it distributes listeners for me without
> Icecast.
>
> Sent from my iPhone
>
>> On Mar 16, 2020, at 6:02 AM, Jos? Luis Artuch <artuch at speedy.com.ar>
>> wrote:
>>
>> ?Hi Gabriele,
>>
>>> El lun, 16-03-2020 a las 11:04 +0100, Gabriele Zaverio escribi?:
>>> Hi there,
>>>
>>> I just set up a system of fallback streams for our free radio station
>>> here but I have this weird problem: it always show zero listeners.
>>>
>>> Our setup is this:
>>>
>>> We have a listening mount point for people - that fall back to a live
>>> streaming from a cellular phone - that fall back to a live streaming
>>> from a base station (a pc), that fall back to a 24/7 archive
>>> streaming.
>>>
>>> No matter what the sound source is (cellular phone, PC or historical
>>> archive 24/7, our listening mount point always show zero listeners.
>>> But we have listeners there, and they are listening our stream, and
>>> everything works fine.
>>>
>>> Any hint about this?
>>>
>>> Server is icecast 2. we stream using mixxx from an Imac, darkice from
>>> PC and liquidsoap for our mp3 archive, streaming 24/7.
>>>
>>> Our fallback section setup is as follow:
>>>
>>> <!-- historical 24/7 mp3 streaming -->
>>> <mount>
>>>        <mount-name>/radiocybernet-archive.mp3</mount-name>
>>>        <hidden>0</hidden>
>>> </mount>
>>>
>>> <!-- live mountpoint streaming from a PC base station -->
>>> <mount>
>>>        <mount-name>/rcyblive.mp3</mount-name>
>>>        <intro>./announce-radiocybernet.mp3</intro>
>>>        <fallback-mount>/radiocybernet-archive.mp3</fallback-mount>
>>>        <fallback-override>1</fallback-override>
>>>        <hidden>1</hidden>
>>> </mount>
>>>
>>> <!-- Live mountpoint for a cellular phone streaming -->
>>> <mount>
>>>        <mount-name>/rcybcell.mp3</mount-name>
>>>        <intro>./announce-radiocybernet.mp3</intro>
>>>        <fallback-mount>/rcyblive.mp3</fallback-mount>
>>>        <fallback-override>1</fallback-override>
>>>        <hidden>1</hidden>
>>> </mount>
>>>
>>> <!-- this is where listeners connect to listen our station -->
>>> <mount>
>>>        <mount-name>/radiocybernet.mp3</mount-name>
>>>        <intro>./announce-radiocybernet.mp3</intro>
>>>        <fallback-mount>/rcybcell.mp3</fallback-mount>
>>>        <fallback-override>1</fallback-override>
>>>        <hidden>0</hidden>
>>> </mount>
>>>
>>> <!-- this is an old mountpoint we used for our transmission, for
>>>      historical purpose, many links on internet point here -->
>>> <mount>
>>>        <mount-name>/rcyb.mp3</mount-name>
>>>        <intro>./announce-radiocybernet.mp3</intro>
>>>        <fallback-mount>/radiocybernet.mp3</fallback-mount>
>>>        <fallback-override>1</fallback-override>
>>>        <hidden>1</hidden>
>>> </mount>
>>>
>>>
>>> Thank you for any help!
>>>
>> You could experiment with some format supported by Icecast2, for
>> example *opus*. Maybe you will get a different result ...
>> Best regards.
>> Jos? Luis
>>
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org
>> http://lists.xiph.org/mailman/listinfo/icecast
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>


-- 
73 de IW9HGS - Gabriele "Asbesto Molesto" Zaverio
Museo dell'Informatica funzionante - Freaknet Computer Museum
http://museum.freaknet.org || http://freaknet.org/asbesto
GPG Fingerprint: 8935 5586 7F2D 9C5E 51B6  BBC5 EA15 9A4E 613D 44D7


From pm at nowster.me.uk  Mon Mar 16 23:05:00 2020
From: pm at nowster.me.uk (Paul Martin)
Date: Mon, 16 Mar 2020 23:05:00 +0000
Subject: [Icecast] Zero listeners on icecast stats
In-Reply-To: <f9c5f1e983224c1562a469f56cc164cfac8a96b9.camel@speedy.com.ar>
References: <CANe_fbsDXGexz36mhNfKrPbPe7LRzVOcSLEowCrGbEcpdTTqJA@mail.gmail.com>
 <f9c5f1e983224c1562a469f56cc164cfac8a96b9.camel@speedy.com.ar>
Message-ID: <20200316230500.GA1168440@thinkpad.nowster.org.uk>

On Mon, Mar 16, 2020 at 08:02:00AM -0300, Jos? Luis Artuch wrote:

> You could experiment with some format supported by Icecast2, for
> example *opus*. Maybe you will get a different result ...

The best of luck in getting current clients working properly with
Ogg/Opus.  Many clients are buggy in that regard, including such
things as closing the stream on metadata change.

Many clients even now can't cope with metadata in Ogg/Vorbis streams!

-- 
Paul Martin <pm at nowster.me.uk>


From asbesto at gmail.com  Wed Mar 18 14:56:45 2020
From: asbesto at gmail.com (Gabriele Zaverio)
Date: Wed, 18 Mar 2020 15:56:45 +0100
Subject: [Icecast] Zero listeners on icecast stats
In-Reply-To: <20200316230500.GA1168440@thinkpad.nowster.org.uk>
References: <CANe_fbsDXGexz36mhNfKrPbPe7LRzVOcSLEowCrGbEcpdTTqJA@mail.gmail.com>
 <f9c5f1e983224c1562a469f56cc164cfac8a96b9.camel@speedy.com.ar>
 <20200316230500.GA1168440@thinkpad.nowster.org.uk>
Message-ID: <CANe_fbspQytZpp+SmnmQ93fqsRkr0Hj-BhZvzpNJVSDV-aYHPA@mail.gmail.com>

That doesn't solve my issue. I need to keep mp3 because it's the most
used format from listeners. Opus? Who use it? Ogg? No existing
hardware player around can play .ogg.

Mp3 it is. :)

btw it's weird, I'm now fumbling with <fallback-override> setting but
with no success.

No solution at all? This is weird. :(


On 3/17/20, Paul Martin <pm at nowster.me.uk> wrote:
> On Mon, Mar 16, 2020 at 08:02:00AM -0300, Jos? Luis Artuch wrote:
>
>> You could experiment with some format supported by Icecast2, for
>> example *opus*. Maybe you will get a different result ...
>
> The best of luck in getting current clients working properly with
> Ogg/Opus.  Many clients are buggy in that regard, including such
> things as closing the stream on metadata change.
>
> Many clients even now can't cope with metadata in Ogg/Vorbis streams!
>
> --
> Paul Martin <pm at nowster.me.uk>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>


-- 
73 de IW9HGS - Gabriele "Asbesto Molesto" Zaverio
Museo dell'Informatica funzionante - Freaknet Computer Museum
http://museum.freaknet.org || http://freaknet.org/asbesto
GPG Fingerprint: 8935 5586 7F2D 9C5E 51B6  BBC5 EA15 9A4E 613D 44D7


From d.geneste at illud.fr  Wed Mar 18 15:25:18 2020
From: d.geneste at illud.fr (Damien GENESTE)
Date: Wed, 18 Mar 2020 16:25:18 +0100
Subject: [Icecast] Issue with Wordpress in HTTPS and Icecast Stream URL in
	HTTP
Message-ID: <CAG4BS6bXiC=eOEKtpRz8JqNPK1uVr_Z4T2tsPvpLaeWNALqzYQ@mail.gmail.com>

Hello,

Configuration :
- Debian 8
- Wordpress 5.3.2 (Apache)
- Icecast 2
- Radio web player : Streamcast

I just installed my Web radio that was working correctly in full HTTP.

I add a Lets Encrypt certificat on my Wordpress that is now in HTTPS. Since
my Wordpress is in HTTPS, my stream on the website is not working. The
direct Link in HTTP is working correctly.

I checked on the internet and it say "mixed content do not work". I was not
able to find a simple procedure to add HTTPS on my Icecast stream link.

Could you please hell me with this ?

Best regards,

Damien
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200318/70f19bad/attachment.htm>

From chiapas at aktivix.org  Wed Mar 18 18:34:25 2020
From: chiapas at aktivix.org (Chip)
Date: Wed, 18 Mar 2020 18:34:25 +0000
Subject: [Icecast] Issue with Wordpress in HTTPS and Icecast Stream URL
	in HTTP
In-Reply-To: <CAG4BS6bXiC=eOEKtpRz8JqNPK1uVr_Z4T2tsPvpLaeWNALqzYQ@mail.gmail.com>
References: <CAG4BS6bXiC=eOEKtpRz8JqNPK1uVr_Z4T2tsPvpLaeWNALqzYQ@mail.gmail.com>
Message-ID: <CAKCymP2YyzafcpO8_sR37=AZnuKczBfhA4RuCVZq-ooCNdtewg@mail.gmail.com>

 How about this:

   - https://serverok.in/centovacast-enable-ssl-on-icecast

You're welcome. Don't mention it :o)

Chip Scooter

On Wed, 18 Mar 2020 at 15:31, Damien GENESTE <d.geneste at illud.fr> wrote:

> Hello,
>
> Configuration :
> - Debian 8
> - Wordpress 5.3.2 (Apache)
> - Icecast 2
> - Radio web player : Streamcast
>
> I just installed my Web radio that was working correctly in full HTTP.
>
> I add a Lets Encrypt certificat on my Wordpress that is now in HTTPS.
> Since my Wordpress is in HTTPS, my stream on the website is not working.
> The direct Link in HTTP is working correctly.
>
> I checked on the internet and it say "mixed content do not work". I was
> not able to find a simple procedure to add HTTPS on my Icecast stream link.
>
> Could you please hell me with this ?
>
> Best regards,
>
> Damien
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200318/03277732/attachment.htm>

From jvoosten at bankai.nl  Wed Mar 18 21:11:30 2020
From: jvoosten at bankai.nl (Jeroen van Oosten)
Date: Wed, 18 Mar 2020 22:11:30 +0100
Subject: [Icecast] Zero listeners on icecast stats
In-Reply-To: <CANe_fbsDXGexz36mhNfKrPbPe7LRzVOcSLEowCrGbEcpdTTqJA@mail.gmail.com>
References: <CANe_fbsDXGexz36mhNfKrPbPe7LRzVOcSLEowCrGbEcpdTTqJA@mail.gmail.com>
Message-ID: <60b3446b-4238-0957-0804-592e749a4a74@bankai.nl>

Hello,


On 16/03/2020 11:04, Gabriele Zaverio wrote:
> Hi there,
>
> <!-- historical 24/7 mp3 streaming -->
> <mount>
>         <mount-name>/radiocybernet-archive.mp3</mount-name>
>         <hidden>0</hidden>
> </mount>
>
> <!-- live mountpoint streaming from a PC base station -->
> <mount>
>         <mount-name>/rcyblive.mp3</mount-name>
>         <intro>./announce-radiocybernet.mp3</intro>
>         <fallback-mount>/radiocybernet-archive.mp3</fallback-mount>
>         <fallback-override>1</fallback-override>
>         <hidden>1</hidden>
> </mount>
>
> <!-- Live mountpoint for a cellular phone streaming -->
> <mount>
>         <mount-name>/rcybcell.mp3</mount-name>
>         <intro>./announce-radiocybernet.mp3</intro>
>         <fallback-mount>/rcyblive.mp3</fallback-mount>
>         <fallback-override>1</fallback-override>
>         <hidden>1</hidden>
> </mount>
>
> <!-- this is where listeners connect to listen our station -->
> <mount>
>         <mount-name>/radiocybernet.mp3</mount-name>
>         <intro>./announce-radiocybernet.mp3</intro>
>         <fallback-mount>/rcybcell.mp3</fallback-mount>
>         <fallback-override>1</fallback-override>
>         <hidden>0</hidden>
> </mount>
>
> <!-- this is an old mountpoint we used for our transmission, for
>       historical purpose, many links on internet point here -->
> <mount>
>         <mount-name>/rcyb.mp3</mount-name>
>         <intro>./announce-radiocybernet.mp3</intro>
>         <fallback-mount>/radiocybernet.mp3</fallback-mount>
>         <fallback-override>1</fallback-override>
>         <hidden>1</hidden>
> </mount>
>
Just a thought: what happens if you remove the <intro>, and make the
historical mount points not hidden?


?- Jeroen



-- 
Bankai Software bv
Jeroen van Oosten
Telefoon: 088-2344999
E-mail: jvoosten at bankai.nl
KvK inschrijving: 67066267
PGP key: B2308F8E

"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." --Red Adair



From konrad.kostecki at gmail.com  Thu Mar 19 15:39:15 2020
From: konrad.kostecki at gmail.com (Konrad Kostecki)
Date: Thu, 19 Mar 2020 16:39:15 +0100
Subject: [Icecast] Icecast source client with web request/voting for next to
	play function
Message-ID: <CALPXi_Q46s+Gg+Ag5DgH7fu5K1KJJq5SK2cS-chqJsEFXEBwoQ@mail.gmail.com>

Hi all!

Thank you for having me. I'm a person who encourage a small local community
for musical involvement. It already kinda worked, we are doing plenty of
fantastic things together.

What I am now thinking of is 24/7 Internet radio based on Icecast that will
air all of their non-professional music I gathered. Functions I'm looking
for:
- frequent scanning of music directory to update music library for dynamic
playlist building
- to shuffle music on playlist fairly to not have same artist played two or
more times in a row, so all artists could have a chance to be aired equally
- from web perspective to have possibility for end-users to select songs
which will be played next
- replaygain support (radio mode, not album mode)

Don't get me wrong, I'm not looking for any easy/ready solution, maybe I'm
not a coder but I can at least try to script something in bash or Python.
However, I'm confused regarding source clients available - Liquidsoap,
butt, MPD, DarkIce, DeeFuzzer, Ezstream (at least I find these projects as
quite active) - I have no experience with them and I can't really find
useful opinions. Can you tell which of them could be best for described
vision? I'd appreciate if you could recommend me any way I could follow,
which specific software components I would possibly need to integrate. Even
brief information will do!

Thanks! Stay healthy!
Kokos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200319/4bebf807/attachment.htm>

From jordan at coolmic.net  Thu Mar 19 16:02:04 2020
From: jordan at coolmic.net (Jordan Erickson)
Date: Thu, 19 Mar 2020 09:02:04 -0700
Subject: [Icecast] Icecast source client with web request/voting for
 next to play function
In-Reply-To: <CALPXi_Q46s+Gg+Ag5DgH7fu5K1KJJq5SK2cS-chqJsEFXEBwoQ@mail.gmail.com>
References: <CALPXi_Q46s+Gg+Ag5DgH7fu5K1KJJq5SK2cS-chqJsEFXEBwoQ@mail.gmail.com>
Message-ID: <25896f23-f2e9-f09b-5abc-74943e87781f@coolmic.net>

Hi Konrad,

I really like what your mission for broadcasting music with Icecast.

I use liquidsoap ( https://www.liquidsoap.info/ ) to automate streaming
of past-recorded music content on my webradio. It's worked great, but be
aware that there is a steep learning curve compared to something like Ices2.

I am managing a project with some excellent developers here called Cool
Mic which broadcasts live audio that you could use for live performances
as well, to for example a fallback mountpoint. We are also using this
code for a live music streaming platform called SubJam (
https://subj.am/ ) that also uses Icecast as a backend. We're looking
for additional developers and funding sources with this project.

I know that others have accomplished the 'vote for next track' function,
it is beyond the scope of Icecast however and would interact with the
source client itself.


Cheers,
Jordan


On 3/19/20 8:39 AM, Konrad Kostecki wrote:
> Hi all!
> 
> Thank you for having me. I'm a person who encourage a small local
> community for musical involvement. It already kinda worked, we are doing
> plenty of fantastic things together.
> 
> What I am now thinking of is 24/7 Internet radio based on Icecast that
> will air all of their non-professional music I gathered. Functions I'm
> looking for:
> - frequent scanning of music directory to update music library for
> dynamic playlist building
> - to shuffle music on playlist fairly to not have same artist played two
> or more times in a row, so all artists could have a chance to be aired
> equally
> - from web perspective to have possibility for end-users to select songs
> which will be played next
> - replaygain support (radio mode, not album mode)
> 
> Don't get me wrong, I'm not looking for any easy/ready solution, maybe
> I'm not a coder but I can at least try to script something in bash or
> Python. However, I'm confused regarding source clients available -
> Liquidsoap, butt, MPD, DarkIce, DeeFuzzer, Ezstream (at least I find
> these projects as quite active) - I have no experience with them and I
> can't really find useful opinions. Can you tell which of them could be
> best for described vision? I'd appreciate if you could recommend me any
> way I could follow, which specific software components I would possibly
> need to integrate. Even brief information will do!
> 
> Thanks! Stay healthy!
> Kokos
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
> 


From asbesto at gmail.com  Thu Mar 19 17:45:55 2020
From: asbesto at gmail.com (Gabriele Zaverio)
Date: Thu, 19 Mar 2020 18:45:55 +0100
Subject: [Icecast] Zero listeners on icecast stats
In-Reply-To: <60b3446b-4238-0957-0804-592e749a4a74@bankai.nl>
References: <CANe_fbsDXGexz36mhNfKrPbPe7LRzVOcSLEowCrGbEcpdTTqJA@mail.gmail.com>
 <60b3446b-4238-0957-0804-592e749a4a74@bankai.nl>
Message-ID: <CANe_fbuP8hX=KJoeVURjfzdL0vvKWZec1ObhOKsqEfhsTmLxTA@mail.gmail.com>

I must try that. Will let you know asap!

btw I'm not "trying to stick with the one that has the most universal
"default browser support" but instead trying to avoid a LOT of
listeners writing me "my player/browser/whatever doesn't connect, it
doesn't understand ogg / opus / xspf " etc. etc. - so mp3 it is.

It's simple surviving :)

On 3/18/20, Jeroen van Oosten <jvoosten at bankai.nl> wrote:
> Hello,
>
>
> On 16/03/2020 11:04, Gabriele Zaverio wrote:
>> Hi there,
>>
>> <!-- historical 24/7 mp3 streaming -->
>> <mount>
>>         <mount-name>/radiocybernet-archive.mp3</mount-name>
>>         <hidden>0</hidden>
>> </mount>
>>
>> <!-- live mountpoint streaming from a PC base station -->
>> <mount>
>>         <mount-name>/rcyblive.mp3</mount-name>
>>         <intro>./announce-radiocybernet.mp3</intro>
>>         <fallback-mount>/radiocybernet-archive.mp3</fallback-mount>
>>         <fallback-override>1</fallback-override>
>>         <hidden>1</hidden>
>> </mount>
>>
>> <!-- Live mountpoint for a cellular phone streaming -->
>> <mount>
>>         <mount-name>/rcybcell.mp3</mount-name>
>>         <intro>./announce-radiocybernet.mp3</intro>
>>         <fallback-mount>/rcyblive.mp3</fallback-mount>
>>         <fallback-override>1</fallback-override>
>>         <hidden>1</hidden>
>> </mount>
>>
>> <!-- this is where listeners connect to listen our station -->
>> <mount>
>>         <mount-name>/radiocybernet.mp3</mount-name>
>>         <intro>./announce-radiocybernet.mp3</intro>
>>         <fallback-mount>/rcybcell.mp3</fallback-mount>
>>         <fallback-override>1</fallback-override>
>>         <hidden>0</hidden>
>> </mount>
>>
>> <!-- this is an old mountpoint we used for our transmission, for
>>       historical purpose, many links on internet point here -->
>> <mount>
>>         <mount-name>/rcyb.mp3</mount-name>
>>         <intro>./announce-radiocybernet.mp3</intro>
>>         <fallback-mount>/radiocybernet.mp3</fallback-mount>
>>         <fallback-override>1</fallback-override>
>>         <hidden>1</hidden>
>> </mount>
>>
> Just a thought: what happens if you remove the <intro>, and make the
> historical mount points not hidden?
>
>
> ?- Jeroen
>
>
>
> --
> Bankai Software bv
> Jeroen van Oosten
> Telefoon: 088-2344999
> E-mail: jvoosten at bankai.nl
> KvK inschrijving: 67066267
> PGP key: B2308F8E
>
> "If you think it's expensive to hire a professional to do the job, wait
> until you hire an amateur." --Red Adair
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>


-- 
73 de IW9HGS - Gabriele "Asbesto Molesto" Zaverio
Museo dell'Informatica funzionante - Freaknet Computer Museum
http://museum.freaknet.org || http://freaknet.org/asbesto
GPG Fingerprint: 8935 5586 7F2D 9C5E 51B6  BBC5 EA15 9A4E 613D 44D7


From mjcolorado89 at aol.com  Thu Mar 19 19:25:06 2020
From: mjcolorado89 at aol.com (Michael Hunt)
Date: Thu, 19 Mar 2020 15:25:06 -0400
Subject: [Icecast] Zero listeners on icecast stats
In-Reply-To: <CANe_fbuP8hX=KJoeVURjfzdL0vvKWZec1ObhOKsqEfhsTmLxTA@mail.gmail.com>
References: <CANe_fbsDXGexz36mhNfKrPbPe7LRzVOcSLEowCrGbEcpdTTqJA@mail.gmail.com>
 <60b3446b-4238-0957-0804-592e749a4a74@bankai.nl>
 <CANe_fbuP8hX=KJoeVURjfzdL0vvKWZec1ObhOKsqEfhsTmLxTA@mail.gmail.com>
Message-ID: <024f01d5fe24$199c5050$4cd4f0f0$@aol.com>

hayden at blindcafe.net


-----Original Message-----
From: Icecast <icecast-bounces at xiph.org> On Behalf Of Gabriele Zaverio
Sent: Thursday, March 19, 2020 1:46 PM
To: Icecast streaming server user discussions <icecast at xiph.org>
Subject: Re: [Icecast] Zero listeners on icecast stats

I must try that. Will let you know asap!

btw I'm not "trying to stick with the one that has the most universal "default browser support" but instead trying to avoid a LOT of listeners writing me "my player/browser/whatever doesn't connect, it doesn't understand ogg / opus / xspf " etc. etc. - so mp3 it is.

It's simple surviving :)

On 3/18/20, Jeroen van Oosten <jvoosten at bankai.nl> wrote:
> Hello,
>
>
> On 16/03/2020 11:04, Gabriele Zaverio wrote:
>> Hi there,
>>
>> <!-- historical 24/7 mp3 streaming --> <mount>
>>         <mount-name>/radiocybernet-archive.mp3</mount-name>
>>         <hidden>0</hidden>
>> </mount>
>>
>> <!-- live mountpoint streaming from a PC base station --> <mount>
>>         <mount-name>/rcyblive.mp3</mount-name>
>>         <intro>./announce-radiocybernet.mp3</intro>
>>         <fallback-mount>/radiocybernet-archive.mp3</fallback-mount>
>>         <fallback-override>1</fallback-override>
>>         <hidden>1</hidden>
>> </mount>
>>
>> <!-- Live mountpoint for a cellular phone streaming --> <mount>
>>         <mount-name>/rcybcell.mp3</mount-name>
>>         <intro>./announce-radiocybernet.mp3</intro>
>>         <fallback-mount>/rcyblive.mp3</fallback-mount>
>>         <fallback-override>1</fallback-override>
>>         <hidden>1</hidden>
>> </mount>
>>
>> <!-- this is where listeners connect to listen our station --> 
>> <mount>
>>         <mount-name>/radiocybernet.mp3</mount-name>
>>         <intro>./announce-radiocybernet.mp3</intro>
>>         <fallback-mount>/rcybcell.mp3</fallback-mount>
>>         <fallback-override>1</fallback-override>
>>         <hidden>0</hidden>
>> </mount>
>>
>> <!-- this is an old mountpoint we used for our transmission, for
>>       historical purpose, many links on internet point here --> 
>> <mount>
>>         <mount-name>/rcyb.mp3</mount-name>
>>         <intro>./announce-radiocybernet.mp3</intro>
>>         <fallback-mount>/radiocybernet.mp3</fallback-mount>
>>         <fallback-override>1</fallback-override>
>>         <hidden>1</hidden>
>> </mount>
>>
> Just a thought: what happens if you remove the <intro>, and make the 
> historical mount points not hidden?
>
>
>  - Jeroen
>
>
>
> --
> Bankai Software bv
> Jeroen van Oosten
> Telefoon: 088-2344999
> E-mail: jvoosten at bankai.nl
> KvK inschrijving: 67066267
> PGP key: B2308F8E
>
> "If you think it's expensive to hire a professional to do the job, 
> wait until you hire an amateur." --Red Adair
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>


--
73 de IW9HGS - Gabriele "Asbesto Molesto" Zaverio Museo dell'Informatica funzionante - Freaknet Computer Museum http://museum.freaknet.org || http://freaknet.org/asbesto GPG Fingerprint: 8935 5586 7F2D 9C5E 51B6  BBC5 EA15 9A4E 613D 44D7 _______________________________________________
Icecast mailing list
Icecast at xiph.org
http://lists.xiph.org/mailman/listinfo/icecast



From jeffares.robert at gmail.com  Thu Mar 19 23:05:29 2020
From: jeffares.robert at gmail.com (Robert Jeffares)
Date: Fri, 20 Mar 2020 12:05:29 +1300
Subject: [Icecast] Icecast source client with web request/voting for
 next to play function
In-Reply-To: <CALPXi_Q46s+Gg+Ag5DgH7fu5K1KJJq5SK2cS-chqJsEFXEBwoQ@mail.gmail.com>
References: <CALPXi_Q46s+Gg+Ag5DgH7fu5K1KJJq5SK2cS-chqJsEFXEBwoQ@mail.gmail.com>
Message-ID: <6fd974bf-4a67-48bb-20eb-dfc06ff445ef@gmail.com>

Hi Kokos

The first thing you need is a music play out system. Almost anything can 
play a random song from your collection; but; you have some conditions 
you want to place on the play out process.

I recommend a program called Rivendell which is free and will do 
everything you want.

http://static.paravelsystems.com/rivendell-install-rd3/rivendell-install-rhel7.html

There is a FB group and a mailing list and a Wiki.

The Rivendell system includes a stream creation program which will 
output mp3 or AAC+ or you can output the audio to a mixer and route that 
to a computer running darkice or whatever.

You will need a computer running Icecast2? and I recommend you do not 
try and run it on the same computer as Rivendell.

You can build Icecast2 on Ubuntu Server on almost anything.

If you want someone to be able to request a song 'on-line', something I 
caution you against, you can create web page code in perl or python 
which will achieve that.

All music is normalised to the same level which you have full control 
over. Big subject. Too big for here. You can install some dynamic 
processing.

You import your music, set up events to play it with separation rules. 
Put the events into clocks where you can add more selection rules.

Your home broadband will not support too many listeners. Depending on 
how much choke your ISP puts on your service; and they all do; you might 
get 3 or 4 reliable simultaneous connects so you will need a streaming 
service.

Depending where there are plenty of options. You get what you pay for.

Have fun.

regards


Robert

On 20/03/20 4:39 am, Konrad Kostecki wrote:
> Hi all!
>
> Thank you for having me. I'm a person who encourage a small local 
> community for musical involvement. It already kinda worked, we are 
> doing plenty of fantastic things together.
>
> What I am now thinking of is 24/7 Internet radio based on Icecast that 
> will air all of their non-professional music I gathered. Functions I'm 
> looking for:
> - frequent scanning of music directory to update music library for 
> dynamic playlist building
> - to shuffle music on playlist fairly to not have same artist played 
> two or more times in a row, so all artists could have a chance to be 
> aired equally
> - from web perspective to have possibility for end-users to select 
> songs which will be played next
> - replaygain support (radio mode, not album mode)
>
> Don't get me wrong, I'm not looking for any easy/ready solution, maybe 
> I'm not a coder but I can at least try to script something in bash or 
> Python. However, I'm confused regarding source clients available - 
> Liquidsoap, butt, MPD, DarkIce, DeeFuzzer, Ezstream (at least I find 
> these projects as quite active) - I have no experience with them and I 
> can't really find useful opinions. Can you tell which of them could be 
> best for described vision? I'd appreciate if you could recommend me 
> any way I could follow, which specific software components I would 
> possibly need to integrate. Even brief information will do!
>
> Thanks! Stay healthy!
> Kokos
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast

-- 
Communication Consultants 2020 Limited
64 Warner Park Avenue
Laingholm
Auckland 0604
New Zealand

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200320/1e975232/attachment.htm>

From mjcolorado89 at aol.com  Fri Mar 20 01:44:53 2020
From: mjcolorado89 at aol.com (Michael Hunt)
Date: Thu, 19 Mar 2020 21:44:53 -0400
Subject: [Icecast] Icecast source client with web request/voting for
	next to play function
In-Reply-To: <6fd974bf-4a67-48bb-20eb-dfc06ff445ef@gmail.com>
References: <CALPXi_Q46s+Gg+Ag5DgH7fu5K1KJJq5SK2cS-chqJsEFXEBwoQ@mail.gmail.com>
 <6fd974bf-4a67-48bb-20eb-dfc06ff445ef@gmail.com>
Message-ID: <004501d5fe59$285bffc0$7913ff40$@aol.com>

hayden at blindcafe.net <mailto:hayden at blindcafe.net> 

 

 

From: Icecast <icecast-bounces at xiph.org> On Behalf Of Robert Jeffares
Sent: Thursday, March 19, 2020 7:05 PM
To: icecast at xiph.org
Subject: Re: [Icecast] Icecast source client with web request/voting for next to play function

 

Hi Kokos

The first thing you need is a music play out system. Almost anything can play a random song from your collection; but; you have some conditions you want to place on the play out process.

I recommend a program called Rivendell which is free and will do everything you want.

http://static.paravelsystems.com/rivendell-install-rd3/rivendell-install-rhel7.html

There is a FB group and a mailing list and a Wiki.

The Rivendell system includes a stream creation program which will output mp3 or AAC+ or you can output the audio to a mixer and route that to a computer running darkice or whatever. 

You will need a computer running Icecast2  and I recommend you do not try and run it on the same computer as Rivendell.

You can build Icecast2 on Ubuntu Server on almost anything.

If you want someone to be able to request a song 'on-line', something I caution you against, you can create web page code in perl or python which will achieve that. 

All music is normalised to the same level which you have full control over. Big subject. Too big for here. You can install some dynamic processing. 

You import your music, set up events to play it with separation rules. Put the events into clocks where you can add more selection rules.

Your home broadband will not support too many listeners. Depending on how much choke your ISP puts on your service; and they all do; you might get 3 or 4 reliable simultaneous connects so you will need a streaming service. 

Depending where there are plenty of options. You get what you pay for.

Have fun.

regards

 

Robert

On 20/03/20 4:39 am, Konrad Kostecki wrote:

Hi all!

 

Thank you for having me. I'm a person who encourage a small local community for musical involvement. It already kinda worked, we are doing plenty of fantastic things together.

 

What I am now thinking of is 24/7 Internet radio based on Icecast that will air all of their non-professional music I gathered. Functions I'm looking for:

- frequent scanning of music directory to update music library for dynamic playlist building

- to shuffle music on playlist fairly to not have same artist played two or more times in a row, so all artists could have a chance to be aired equally

- from web perspective to have possibility for end-users to select songs which will be played next

- replaygain support (radio mode, not album mode)

 

Don't get me wrong, I'm not looking for any easy/ready solution, maybe I'm not a coder but I can at least try to script something in bash or Python. However, I'm confused regarding source clients available - Liquidsoap, butt, MPD, DarkIce, DeeFuzzer, Ezstream (at least I find these projects as quite active) - I have no experience with them and I can't really find useful opinions. Can you tell which of them could be best for described vision? I'd appreciate if you could recommend me any way I could follow, which specific software components I would possibly need to integrate. Even brief information will do!

 

Thanks! Stay healthy!

Kokos





_______________________________________________
Icecast mailing list
Icecast at xiph.org <mailto:Icecast at xiph.org> 
http://lists.xiph.org/mailman/listinfo/icecast

-- 
Communication Consultants 2020 Limited
64 Warner Park Avenue
Laingholm
Auckland 0604
New Zealand
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200319/40b1f032/attachment.htm>

From danny at gheraille.be  Fri Mar 20 14:06:34 2020
From: danny at gheraille.be (Danny Gheraille)
Date: Fri, 20 Mar 2020 14:06:34 +0000
Subject: [Icecast] Listenurl is not in HTTPS
Message-ID: <c7ea5c1be60a44068b2d10a131a9c6b8@gheraille.be>

I have successfully installed IceCast with SSL support : https://relay2.dgnet.be/

Stream is working fine with this URL : https://relay2.dgnet.be:443/different.ogg

Nevertheless the listen URL still points to http://relay2.dgnet.be:443/different.ogg ( without https then )
So the links provided/generated by IceCast are wrong .

What did I miss ?
Is it possible to force the listenurl value in the icecast.xml ?

Thanks in advance for your help,
Danny

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200320/dd2e9ecf/attachment.htm>

From danny at gheraille.be  Fri Mar 20 14:01:23 2020
From: danny at gheraille.be (Danny Gheraille)
Date: Fri, 20 Mar 2020 14:01:23 +0000
Subject: [Icecast] Listenurl is not in HTTPS
Message-ID: <ebc319a2cbb54765bdaaf9580cc2b6aa@gheraille.be>

I have successfully installed IceCast with SSL support : https://relay2.dgnet.be/

Stream is working fine with this URL : https://relay2.dgnet.be:443/different.ogg

Nevertheless the listen URL still points to http://relay2.dgnet.be:443/different.ogg ( without https then )
So the links provided/generated by IceCast are wrong .

What did I miss ?
Is it possible to force the listenurl value in the icecast.xml ?

Thanks in advance for your help,
Danny
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200320/16ed0b99/attachment.htm>

From d.geneste at illud.fr  Fri Mar 20 14:05:17 2020
From: d.geneste at illud.fr (Damien GENESTE)
Date: Fri, 20 Mar 2020 15:05:17 +0100
Subject: [Icecast] Issue with Wordpress in HTTPS and Icecast Stream URL
	in HTTP
In-Reply-To: <CAKCymP2YyzafcpO8_sR37=AZnuKczBfhA4RuCVZq-ooCNdtewg@mail.gmail.com>
References: <CAG4BS6bXiC=eOEKtpRz8JqNPK1uVr_Z4T2tsPvpLaeWNALqzYQ@mail.gmail.com>
 <CAKCymP2YyzafcpO8_sR37=AZnuKczBfhA4RuCVZq-ooCNdtewg@mail.gmail.com>
Message-ID: <CAG4BS6YXmcUCPH2hka+6boAiGceoNBJ33eojLFCMnsZ8374+CA@mail.gmail.com>

Hello,

Thank you for your help. I tried to follow steps on your link but it didn't
work. I used this one :
https://weekly-geekly.github.io/articles/350236/index.html

I finish all steps but when i try to launch icecast with : su icecast2 -s
/bin/bash icecast -c /usr/local/etc/icecast.xml

I get this error : /usr/local/etc/icecast.xml: line 1: syntax error near
unexpected token `newline'
/usr/local/etc/icecast.xml: line 1: `<icecast>'

Do you know how to fix it ?

BR,

*Ceelo*

On Wed, Mar 18, 2020 at 7:34 PM Chip <chiapas at aktivix.org> wrote:

> How about this:
>
>    - https://serverok.in/centovacast-enable-ssl-on-icecast
>
> You're welcome. Don't mention it :o)
>
> Chip Scooter
>
> On Wed, 18 Mar 2020 at 15:31, Damien GENESTE <d.geneste at illud.fr> wrote:
>
>> Hello,
>>
>> Configuration :
>> - Debian 8
>> - Wordpress 5.3.2 (Apache)
>> - Icecast 2
>> - Radio web player : Streamcast
>>
>> I just installed my Web radio that was working correctly in full HTTP.
>>
>> I add a Lets Encrypt certificat on my Wordpress that is now in HTTPS.
>> Since my Wordpress is in HTTPS, my stream on the website is not working.
>> The direct Link in HTTP is working correctly.
>>
>> I checked on the internet and it say "mixed content do not work". I was
>> not able to find a simple procedure to add HTTPS on my Icecast stream link.
>>
>> Could you please hell me with this ?
>>
>> Best regards,
>>
>> Damien
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org
>> http://lists.xiph.org/mailman/listinfo/icecast
>>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200320/4c7ef0eb/attachment.htm>

From d.geneste at illud.fr  Fri Mar 20 14:13:11 2020
From: d.geneste at illud.fr (Damien GENESTE)
Date: Fri, 20 Mar 2020 15:13:11 +0100
Subject: [Icecast] Listenurl is not in HTTPS
In-Reply-To: <c7ea5c1be60a44068b2d10a131a9c6b8@gheraille.be>
References: <c7ea5c1be60a44068b2d10a131a9c6b8@gheraille.be>
Message-ID: <CAG4BS6bigg2P7hKFHj03R1YJcMX4tNTpkWS6axEt3U3R1k_RLg@mail.gmail.com>

Hello,

If you are using liquidsoap, check the URL in your .liq.

BR,

*Ceelo*


On Fri, Mar 20, 2020 at 3:06 PM Danny Gheraille <danny at gheraille.be> wrote:

> I have successfully installed IceCast with SSL support :
> https://relay2.dgnet.be/
>
>
>
> Stream is working fine with this URL :
> https://relay2.dgnet.be:443/different.ogg
>
>
>
> Nevertheless the listen URL still points to
> http://relay2.dgnet.be:443/different.ogg ( without https then )
>
> So the links provided/generated by IceCast are wrong .
>
>
>
> What did I miss ?
> Is it possible to force the listenurl value in the icecast.xml ?
>
>
>
> Thanks in advance for your help,
>
> Danny
>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200320/523f3bb4/attachment.htm>

From chiapas at aktivix.org  Fri Mar 20 14:27:16 2020
From: chiapas at aktivix.org (Chip)
Date: Fri, 20 Mar 2020 14:27:16 +0000
Subject: [Icecast] Issue with Wordpress in HTTPS and Icecast Stream URL
	in HTTP
In-Reply-To: <CAG4BS6YXmcUCPH2hka+6boAiGceoNBJ33eojLFCMnsZ8374+CA@mail.gmail.com>
References: <CAG4BS6bXiC=eOEKtpRz8JqNPK1uVr_Z4T2tsPvpLaeWNALqzYQ@mail.gmail.com>
 <CAKCymP2YyzafcpO8_sR37=AZnuKczBfhA4RuCVZq-ooCNdtewg@mail.gmail.com>
 <CAG4BS6YXmcUCPH2hka+6boAiGceoNBJ33eojLFCMnsZ8374+CA@mail.gmail.com>
Message-ID: <CAKCymP2auzcFw1MejtXHpebj3zGTLaW7jaPBguZL6BwsSyyGfg@mail.gmail.com>

Syntax error in your conf file.

Check it from the command line using: *xmllint icecast.xml*

That will show you the error.

Or use something like this: https://xmlvalidation.com/

Probably an unclosed tag.

You're welcome. Don't mention it :o)

Chip Scooter

On Fri, 20 Mar 2020 at 14:06, Damien GENESTE <d.geneste at illud.fr> wrote:

> Hello,
>
> Thank you for your help. I tried to follow steps on your link but it
> didn't work. I used this one :
> https://weekly-geekly.github.io/articles/350236/index.html
>
> I finish all steps but when i try to launch icecast with : su icecast2 -s
> /bin/bash icecast -c /usr/local/etc/icecast.xml
>
> I get this error : /usr/local/etc/icecast.xml: line 1: syntax error near
> unexpected token `newline'
> /usr/local/etc/icecast.xml: line 1: `<icecast>'
>
> Do you know how to fix it ?
>
> BR,
>
> *Ceelo*
>
> On Wed, Mar 18, 2020 at 7:34 PM Chip <chiapas at aktivix.org> wrote:
>
>> How about this:
>>
>>    - https://serverok.in/centovacast-enable-ssl-on-icecast
>>
>> You're welcome. Don't mention it :o)
>>
>> Chip Scooter
>>
>> On Wed, 18 Mar 2020 at 15:31, Damien GENESTE <d.geneste at illud.fr> wrote:
>>
>>> Hello,
>>>
>>> Configuration :
>>> - Debian 8
>>> - Wordpress 5.3.2 (Apache)
>>> - Icecast 2
>>> - Radio web player : Streamcast
>>>
>>> I just installed my Web radio that was working correctly in full HTTP.
>>>
>>> I add a Lets Encrypt certificat on my Wordpress that is now in HTTPS.
>>> Since my Wordpress is in HTTPS, my stream on the website is not working.
>>> The direct Link in HTTP is working correctly.
>>>
>>> I checked on the internet and it say "mixed content do not work". I was
>>> not able to find a simple procedure to add HTTPS on my Icecast stream link.
>>>
>>> Could you please hell me with this ?
>>>
>>> Best regards,
>>>
>>> Damien
>>> _______________________________________________
>>> Icecast mailing list
>>> Icecast at xiph.org
>>> http://lists.xiph.org/mailman/listinfo/icecast
>>>
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org
>> http://lists.xiph.org/mailman/listinfo/icecast
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200320/115b0c8b/attachment.htm>

From d.geneste at illud.fr  Fri Mar 20 14:55:36 2020
From: d.geneste at illud.fr (Damien GENESTE)
Date: Fri, 20 Mar 2020 15:55:36 +0100
Subject: [Icecast] Issue with Wordpress in HTTPS and Icecast Stream URL
	in HTTP
In-Reply-To: <CAKCymP2auzcFw1MejtXHpebj3zGTLaW7jaPBguZL6BwsSyyGfg@mail.gmail.com>
References: <CAG4BS6bXiC=eOEKtpRz8JqNPK1uVr_Z4T2tsPvpLaeWNALqzYQ@mail.gmail.com>
 <CAKCymP2YyzafcpO8_sR37=AZnuKczBfhA4RuCVZq-ooCNdtewg@mail.gmail.com>
 <CAG4BS6YXmcUCPH2hka+6boAiGceoNBJ33eojLFCMnsZ8374+CA@mail.gmail.com>
 <CAKCymP2auzcFw1MejtXHpebj3zGTLaW7jaPBguZL6BwsSyyGfg@mail.gmail.com>
Message-ID: <CAG4BS6bitQOb9XdYDTE0s=nYgS4wofqafA7HdS+FkhfwXXh7EQ@mail.gmail.com>

Hello Chip,

I have no error in my file. I also test my previous XML file that was
working and it say the same error :  line 1: syntax error near unexpected
token `newline'
/usr/local/etc/icecast.xml: line 1: `<icecast>'

BR,

Ceelo



On Fri, Mar 20, 2020 at 3:27 PM Chip <chiapas at aktivix.org> wrote:

> Syntax error in your conf file.
>
> Check it from the command line using: *xmllint icecast.xml*
>
> That will show you the error.
>
> Or use something like this: https://xmlvalidation.com/
>
> Probably an unclosed tag.
>
> You're welcome. Don't mention it :o)
>
> Chip Scooter
>
> On Fri, 20 Mar 2020 at 14:06, Damien GENESTE <d.geneste at illud.fr> wrote:
>
>> Hello,
>>
>> Thank you for your help. I tried to follow steps on your link but it
>> didn't work. I used this one :
>> https://weekly-geekly.github.io/articles/350236/index.html
>>
>> I finish all steps but when i try to launch icecast with : su icecast2 -s
>> /bin/bash icecast -c /usr/local/etc/icecast.xml
>>
>> I get this error : /usr/local/etc/icecast.xml: line 1: syntax error near
>> unexpected token `newline'
>> /usr/local/etc/icecast.xml: line 1: `<icecast>'
>>
>> Do you know how to fix it ?
>>
>> BR,
>>
>> *Ceelo*
>>
>> On Wed, Mar 18, 2020 at 7:34 PM Chip <chiapas at aktivix.org> wrote:
>>
>>> How about this:
>>>
>>>    - https://serverok.in/centovacast-enable-ssl-on-icecast
>>>
>>> You're welcome. Don't mention it :o)
>>>
>>> Chip Scooter
>>>
>>> On Wed, 18 Mar 2020 at 15:31, Damien GENESTE <d.geneste at illud.fr> wrote:
>>>
>>>> Hello,
>>>>
>>>> Configuration :
>>>> - Debian 8
>>>> - Wordpress 5.3.2 (Apache)
>>>> - Icecast 2
>>>> - Radio web player : Streamcast
>>>>
>>>> I just installed my Web radio that was working correctly in full HTTP.
>>>>
>>>> I add a Lets Encrypt certificat on my Wordpress that is now in HTTPS.
>>>> Since my Wordpress is in HTTPS, my stream on the website is not working.
>>>> The direct Link in HTTP is working correctly.
>>>>
>>>> I checked on the internet and it say "mixed content do not work". I was
>>>> not able to find a simple procedure to add HTTPS on my Icecast stream link.
>>>>
>>>> Could you please hell me with this ?
>>>>
>>>> Best regards,
>>>>
>>>> Damien
>>>> _______________________________________________
>>>> Icecast mailing list
>>>> Icecast at xiph.org
>>>> http://lists.xiph.org/mailman/listinfo/icecast
>>>>
>>> _______________________________________________
>>> Icecast mailing list
>>> Icecast at xiph.org
>>> http://lists.xiph.org/mailman/listinfo/icecast
>>>
>> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200320/85b8b8da/attachment.htm>

From danny at gheraille.be  Fri Mar 20 15:13:31 2020
From: danny at gheraille.be (Danny Gheraille)
Date: Fri, 20 Mar 2020 15:13:31 +0000
Subject: [Icecast] Listenurl is not in HTTPS
In-Reply-To: <CAG4BS6bigg2P7hKFHj03R1YJcMX4tNTpkWS6axEt3U3R1k_RLg@mail.gmail.com>
References: <c7ea5c1be60a44068b2d10a131a9c6b8@gheraille.be>
 <CAG4BS6bigg2P7hKFHj03R1YJcMX4tNTpkWS6axEt3U3R1k_RLg@mail.gmail.com>
Message-ID: <f35ee91e131b4cb08fce80613757c7e8@gheraille.be>

No,  this is a relay of a Shoutcast server.

Everything is configured in https on IceCast ( https://relay2.dgnet.be/ ) , except this value listenurl ( in Admin / Mountpoint) which in cannot change apparently.

So the .m3u file is created with an http:// link ( instead of https:// )
But the stream is available and working  in https://relay2.dgnet.be:443/different.ogg

Danny

From: Icecast <icecast-bounces at xiph.org> On Behalf Of Damien GENESTE
Sent: Friday, March 20, 2020 3:13 PM
To: Icecast streaming server user discussions <icecast at xiph.org>
Subject: Re: [Icecast] Listenurl is not in HTTPS

Hello,

If you are using liquidsoap, check the URL in your .liq.

BR,

Ceelo


On Fri, Mar 20, 2020 at 3:06 PM Danny Gheraille <danny at gheraille.be<mailto:danny at gheraille.be>> wrote:
I have successfully installed IceCast with SSL support : https://relay2.dgnet.be/

Stream is working fine with this URL : https://relay2.dgnet.be:443/different.ogg

Nevertheless the listen URL still points to http://relay2.dgnet.be:443/different.ogg ( without https then )
So the links provided/generated by IceCast are wrong .

What did I miss ?
Is it possible to force the listenurl value in the icecast.xml ?

Thanks in advance for your help,
Danny

_______________________________________________
Icecast mailing list
Icecast at xiph.org<mailto:Icecast at xiph.org>
http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200320/1cae096c/attachment.htm>

From robert at webtent.org  Fri Mar 20 15:20:55 2020
From: robert at webtent.org (Robert Fitzpatrick)
Date: Fri, 20 Mar 2020 11:20:55 -0400
Subject: [Icecast] Listenurl is not in HTTPS
In-Reply-To: <f35ee91e131b4cb08fce80613757c7e8@gheraille.be>
References: <c7ea5c1be60a44068b2d10a131a9c6b8@gheraille.be>
 <CAG4BS6bigg2P7hKFHj03R1YJcMX4tNTpkWS6axEt3U3R1k_RLg@mail.gmail.com>
 <f35ee91e131b4cb08fce80613757c7e8@gheraille.be>
Message-ID: <ce38a49a-d6f4-5482-7edc-6bdfd3244fd4@webtent.org>

Danny Gheraille wrote on 3/20/2020 11:13 AM:
> No, ?this is a relay of a Shoutcast server.
> 
> Everything is configured in https on IceCast ( https://relay2.dgnet.be/ 
> ) , except this value listenurl ( in Admin / Mountpoint) which in cannot 
> change apparently.
> 
> So the .m3u file is created with an http:// link ( instead of https:// )
> But the stream is available and working ?in 
> https://relay2.dgnet.be:443/different.ogg
> 
I had to create files for each mount point in the web root. For 
instance, a mount of /mymount on mystream.org would be:

user at stream:~$ cat /usr/share/icecast2/web/mymount.m3u
https://mystream.org/mymount

-- 
Robert



From d.geneste at illud.fr  Fri Mar 20 15:53:03 2020
From: d.geneste at illud.fr (Damien GENESTE)
Date: Fri, 20 Mar 2020 16:53:03 +0100
Subject: [Icecast] Issue with Wordpress in HTTPS and Icecast Stream URL
	in HTTP
In-Reply-To: <CAG4BS6bitQOb9XdYDTE0s=nYgS4wofqafA7HdS+FkhfwXXh7EQ@mail.gmail.com>
References: <CAG4BS6bXiC=eOEKtpRz8JqNPK1uVr_Z4T2tsPvpLaeWNALqzYQ@mail.gmail.com>
 <CAKCymP2YyzafcpO8_sR37=AZnuKczBfhA4RuCVZq-ooCNdtewg@mail.gmail.com>
 <CAG4BS6YXmcUCPH2hka+6boAiGceoNBJ33eojLFCMnsZ8374+CA@mail.gmail.com>
 <CAKCymP2auzcFw1MejtXHpebj3zGTLaW7jaPBguZL6BwsSyyGfg@mail.gmail.com>
 <CAG4BS6bitQOb9XdYDTE0s=nYgS4wofqafA7HdS+FkhfwXXh7EQ@mail.gmail.com>
Message-ID: <CAG4BS6ZuLRk-VBGSVdw2rJDB5p3E6xZXRk6tz4ZTJKdGiQ8hEg@mail.gmail.com>

It's worrrrrrrking, thanks Chip,

These commands was missing :

sudo ln -s /usr/local/bin/icecast /usr/bin/icecast2
sudo ln -s /usr/local/share/icecast /usr/share/icecast2


*BR*

*Ceelo*


On Fri, Mar 20, 2020 at 3:55 PM Damien GENESTE <d.geneste at illud.fr> wrote:

> Hello Chip,
>
> I have no error in my file. I also test my previous XML file that was
> working and it say the same error :  line 1: syntax error near unexpected
> token `newline'
> /usr/local/etc/icecast.xml: line 1: `<icecast>'
>
> BR,
>
> Ceelo
>
>
>
> On Fri, Mar 20, 2020 at 3:27 PM Chip <chiapas at aktivix.org> wrote:
>
>> Syntax error in your conf file.
>>
>> Check it from the command line using: *xmllint icecast.xml*
>>
>> That will show you the error.
>>
>> Or use something like this: https://xmlvalidation.com/
>>
>> Probably an unclosed tag.
>>
>> You're welcome. Don't mention it :o)
>>
>> Chip Scooter
>>
>> On Fri, 20 Mar 2020 at 14:06, Damien GENESTE <d.geneste at illud.fr> wrote:
>>
>>> Hello,
>>>
>>> Thank you for your help. I tried to follow steps on your link but it
>>> didn't work. I used this one :
>>> https://weekly-geekly.github.io/articles/350236/index.html
>>>
>>> I finish all steps but when i try to launch icecast with : su icecast2
>>> -s /bin/bash icecast -c /usr/local/etc/icecast.xml
>>>
>>> I get this error : /usr/local/etc/icecast.xml: line 1: syntax error near
>>> unexpected token `newline'
>>> /usr/local/etc/icecast.xml: line 1: `<icecast>'
>>>
>>> Do you know how to fix it ?
>>>
>>> BR,
>>>
>>> *Ceelo*
>>>
>>> On Wed, Mar 18, 2020 at 7:34 PM Chip <chiapas at aktivix.org> wrote:
>>>
>>>> How about this:
>>>>
>>>>    - https://serverok.in/centovacast-enable-ssl-on-icecast
>>>>
>>>> You're welcome. Don't mention it :o)
>>>>
>>>> Chip Scooter
>>>>
>>>> On Wed, 18 Mar 2020 at 15:31, Damien GENESTE <d.geneste at illud.fr>
>>>> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> Configuration :
>>>>> - Debian 8
>>>>> - Wordpress 5.3.2 (Apache)
>>>>> - Icecast 2
>>>>> - Radio web player : Streamcast
>>>>>
>>>>> I just installed my Web radio that was working correctly in full HTTP.
>>>>>
>>>>> I add a Lets Encrypt certificat on my Wordpress that is now in HTTPS.
>>>>> Since my Wordpress is in HTTPS, my stream on the website is not working.
>>>>> The direct Link in HTTP is working correctly.
>>>>>
>>>>> I checked on the internet and it say "mixed content do not work". I
>>>>> was not able to find a simple procedure to add HTTPS on my Icecast stream
>>>>> link.
>>>>>
>>>>> Could you please hell me with this ?
>>>>>
>>>>> Best regards,
>>>>>
>>>>> Damien
>>>>> _______________________________________________
>>>>> Icecast mailing list
>>>>> Icecast at xiph.org
>>>>> http://lists.xiph.org/mailman/listinfo/icecast
>>>>>
>>>> _______________________________________________
>>>> Icecast mailing list
>>>> Icecast at xiph.org
>>>> http://lists.xiph.org/mailman/listinfo/icecast
>>>>
>>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org
>> http://lists.xiph.org/mailman/listinfo/icecast
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200320/2aa5b7ed/attachment.htm>

From webmaster at berean-biblechurch.org  Sat Mar 21 00:56:38 2020
From: webmaster at berean-biblechurch.org (webmaster at berean-biblechurch.org)
Date: Fri, 20 Mar 2020 19:56:38 -0500
Subject: [Icecast] Listenurl is not in HTTPS
In-Reply-To: <c7ea5c1be60a44068b2d10a131a9c6b8@gheraille.be>
References: <c7ea5c1be60a44068b2d10a131a9c6b8@gheraille.be>
Message-ID: <0420c6beada25500fbb399c75d9a3d73@berean-biblechurch.org>

Danny, 

Are you talking about the listen URL in the Icecast status page?  I
think it is currently not able show the link as httpS.  Maybe one of the
Icecast experts can confirm that. 

In case you didn't know, you don't need the port (:443) in the URL. 

Is this truly an OGG audio file?  Why does the server response give a
Content-Type of "audio/mpeg"? 

Justin

On 2020-03-20 09:06, Danny Gheraille wrote:

> I have successfully installed IceCast with SSL support : https://relay2.dgnet.be/ [1] 
> 
> Stream is working fine with this URL : https://relay2.dgnet.be:443/different.ogg [2] 
> 
> Nevertheless the listen URL still points to http://relay2.dgnet.be:443/different.ogg ( without https then ) 
> 
> So the links provided/generated by IceCast are wrong . 
> 
> What did I miss ? 
> Is it possible to force the listenurl value in the icecast.xml ? 
> 
> Thanks in advance for your help, 
> 
> Danny 
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
 

Links:
------
[1] https://relay2.dgnet.be/
[2] https://relay2.dgnet.be:443/different.ogg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200320/fba1549d/attachment.htm>

From danny at gheraille.be  Sat Mar 21 09:51:13 2020
From: danny at gheraille.be (Danny Gheraille)
Date: Sat, 21 Mar 2020 09:51:13 +0000
Subject: [Icecast] Listenurl is not in HTTPS
In-Reply-To: <0420c6beada25500fbb399c75d9a3d73@berean-biblechurch.org>
References: <c7ea5c1be60a44068b2d10a131a9c6b8@gheraille.be>
 <0420c6beada25500fbb399c75d9a3d73@berean-biblechurch.org>
Message-ID: <8b3cb904b86045f7a94870bb69665a88@gheraille.be>

Hi Justin,


>Are you talking about the listen URL in the Icecast status page?  I think it is currently not able show the link as httpS.  Maybe one of the Icecast experts can confirm that.
Yes I was talking about this value.
The workaround was to put my own m3u file ( with the correct link )  in the icecast web folder


> Is this truly an OGG audio file?  Why does the server response give a Content-Type of "audio/mpeg"?
Indeed, this is a relay of an audio/mpeg Shoucast stream .
Is this a problem ? should I change something in the config to be more compliant with Icecast best practices

Thanks for your help,
Danny

From: webmaster at berean-biblechurch.org <webmaster at berean-biblechurch.org>
Sent: samedi 21 mars 2020 01:57
To: Icecast streaming server user discussions <icecast at xiph.org>
Cc: Danny Gheraille <danny at gheraille.be>
Subject: Re: [Icecast] Listenurl is not in HTTPS


Danny,

Are you talking about the listen URL in the Icecast status page?  I think it is currently not able show the link as httpS.  Maybe one of the Icecast experts can confirm that.

In case you didn't know, you don't need the port (:443) in the URL.

Is this truly an OGG audio file?  Why does the server response give a Content-Type of "audio/mpeg"?



Justin




On 2020-03-20 09:06, Danny Gheraille wrote:
I have successfully installed IceCast with SSL support : https://relay2.dgnet.be/

Stream is working fine with this URL : https://relay2.dgnet.be:443/different.ogg

Nevertheless the listen URL still points to http://relay2.dgnet.be:443/different.ogg ( without https then )
So the links provided/generated by IceCast are wrong .

What did I miss ?
Is it possible to force the listenurl value in the icecast.xml ?

Thanks in advance for your help,
Danny


_______________________________________________
Icecast mailing list
Icecast at xiph.org<mailto:Icecast at xiph.org>
http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200321/02776baa/attachment.htm>

From tim at tjbaker.co.uk  Sat Mar 21 16:51:26 2020
From: tim at tjbaker.co.uk (Tim Baker)
Date: Sat, 21 Mar 2020 16:51:26 +0000
Subject: [Icecast] Problem with HTTP stream but not HTTPS.
Message-ID: <D3655A3A-1CD1-4604-A43C-BE1A57E908D2@tjbaker.co.uk>

Strange issue - not sure if something has changed in Icecast2, but suddenly my long-running stream won?t connect to 8000 and says 'File or directory not found?

http://listen.radioclash.com:8000/ <http://listen.radioclash.com:8000/>

but will happily connect to the SSL port I?ve set up

https://listen.radioclash.com:8443/ <https://listen.radioclash.com:8443/>

I am using Liquidsoap to create the streams, it?s an Auto DJ station?problem is the URL I use for TuneIn etc is the HTTP one, could redirect but better to fix why the HTTP is doing that all of a sudden - but it was working until fairly recently.

Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200321/2d6fbd32/attachment.htm>

From yahav.shasha at gmail.com  Sat Mar 21 17:12:53 2020
From: yahav.shasha at gmail.com (Yahav Shasha)
Date: Sat, 21 Mar 2020 19:12:53 +0200
Subject: [Icecast] Problem with HTTP stream but not HTTPS.
In-Reply-To: <D3655A3A-1CD1-4604-A43C-BE1A57E908D2@tjbaker.co.uk>
References: <D3655A3A-1CD1-4604-A43C-BE1A57E908D2@tjbaker.co.uk>
Message-ID: <CABuab=SOL8+rtM=t_7J6koWav9kSX=c7U+y3AWBqXg8AUkg+WQ@mail.gmail.com>

Perhaps you should include your config and error log (while set to debug)

On Sat, Mar 21, 2020 at 7:10 PM Tim Baker <tim at tjbaker.co.uk> wrote:

> Strange issue - not sure if something has changed in Icecast2, but
> suddenly my long-running stream won?t connect to 8000 and says 'File or
> directory not found?
>
> http://listen.radioclash.com:8000/
>
> but will happily connect to the SSL port I?ve set up
>
> https://listen.radioclash.com:8443/
>
> I am using Liquidsoap to create the streams, it?s an Auto DJ
> station?problem is the URL I use for TuneIn etc is the HTTP one, could
> redirect but better to fix why the HTTP is doing that all of a sudden - but
> it was working until fairly recently.
>
> Tim
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200321/98df47cc/attachment.htm>

From jordan at coolmic.net  Sat Mar 21 17:21:26 2020
From: jordan at coolmic.net (Jordan Erickson)
Date: Sat, 21 Mar 2020 10:21:26 -0700
Subject: [Icecast] Problem with HTTP stream but not HTTPS.
In-Reply-To: <D3655A3A-1CD1-4604-A43C-BE1A57E908D2@tjbaker.co.uk>
References: <D3655A3A-1CD1-4604-A43C-BE1A57E908D2@tjbaker.co.uk>
Message-ID: <38089e18-d380-7a20-00ac-881253a16c23@coolmic.net>

Likely Google Chrome's recent change to disallow HTTP streams
(subresources) within HTTPS URLs?

https://security.googleblog.com/2019/10/no-more-mixed-messages-about-https_3.html


Cheers,
Jordan



On 3/21/20 9:51 AM, Tim Baker wrote:
> Strange issue - not sure if something has changed in Icecast2, but
> suddenly my long-running stream won?t connect to 8000 and says 'File or
> directory not found?
> 
> http://listen.radioclash.com:8000/
> 
> but will happily connect to the SSL port I?ve set up
> 
> https://listen.radioclash.com:8443/
> 
> I am using Liquidsoap to create the streams, it?s an Auto DJ
> station?problem is the URL I use for TuneIn etc is the HTTP one, could
> redirect but better to fix why the HTTP is doing that all of a sudden -
> but it was working until fairly recently.
> 
> Tim
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
> 


From greg at indexcom.com  Sat Mar 21 18:50:26 2020
From: greg at indexcom.com (Greg Ogonowski)
Date: Sat, 21 Mar 2020 11:50:26 -0700
Subject: [Icecast] Problem with HTTP stream but not HTTPS.
In-Reply-To: <D3655A3A-1CD1-4604-A43C-BE1A57E908D2@tjbaker.co.uk>
References: <D3655A3A-1CD1-4604-A43C-BE1A57E908D2@tjbaker.co.uk>
Message-ID: <004c01d5ffb1$95e62580$c1b27080$@indexcom.com>

Best to change to hls.

Icy is doomed.

/g.

 

 

From: Icecast <icecast-bounces at xiph.org> On Behalf Of Tim Baker
Sent: Saturday, 21 March, 2020 09:51
To: Icecast at xiph.org
Subject: [Icecast] Problem with HTTP stream but not HTTPS.

 

Strange issue - not sure if something has changed in Icecast2, but suddenly my long-running stream won?t connect to 8000 and says 'File or directory not found?

 

http://listen.radioclash.com:8000/

 

but will happily connect to the SSL port I?ve set up

 

https://listen.radioclash.com:8443/

 

I am using Liquidsoap to create the streams, it?s an Auto DJ station?problem is the URL I use for TuneIn etc is the HTTP one, could redirect but better to fix why the HTTP is doing that all of a sudden - but it was working until fairly recently.

 

Tim

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200321/0cbd80d4/attachment.htm>

From gavin at stephens.net.nz  Sat Mar 21 19:07:25 2020
From: gavin at stephens.net.nz (Gavin Stephens)
Date: Sun, 22 Mar 2020 08:07:25 +1300
Subject: [Icecast] Problem with HTTP stream but not HTTPS.
In-Reply-To: <004c01d5ffb1$95e62580$c1b27080$@indexcom.com>
References: <D3655A3A-1CD1-4604-A43C-BE1A57E908D2@tjbaker.co.uk>
 <004c01d5ffb1$95e62580$c1b27080$@indexcom.com>
Message-ID: <0b501db1-3844-5970-6680-668bf91dcaf2@stephens.net.nz>

If you use Chrome, recent updates won't allow connections to an http 
server if the referring url is on an https server.

I wonder how much additional CPU strain this causes when you have a few 
hundred plus listeners to encrypt everything. Anyway, this is the way it 
is now, unless you use the likes of .pls/.m3u files with the http server 
link for an external player.


Cheers,

Gavin.


On 22/03/2020 7:50 am, Greg Ogonowski wrote:
>
> Best to change to hls.
>
> Icy is doomed.
>
> /g.
>
> *From:* Icecast <icecast-bounces at xiph.org> *On Behalf Of *Tim Baker
> *Sent:* Saturday, 21 March, 2020 09:51
> *To:* Icecast at xiph.org
> *Subject:* [Icecast] Problem with HTTP stream but not HTTPS.
>
> Strange issue - not sure if something has changed in Icecast2, but 
> suddenly my long-running stream won?t connect to 8000 and says 'File 
> or directory not found?
>
> http://listen.radioclash.com:8000/
>
> but will happily connect to the SSL port I?ve set up
>
> https://listen.radioclash.com:8443/
>
> I am using Liquidsoap to create the streams, it?s an Auto DJ 
> station?problem is the URL I use for TuneIn etc is the HTTP one, could 
> redirect but better to fix why the HTTP is doing that all of a sudden 
> - but it was working until fairly recently.
>
> Tim
>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200322/1654f87a/attachment.htm>

From gavin at stephens.net.nz  Sat Mar 21 19:41:12 2020
From: gavin at stephens.net.nz (Gavin Stephens)
Date: Sun, 22 Mar 2020 08:41:12 +1300
Subject: [Icecast] Problem with HTTP stream but not HTTPS.
In-Reply-To: <0b501db1-3844-5970-6680-668bf91dcaf2@stephens.net.nz>
References: <D3655A3A-1CD1-4604-A43C-BE1A57E908D2@tjbaker.co.uk>
 <004c01d5ffb1$95e62580$c1b27080$@indexcom.com>
 <0b501db1-3844-5970-6680-668bf91dcaf2@stephens.net.nz>
Message-ID: <58fb0e8c-11ff-a255-eae4-bf121204c618@stephens.net.nz>

Sorry thought it may have been related.


On 22/03/2020 8:07 am, Gavin Stephens wrote:
>
> If you use Chrome, recent updates won't allow connections to an http 
> server if the referring url is on an https server.
>
> I wonder how much additional CPU strain this causes when you have a 
> few hundred plus listeners to encrypt everything. Anyway, this is the 
> way it is now, unless you use the likes of .pls/.m3u files with the 
> http server link for an external player.
>
>
> Cheers,
>
> Gavin.
>
>
> On 22/03/2020 7:50 am, Greg Ogonowski wrote:
>>
>> Best to change to hls.
>>
>> Icy is doomed.
>>
>> /g.
>>
>> *From:* Icecast <icecast-bounces at xiph.org> *On Behalf Of *Tim Baker
>> *Sent:* Saturday, 21 March, 2020 09:51
>> *To:* Icecast at xiph.org
>> *Subject:* [Icecast] Problem with HTTP stream but not HTTPS.
>>
>> Strange issue - not sure if something has changed in Icecast2, but 
>> suddenly my long-running stream won?t connect to 8000 and says 'File 
>> or directory not found?
>>
>> http://listen.radioclash.com:8000/
>>
>> but will happily connect to the SSL port I?ve set up
>>
>> https://listen.radioclash.com:8443/
>>
>> I am using Liquidsoap to create the streams, it?s an Auto DJ 
>> station?problem is the URL I use for TuneIn etc is the HTTP one, 
>> could redirect but better to fix why the HTTP is doing that all of a 
>> sudden - but it was working until fairly recently.
>>
>> Tim
>>
>>
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org
>> http://lists.xiph.org/mailman/listinfo/icecast
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200322/04c3a761/attachment.htm>

From webmaster at berean-biblechurch.org  Sun Mar 22 00:46:55 2020
From: webmaster at berean-biblechurch.org (webmaster at berean-biblechurch.org)
Date: Sat, 21 Mar 2020 19:46:55 -0500
Subject: [Icecast] Listenurl is not in HTTPS
In-Reply-To: <8b3cb904b86045f7a94870bb69665a88@gheraille.be>
References: <c7ea5c1be60a44068b2d10a131a9c6b8@gheraille.be>
 <0420c6beada25500fbb399c75d9a3d73@berean-biblechurch.org>
 <8b3cb904b86045f7a94870bb69665a88@gheraille.be>
Message-ID: <110e2aecb3f94e9917f58df05e934c6d@berean-biblechurch.org>

I'd have to defer to more knowledgeable Icecasters than me to answer if
your config needs to change.  (I don't have experience with relays.) 

However, if the file is an OGG, I'd expect a mime type of "audio/ogg". 
I don't know if that needs to be set on the origin stream or your relay.


Justin

On 2020-03-21 04:51, Danny Gheraille wrote:

> Hi Justin, 
> 
>> Are you talking about the listen URL in the Icecast status page?  I think it is currently not able show the link as httpS.  Maybe one of the Icecast experts can confirm that. 
> 
> Yes I was talking about this value.
> The workaround was to put my own m3u file ( with the correct link )  in the icecast web folder 
> 
>> Is this truly an OGG audio file?  Why does the server response give a Content-Type of "audio/mpeg"? 
> 
> Indeed, this is a relay of an audio/mpeg Shoucast stream . 
> Is this a problem ? should I change something in the config to be more compliant with Icecast best practices 
> 
> Thanks for your help,
> Danny 
> 
> FROM: webmaster at berean-biblechurch.org <webmaster at berean-biblechurch.org> 
> SENT: samedi 21 mars 2020 01:57
> TO: Icecast streaming server user discussions <icecast at xiph.org>
> CC: Danny Gheraille <danny at gheraille.be>
> SUBJECT: Re: [Icecast] Listenurl is not in HTTPS 
> 
> Danny, 
> 
> Are you talking about the listen URL in the Icecast status page?  I think it is currently not able show the link as httpS.  Maybe one of the Icecast experts can confirm that. 
> 
> In case you didn't know, you don't need the port (:443) in the URL. 
> 
> Is this truly an OGG audio file?  Why does the server response give a Content-Type of "audio/mpeg"? 
> 
> Justin
> 
> On 2020-03-20 09:06, Danny Gheraille wrote:
> 
>> I have successfully installed IceCast with SSL support : https://relay2.dgnet.be/ 
>> 
>> Stream is working fine with this URL : https://relay2.dgnet.be:443/different.ogg 
>> 
>> Nevertheless the listen URL still points to http://relay2.dgnet.be:443/different.ogg ( without https then ) 
>> 
>> So the links provided/generated by IceCast are wrong . 
>> 
>> What did I miss ? 
>> Is it possible to force the listenurl value in the icecast.xml ? 
>> 
>> Thanks in advance for your help, 
>> 
>> Danny 
>> 
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org
>> http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200321/622039ca/attachment.htm>

From webmaster at berean-biblechurch.org  Thu Mar 26 01:24:40 2020
From: webmaster at berean-biblechurch.org (webmaster at berean-biblechurch.org)
Date: Wed, 25 Mar 2020 20:24:40 -0500
Subject: [Icecast] making sense of the stats
Message-ID: <67572a3fa5f738b576eb80b378a3c7b6@berean-biblechurch.org>

I can't make sense of the connection stats on the admin page.  We have
one source and one mountpoint. 

What is the difference between _client_connections_ and _clients_ and
_connection_s?  How can they be so different in value?  Same questions
for _listener_connections_ and _listeners_?  The connections values seem
high for only 5 listeners and one admin. 

Here is a snapshot of the admin page a few minutes after the server was
started and mountpoint was made available: 

            client_connections
            18

            clients
            7

            connections
            24

            file_connections
            0

            listener_connections
            17

            listeners
            5

            source_client_connections
            1

            source_relay_connections
            0

            source_total_connections
            1

            sources
            1

            stats
            0

            stats_connections
            0

     Mountpoint /live.mp3
              listener_peak
              6

              listeners
              5

              max_listeners
              unlimited 

After more people started to connect, the admin #s got even more whacky.


Then, I have the max clients set to 25, yet the mountpoint says
'unlimited' listeners.  Why the difference here?  Aren't listeners also
clients? 

<limits>
  <clients>25</clients>
  <sources>1</sources> 

Thanks,
Justin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200325/651fd046/attachment.htm>

From jeffares.robert at gmail.com  Thu Mar 26 05:18:05 2020
From: jeffares.robert at gmail.com (Robert Jeffares)
Date: Thu, 26 Mar 2020 18:18:05 +1300
Subject: [Icecast] making sense of the stats
In-Reply-To: <67572a3fa5f738b576eb80b378a3c7b6@berean-biblechurch.org>
References: <67572a3fa5f738b576eb80b378a3c7b6@berean-biblechurch.org>
Message-ID: <db63ddfe-25fe-61eb-8304-dbbb910204d2@gmail.com>

Hi Justin,

/*? Aren't listeners also clients?*/

No.

Icecast xml is a bit daunting.

There are two kinds of connections.

Listener and Client

Client:...

Connections from your source which may be darkice, BUTT, or some other 
encoder.

You actually need plenty of these. I set mine to 20 when I have 4 services.

One client may have several connections. I assume there is some 
handshaking and there may be metadata as well.

Listener:...

Connections from anyone using the mount address which may be a listener 
or a relay.

The same listener can connect more than once. The reconnect may be 
because of a gap the listener does not know about because of the buffer, 
or store o audio waiting to be played.

On ADSL I limit this number to 5 and on Fibre I limit this to 10. Your 
ISP will choke the upload bandwidth especially mp3. I use AAC+ which has 
a smaller data size for the same quality, it's also not on the choke list.

If you plan on having more listeners than 5 or so then you need a 
Streaming Service who may take your stream and feed it to 100,200 or 
some larger number of listeners for $xx.95 a month. Most of these are 
mp3 only.

hope this helps

regards

Robert


On 26/03/20 2:24 pm, webmaster at berean-biblechurch.org wrote:
>
> I can't make sense of the connection stats on the admin page. We have 
> one source and one mountpoint.
>
> What is the difference between /client_connections/ and /clients/ and 
> /connection/s?? How can they be so different in value?? Same questions 
> for /listener_connections/ and /listeners/?? The connections values 
> seem high for only 5 listeners and one admin.
>
> Here is a snapshot of the admin page a few minutes after the server 
> was started and mountpoint was made available:
>
> ??????????? client_connections
> ??????????? 18
>
> ??????????? clients
> ??????????? 7
>
> ??????????? connections
> ??????????? 24
>
> ??????????? file_connections
> ??????????? 0
>
> ??????????? listener_connections
> ??????????? 17
>
> ??????????? listeners
> ??????????? 5
>
> ??????????? source_client_connections
> ??????????? 1
>
> ??????????? source_relay_connections
> ??????????? 0
>
> ??????????? source_total_connections
> ??????????? 1
>
> ??????????? sources
> ??????????? 1
>
> ??????????? stats
> ??????????? 0
>
> ??????????? stats_connections
> ??????????? 0
>
> ???? Mountpoint /live.mp3
> ????????????? listener_peak
> ????????????? 6
>
> ????????????? listeners
> ????????????? 5
>
> ????????????? max_listeners
> ????????????? unlimited
>
> After more people started to connect, the admin #s got even more whacky.
>
> Then, I have the max clients set to 25, yet the mountpoint says 
> 'unlimited' listeners.? Why the difference here?? Aren't listeners 
> also clients?
>
> <limits>
> ? <clients>25</clients>
> ? <sources>1</sources>
>
>
> Thanks,
> Justin
>
>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast

-- 
Communication Consultants 2020 Limited
64 Warner Park Avenue
Laingholm
Auckland 0604
New Zealand

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200326/e4698a15/attachment.htm>

From chiapas at aktivix.org  Thu Mar 26 11:16:54 2020
From: chiapas at aktivix.org (Chip)
Date: Thu, 26 Mar 2020 11:16:54 +0000
Subject: [Icecast] Blocking IP addresses on a per mountpoint level
Message-ID: <CAKCymP2ntYXmQpg2iYhU2Y3r2Xvd7Ja+vzF9yPxoEAhoufqzoA@mail.gmail.com>

Hi

Several questions below:

a) is it possible to block IP addresses on a per mountpoint level e.g. my
user with /mountpointA.ogg does not mind being hammered by connections from
93.184.216.34 [example.com] but my user with /mountpointB.ogg wants to
block that IP address.

b) is it possible to geoblock ranges of IP addresses and whole countries on
a per mountpoint basis?

c) what options do people use for geoblocking? I'm on a VPS so ipset is
currently not an option.

Many thanks in advance

Chip Scooter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200326/03e1f93f/attachment.htm>

From marius at flage.org  Thu Mar 26 11:24:09 2020
From: marius at flage.org (Marius Flage)
Date: Thu, 26 Mar 2020 12:24:09 +0100
Subject: [Icecast] Blocking IP addresses on a per mountpoint level
In-Reply-To: <CAKCymP2ntYXmQpg2iYhU2Y3r2Xvd7Ja+vzF9yPxoEAhoufqzoA@mail.gmail.com>
References: <CAKCymP2ntYXmQpg2iYhU2Y3r2Xvd7Ja+vzF9yPxoEAhoufqzoA@mail.gmail.com>
Message-ID: <b9d53559-3b45-345a-ce36-1676b865e0b9@flage.org>

I believe the easiest is just to do this using iptables ('iptables -A
INPUT -s 93.184.216.34 -j DROP'). There's also an geoip module available
for iptables.

--
Marius

On 26.03.2020 12:16, Chip wrote:
> Hi
>
> Several questions below:
>
> a) is it possible to block IP addresses on a per mountpoint level e.g.
> my user with /mountpointA.ogg does not mind being hammered by
> connections from 93.184.216.34 [example.com <http://example.com>] but
> my user with /mountpointB.ogg wants to block that IP address.
>
> b) is it possible to geoblock ranges of IP addresses and whole
> countries on a per mountpoint basis?
>
> c) what options do people use for geoblocking? I'm on a VPS so ipset
> is currently not an option.
>
> Many thanks in advance
>
> Chip Scooter
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200326/7e4f1654/attachment.htm>

From chiapas at aktivix.org  Thu Mar 26 12:49:28 2020
From: chiapas at aktivix.org (Chip)
Date: Thu, 26 Mar 2020 12:49:28 +0000
Subject: [Icecast] Blocking IP addresses on a per mountpoint level
In-Reply-To: <b9d53559-3b45-345a-ce36-1676b865e0b9@flage.org>
References: <CAKCymP2ntYXmQpg2iYhU2Y3r2Xvd7Ja+vzF9yPxoEAhoufqzoA@mail.gmail.com>
 <b9d53559-3b45-345a-ce36-1676b865e0b9@flage.org>
Message-ID: <CAKCymP0NAKPUm4CUKGEb+NLfu=XKK0JT5pUHvKKLJu9DJgd9ow@mail.gmail.com>

Thanks.

Indeed - but is it it possible to block IP addresses on a per mountpoint
level? For example, my user with /mountpointA.ogg does not mind being
hammered by connections from 93.184.216.34 [example.com] but my user with
/mountpointB.ogg wants to block that IP address.

Using iptables I've blocked connections, at a server level, from example.com
for my User B but my User A doesn't mind their connection being probed once
per minute 24/7/365 by a badly-configured player from that IP address.

Thank you

Chip Scooter

On Thu, 26 Mar 2020 at 11:30, Marius Flage <marius at flage.org> wrote:

> I believe the easiest is just to do this using iptables ('iptables -A
> INPUT -s 93.184.216.34 -j DROP'). There's also an geoip module available
> for iptables.
>
> --
> Marius
> On 26.03.2020 12:16, Chip wrote:
>
> Hi
>
> Several questions below:
>
> a) is it possible to block IP addresses on a per mountpoint level e.g. my
> user with /mountpointA.ogg does not mind being hammered by connections from
> 93.184.216.34 [example.com] but my user with /mountpointB.ogg wants to
> block that IP address.
>
> b) is it possible to geoblock ranges of IP addresses and whole countries
> on a per mountpoint basis?
>
> c) what options do people use for geoblocking? I'm on a VPS so ipset is
> currently not an option.
>
> Many thanks in advance
>
> Chip Scooter
>
> _______________________________________________
> Icecast mailing listIcecast at xiph.orghttp://lists.xiph.org/mailman/listinfo/icecast
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200326/63d40720/attachment.htm>

From marius at flage.org  Thu Mar 26 13:00:44 2020
From: marius at flage.org (Marius Flage)
Date: Thu, 26 Mar 2020 14:00:44 +0100
Subject: [Icecast] Blocking IP addresses on a per mountpoint level
In-Reply-To: <CAKCymP0NAKPUm4CUKGEb+NLfu=XKK0JT5pUHvKKLJu9DJgd9ow@mail.gmail.com>
References: <CAKCymP2ntYXmQpg2iYhU2Y3r2Xvd7Ja+vzF9yPxoEAhoufqzoA@mail.gmail.com>
 <b9d53559-3b45-345a-ce36-1676b865e0b9@flage.org>
 <CAKCymP0NAKPUm4CUKGEb+NLfu=XKK0JT5pUHvKKLJu9DJgd9ow@mail.gmail.com>
Message-ID: <b4fcee40-3190-4a5a-6c94-453801396dd0@flage.org>

Ah,

I must have overlooked that requirement in my first reply. I don't think
you can do it natively in Icecast, and doing this in the kernel will be
too low level and too wide a block, so I guess a web application
firewall or a reverse proxy is the way to go. Maybe setting up HAproxy
or similar could solve this?

--
Marius

On 26.03.2020 13:49, Chip wrote:
> Thanks.
>
> Indeed - but is it it possible to block IP addresses on a per
> mountpoint level? For example, my user with /mountpointA.ogg does not
> mind being hammered by connections from 93.184.216.34 [example.com
> <http://example.com>] but my user with /mountpointB.ogg wants to block
> that IP address.
>
> Using iptables I've blocked connections, at a server level, from
> example.com <http://example.com> for my User B but my User A doesn't
> mind their connection being probed once per minute 24/7/365 by a
> badly-configured player from that IP address.
>
> Thank you
>
> Chip Scooter
>
> On Thu, 26 Mar 2020 at 11:30, Marius Flage <marius at flage.org
> <mailto:marius at flage.org>> wrote:
>
>     I believe the easiest is just to do this using iptables ('iptables
>     -A INPUT -s 93.184.216.34 -j DROP'). There's also an geoip module
>     available for iptables.
>
>     --
>     Marius
>
>     On 26.03.2020 12:16, Chip wrote:
>>     Hi
>>
>>     Several questions below:
>>
>>     a) is it possible to block IP addresses on a per mountpoint level
>>     e.g. my user with /mountpointA.ogg does not mind being hammered
>>     by connections from 93.184.216.34 [example.com
>>     <http://example.com>] but my user with /mountpointB.ogg wants to
>>     block that IP address.
>>
>>     b) is it possible to geoblock ranges of IP addresses and whole
>>     countries on a per mountpoint basis?
>>
>>     c) what options do people use for geoblocking? I'm on a VPS so
>>     ipset is currently not an option.
>>
>>     Many thanks in advance
>>
>>     Chip Scooter
>>
>>     _______________________________________________
>>     Icecast mailing list
>>     Icecast at xiph.org <mailto:Icecast at xiph.org>
>>     http://lists.xiph.org/mailman/listinfo/icecast
>     _______________________________________________
>     Icecast mailing list
>     Icecast at xiph.org <mailto:Icecast at xiph.org>
>     http://lists.xiph.org/mailman/listinfo/icecast
>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200326/def1bdde/attachment.htm>

From jvoosten at bankai.nl  Thu Mar 26 13:07:44 2020
From: jvoosten at bankai.nl (Jeroen van Oosten)
Date: Thu, 26 Mar 2020 14:07:44 +0100
Subject: [Icecast] Blocking IP addresses on a per mountpoint level
In-Reply-To: <CAKCymP0NAKPUm4CUKGEb+NLfu=XKK0JT5pUHvKKLJu9DJgd9ow@mail.gmail.com>
References: <CAKCymP2ntYXmQpg2iYhU2Y3r2Xvd7Ja+vzF9yPxoEAhoufqzoA@mail.gmail.com>
 <b9d53559-3b45-345a-ce36-1676b865e0b9@flage.org>
 <CAKCymP0NAKPUm4CUKGEb+NLfu=XKK0JT5pUHvKKLJu9DJgd9ow@mail.gmail.com>
Message-ID: <9cc383b2-180d-9eda-fca9-09a6b40a1972@bankai.nl>

On 26/03/2020 13:49, Chip wrote:
> Thanks.
>
> Indeed - but is it it possible to block IP addresses on a per
> mountpoint level? For example, my user with /mountpointA.ogg does not
> mind being hammered by connections from 93.184.216.34 [example.com
> <http://example.com>] but my user with /mountpointB.ogg wants to block
> that IP address.


If the mountpoints are at different ports you can specify that in
iptables as well:

iptables -A INPUT -s 93.185.216.34 --dport xxx -j DROP

That will only block connections from that IP address to the given
destionation port.

Regards,

?- Jeroen



-- 
Bankai Software bv
Jeroen van Oosten
Telefoon: 088-2344999
E-mail: jvoosten at bankai.nl
KvK inschrijving: 67066267
PGP key: B2308F8E

"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." --Red Adair

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200326/97889386/attachment.htm>

From chiapas at aktivix.org  Thu Mar 26 13:17:37 2020
From: chiapas at aktivix.org (Chip)
Date: Thu, 26 Mar 2020 13:17:37 +0000
Subject: [Icecast] Blocking IP addresses on a per mountpoint level
In-Reply-To: <b4fcee40-3190-4a5a-6c94-453801396dd0@flage.org>
References: <CAKCymP2ntYXmQpg2iYhU2Y3r2Xvd7Ja+vzF9yPxoEAhoufqzoA@mail.gmail.com>
 <b9d53559-3b45-345a-ce36-1676b865e0b9@flage.org>
 <CAKCymP0NAKPUm4CUKGEb+NLfu=XKK0JT5pUHvKKLJu9DJgd9ow@mail.gmail.com>
 <b4fcee40-3190-4a5a-6c94-453801396dd0@flage.org>
Message-ID: <CAKCymP36d8JODptAp0cKktgvDW_jw-enKWqcswo1wvPVQ62UDw@mail.gmail.com>

Thanks.

Maybe something like this might do it:

   - https://mediarealm.com.au/articles/icecast-stream-geoblocking/

I should have searched more before asking the question(s) :o)

Cheers

Chip Scooter


On Thu, 26 Mar 2020 at 13:00, Marius Flage <marius at flage.org> wrote:

> Ah,
>
> I must have overlooked that requirement in my first reply. I don't think
> you can do it natively in Icecast, and doing this in the kernel will be too
> low level and too wide a block, so I guess a web application firewall or a
> reverse proxy is the way to go. Maybe setting up HAproxy or similar could
> solve this?
>
> --
> Marius
> On 26.03.2020 13:49, Chip wrote:
>
> Thanks.
>
> Indeed - but is it it possible to block IP addresses on a per mountpoint
> level? For example, my user with /mountpointA.ogg does not mind being
> hammered by connections from 93.184.216.34 [example.com] but my user with
> /mountpointB.ogg wants to block that IP address.
>
> Using iptables I've blocked connections, at a server level, from
> example.com for my User B but my User A doesn't mind their connection
> being probed once per minute 24/7/365 by a badly-configured player from
> that IP address.
>
> Thank you
>
> Chip Scooter
>
> On Thu, 26 Mar 2020 at 11:30, Marius Flage <marius at flage.org> wrote:
>
>> I believe the easiest is just to do this using iptables ('iptables -A
>> INPUT -s 93.184.216.34 -j DROP'). There's also an geoip module available
>> for iptables.
>>
>> --
>> Marius
>> On 26.03.2020 12:16, Chip wrote:
>>
>> Hi
>>
>> Several questions below:
>>
>> a) is it possible to block IP addresses on a per mountpoint level e.g. my
>> user with /mountpointA.ogg does not mind being hammered by connections from
>> 93.184.216.34 [example.com] but my user with /mountpointB.ogg wants to
>> block that IP address.
>>
>> b) is it possible to geoblock ranges of IP addresses and whole countries
>> on a per mountpoint basis?
>>
>> c) what options do people use for geoblocking? I'm on a VPS so ipset is
>> currently not an option.
>>
>> Many thanks in advance
>>
>> Chip Scooter
>>
>> _______________________________________________
>> Icecast mailing listIcecast at xiph.orghttp://lists.xiph.org/mailman/listinfo/icecast
>>
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org
>> http://lists.xiph.org/mailman/listinfo/icecast
>>
>
> _______________________________________________
> Icecast mailing listIcecast at xiph.orghttp://lists.xiph.org/mailman/listinfo/icecast
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200326/869ad5ea/attachment.htm>

From chiapas at aktivix.org  Thu Mar 26 13:18:40 2020
From: chiapas at aktivix.org (Chip)
Date: Thu, 26 Mar 2020 13:18:40 +0000
Subject: [Icecast] Blocking IP addresses on a per mountpoint level
In-Reply-To: <9cc383b2-180d-9eda-fca9-09a6b40a1972@bankai.nl>
References: <CAKCymP2ntYXmQpg2iYhU2Y3r2Xvd7Ja+vzF9yPxoEAhoufqzoA@mail.gmail.com>
 <b9d53559-3b45-345a-ce36-1676b865e0b9@flage.org>
 <CAKCymP0NAKPUm4CUKGEb+NLfu=XKK0JT5pUHvKKLJu9DJgd9ow@mail.gmail.com>
 <9cc383b2-180d-9eda-fca9-09a6b40a1972@bankai.nl>
Message-ID: <CAKCymP241cAf+MWUZJtL6xzJBz3V_mVP0ka1ik=xfopUJQ_otQ@mail.gmail.com>

Thanks - very cool.

They might indeed be on different ports. I'll need to investigate.

Cheers

Chip Scooter

On Thu, 26 Mar 2020 at 13:16, Jeroen van Oosten <jvoosten at bankai.nl> wrote:

> On 26/03/2020 13:49, Chip wrote:
>
> Thanks.
>
> Indeed - but is it it possible to block IP addresses on a per mountpoint
> level? For example, my user with /mountpointA.ogg does not mind being
> hammered by connections from 93.184.216.34 [example.com] but my user with
> /mountpointB.ogg wants to block that IP address.
>
>
> If the mountpoints are at different ports you can specify that in iptables
> as well:
>
> iptables -A INPUT -s 93.185.216.34 --dport xxx -j DROP
>
> That will only block connections from that IP address to the given
> destionation port.
>
> Regards,
>
>  - Jeroen
>
>
> --
> Bankai Software bv
> Jeroen van Oosten
> Telefoon: 088-2344999
> E-mail: jvoosten at bankai.nl
> KvK inschrijving: 67066267
> PGP key: B2308F8E
>
> "If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." --Red Adair
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200326/b0912157/attachment.htm>

From webmaster at berean-biblechurch.org  Fri Mar 27 01:55:17 2020
From: webmaster at berean-biblechurch.org (webmaster at berean-biblechurch.org)
Date: Thu, 26 Mar 2020 20:55:17 -0500
Subject: [Icecast] making sense of the stats
In-Reply-To: <db63ddfe-25fe-61eb-8304-dbbb910204d2@gmail.com>
References: <67572a3fa5f738b576eb80b378a3c7b6@berean-biblechurch.org>
 <db63ddfe-25fe-61eb-8304-dbbb910204d2@gmail.com>
Message-ID: <cc8d63dba543b0551979300101b3036e@berean-biblechurch.org>

Hi, Robert.  I appreciate the explanation.  Indeed, the terminology is
not consistent or intuitive. 

So by your "4 services" you mean _sources_? 

If clients are source connections (one and the same?), then how do we
reconcile limits for both clients and sources?  Is it like saying, 'for
all of the X sources, they can have a total of Y connections'? 

How can I set limits on the number of _listeners_?  And this limit would
be different than a limit on the number of _listener connections_"? 

On 2020-03-26 00:18, Robert Jeffares wrote:

> Hi Justin, 
> 
> _  AREN'T LISTENERS ALSO CLIENTS?_ 
> 
> No. 
> 
> Icecast xml is a bit daunting. 
> 
> There are two kinds of connections. 
> 
> Listener and Client 
> 
> Client:... 
> 
> Connections from your source which may be darkice, BUTT, or some other encoder. 
> 
> You actually need plenty of these. I set mine to 20 when I have 4 services. 
> 
> One client may have several connections. I assume there is some handshaking and there may be metadata as well. 
> 
> Listener:... 
> 
> Connections from anyone using the mount address which may be a listener or a relay. 
> 
> The same listener can connect more than once. The reconnect may be because of a gap the listener does not know about because of the buffer, or store o audio waiting to be played. 
> 
> On ADSL I limit this number to 5 and on Fibre I limit this to 10. Your ISP will choke the upload bandwidth especially mp3. I use AAC+ which has a smaller data size for the same quality, it's also not on the choke list. 
> 
> If you plan on having more listeners than 5 or so then you need a Streaming Service who may take your stream and feed it to 100,200 or some larger number of listeners for $xx.95 a month. Most of these are mp3 only. 
> 
> hope this helps 
> 
> regards 
> 
> Robert 
> 
> On 26/03/20 2:24 pm, webmaster at berean-biblechurch.org wrote: 
> 
>> I can't make sense of the connection stats on the admin page.  We have one source and one mountpoint. 
>> 
>> What is the difference between _client_connections_ and _clients_ and _connection_s?  How can they be so different in value?  Same questions for _listener_connections_ and _listeners_?  The connections values seem high for only 5 listeners and one admin. 
>> 
>> Here is a snapshot of the admin page a few minutes after the server was started and mountpoint was made available: 
>> 
>> client_connections
>> 18
>> 
>> clients
>> 7
>> 
>> connections
>> 24
>> 
>> file_connections
>> 0
>> 
>> listener_connections
>> 17
>> 
>> listeners
>> 5
>> 
>> source_client_connections
>> 1
>> 
>> source_relay_connections
>> 0
>> 
>> source_total_connections
>> 1
>> 
>> sources
>> 1
>> 
>> stats
>> 0
>> 
>> stats_connections
>> 0
>> 
>> Mountpoint /live.mp3
>> listener_peak
>> 6
>> 
>> listeners
>> 5
>> 
>> max_listeners
>> unlimited 
>> 
>> After more people started to connect, the admin #s got even more whacky. 
>> 
>> Then, I have the max clients set to 25, yet the mountpoint says 'unlimited' listeners.  Why the difference here?  Aren't listeners also clients? 
>> 
>> <limits>
>> <clients>25</clients>
>> <sources>1</sources> 
>> 
>> Thanks,
>> Justin 
>> 
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org
>> http://lists.xiph.org/mailman/listinfo/icecast
> 
> -- 
> Communication Consultants 2020 Limited
> 64 Warner Park Avenue
> Laingholm
> Auckland 0604
> New Zealand
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200326/3511b6d6/attachment.htm>

From railgun.michael at gmail.com  Fri Mar 27 06:50:07 2020
From: railgun.michael at gmail.com (Railgun)
Date: Fri, 27 Mar 2020 07:50:07 +0100
Subject: [Icecast] making sense of the stats
In-Reply-To: <cc8d63dba543b0551979300101b3036e@berean-biblechurch.org>
References: <67572a3fa5f738b576eb80b378a3c7b6@berean-biblechurch.org>
 <db63ddfe-25fe-61eb-8304-dbbb910204d2@gmail.com>
 <cc8d63dba543b0551979300101b3036e@berean-biblechurch.org>
Message-ID: <CAOUVwuu=rWdAO_2_iK5=VeqWUMZUoC1DjVPCa5jTAxAMiG+mAQ@mail.gmail.com>

You can der listener Limit per mountpoint If you define the mountpoint at
config.

<webmaster at berean-biblechurch.org> schrieb am Fr., 27. M?rz 2020, 03:18:

> Hi, Robert.  I appreciate the explanation.  Indeed, the terminology is not
> consistent or intuitive.
>
> So by your "4 services" you mean *sources*?
>
> If clients are source connections (one and the same?), then how do we
> reconcile limits for both clients and sources?  Is it like saying, 'for all
> of the X sources, they can have a total of Y connections'?
>
> How can I set limits on the number of *listeners*?  And this limit would
> be different than a limit on the number of *listener connections*"?
>
>
> On 2020-03-26 00:18, Robert Jeffares wrote:
>
> Hi Justin,
>
> *  Aren't listeners also clients?*
>
> No.
>
> Icecast xml is a bit daunting.
>
> There are two kinds of connections.
>
> Listener and Client
>
> Client:...
>
> Connections from your source which may be darkice, BUTT, or some other
> encoder.
>
> You actually need plenty of these. I set mine to 20 when I have 4 services.
>
> One client may have several connections. I assume there is some
> handshaking and there may be metadata as well.
>
> Listener:...
>
> Connections from anyone using the mount address which may be a listener or
> a relay.
>
> The same listener can connect more than once. The reconnect may be because
> of a gap the listener does not know about because of the buffer, or store o
> audio waiting to be played.
>
> On ADSL I limit this number to 5 and on Fibre I limit this to 10. Your ISP
> will choke the upload bandwidth especially mp3. I use AAC+ which has a
> smaller data size for the same quality, it's also not on the choke list.
>
> If you plan on having more listeners than 5 or so then you need a
> Streaming Service who may take your stream and feed it to 100,200 or some
> larger number of listeners for $xx.95 a month. Most of these are mp3 only.
>
> hope this helps
>
> regards
>
> Robert
>
>
> On 26/03/20 2:24 pm, webmaster at berean-biblechurch.org wrote:
>
> I can't make sense of the connection stats on the admin page.  We have one
> source and one mountpoint.
>
> What is the difference between *client_connections* and *clients* and
> *connection*s?  How can they be so different in value?  Same questions
> for *listener_connections* and *listeners*?  The connections values seem
> high for only 5 listeners and one admin.
>
> Here is a snapshot of the admin page a few minutes after the server was
> started and mountpoint was made available:
>
>             client_connections
>             18
>
>             clients
>             7
>
>             connections
>             24
>
>             file_connections
>             0
>
>             listener_connections
>             17
>
>             listeners
>             5
>
>             source_client_connections
>             1
>
>             source_relay_connections
>             0
>
>             source_total_connections
>             1
>
>             sources
>             1
>
>             stats
>             0
>
>             stats_connections
>             0
>
>      Mountpoint /live.mp3
>               listener_peak
>               6
>
>               listeners
>               5
>
>               max_listeners
>               unlimited
>
> After more people started to connect, the admin #s got even more whacky.
>
> Then, I have the max clients set to 25, yet the mountpoint says
> 'unlimited' listeners.  Why the difference here?  Aren't listeners also
> clients?
>
> <limits>
>   <clients>25</clients>
>   <sources>1</sources>
>
>
> Thanks,
> Justin
>
>
>
> _______________________________________________
> Icecast mailing listIcecast at xiph.orghttp://lists.xiph.org/mailman/listinfo/icecast
>
> --
> Communication Consultants 2020 Limited
> 64 Warner Park Avenue
> Laingholm
> Auckland 0604
> New Zealand
>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200327/fea68e4d/attachment.htm>

From faribbeiro at gmail.com  Fri Mar 27 10:18:45 2020
From: faribbeiro at gmail.com (=?UTF-8?B?RmzDoXZpbyBBbnTDtG5pbyBSaWJlaXJv?=)
Date: Fri, 27 Mar 2020 07:18:45 -0300
Subject: [Icecast] Ref. Difficulties with statistical data
Message-ID: <CAEFQ5fnJ8ZSE0zwZk_F6MFNP=w=Z330LMG=6BBSzgcQCR53u7g@mail.gmail.com>

Hi,

I'm Fl?vio (Acesita FM - Brazil).

We are having difficulties in obtaining statistical data from our broadcast
and our radio is also not found on the portal http://dir.xiph.org/.
We ask that you help us with any solution to these problems. Just consider
that we are inexperienced on this platform.

We thank you immensely.

greetings
Fl?vio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200327/3b92427c/attachment.htm>

From jeffares.robert at gmail.com  Fri Mar 27 17:34:10 2020
From: jeffares.robert at gmail.com (Robert Jeffares)
Date: Sat, 28 Mar 2020 06:34:10 +1300
Subject: [Icecast] making sense of the stats
In-Reply-To: <cc8d63dba543b0551979300101b3036e@berean-biblechurch.org>
References: <67572a3fa5f738b576eb80b378a3c7b6@berean-biblechurch.org>
 <db63ddfe-25fe-61eb-8304-dbbb910204d2@gmail.com>
 <cc8d63dba543b0551979300101b3036e@berean-biblechurch.org>
Message-ID: <fff8dcff-7fdf-3b75-4477-c151c7d38a76@gmail.com>

Justin...

On 27/03/20 2:55 pm, webmaster at berean-biblechurch.org wrote:
>
> Hi, Robert.? I appreciate the explanation.? Indeed, the terminology is 
> not consistent or intuitive.
>
> So by your "4 services" you mean /sources/?
>
I mean 4 separate streams, in my case AAC+ for external transmitter 
sites, 320mb/s mp3 [for logger], 256 kb/s for some streaming service, 56 
kb/s mp3 for smartphones.

Yes they would be sources. In my case 4 varieties of the same programme.

I also use the same Icecast for Outside Broadcast [Remote] The outside 
user mounts on port 8000 using BUTT.


> If clients are source connections (one and the same?), then how do we 
> reconcile limits for both clients and sources?? Is it like saying, 
> 'for all of the X sources, they can have a total of Y connections'?
>
By trial and error I figured out that each stream takes up more then one 
connection. I configure 5:1. It works.
>
> How can I set limits on the number of /listeners/?? And this limit 
> would be different than a limit on the number of /listener connections/"?
>
I think one is an accumulated total and the other is the number of current.

Max Listeners needs to be set so your broadband is not taken out by 
overload.

ISP's choke upload unless you negotiate with them. We just went 100:100 
at one site but most of the others are like 60:30 and some a lot less 
than that.

Here is a report from an ADSL site. That upload manages 1 listener which 
is an Icecast relay on fibre delivering the programme to 6 listeners.

Download: 15.91 Mbit/s
Testing upload speed..................................................
Upload: 0.85 Mbit/s

>
> On 2020-03-26 00:18, Robert Jeffares wrote:
>
>> Hi Justin,
>>
>> /*? Aren't listeners also clients?*/
>>
>> No.
>>
>> Icecast xml is a bit daunting.
>>
>> There are two kinds of connections.
>>
>> Listener and Client
>>
>> Client:...
>>
>> Connections from your source which may be darkice, BUTT, or some 
>> other encoder.
>>
>> You actually need plenty of these. I set mine to 20 when I have 4 
>> services.
>>
>> One client may have several connections. I assume there is some 
>> handshaking and there may be metadata as well.
>>
>> Listener:...
>>
>> Connections from anyone using the mount address which may be a 
>> listener or a relay.
>>
>> The same listener can connect more than once. The reconnect may be 
>> because of a gap the listener does not know about because of the 
>> buffer, or store o audio waiting to be played.
>>
>> On ADSL I limit this number to 5 and on Fibre I limit this to 10. 
>> Your ISP will choke the upload bandwidth especially mp3. I use AAC+ 
>> which has a smaller data size for the same quality, it's also not on 
>> the choke list.
>>
>> If you plan on having more listeners than 5 or so then you need a 
>> Streaming Service who may take your stream and feed it to 100,200 or 
>> some larger number of listeners for $xx.95 a month. Most of these are 
>> mp3 only.
>>
>> hope this helps
>>
>> regards
>>
>> Robert
>>
>>
>> On 26/03/20 2:24 pm, webmaster at berean-biblechurch.org wrote:
>>>
>>> I can't make sense of the connection stats on the admin page.? We 
>>> have one source and one mountpoint.
>>>
>>> What is the difference between /client_connections/ and /clients/ 
>>> and /connection/s?? How can they be so different in value?? Same 
>>> questions for /listener_connections/ and /listeners/?? The 
>>> connections values seem high for only 5 listeners and one admin.
>>>
>>> Here is a snapshot of the admin page a few minutes after the server 
>>> was started and mountpoint was made available:
>>>
>>> ??????????? client_connections
>>> ??????????? 18
>>>
>>> ??????????? clients
>>> ??????????? 7
>>>
>>> ??????????? connections
>>> ??????????? 24
>>>
>>> ??????????? file_connections
>>> ??????????? 0
>>>
>>> ??????????? listener_connections
>>> ??????????? 17
>>>
>>> ??????????? listeners
>>> ??????????? 5
>>>
>>> ??????????? source_client_connections
>>> ??????????? 1
>>>
>>> ??????????? source_relay_connections
>>> ??????????? 0
>>>
>>> ??????????? source_total_connections
>>> ??????????? 1
>>>
>>> ??????????? sources
>>> ??????????? 1
>>>
>>> ??????????? stats
>>> ??????????? 0
>>>
>>> ??????????? stats_connections
>>> ??????????? 0
>>>
>>> ???? Mountpoint /live.mp3
>>> ????????????? listener_peak
>>> ????????????? 6
>>>
>>> ????????????? listeners
>>> ????????????? 5
>>>
>>> ????????????? max_listeners
>>> ????????????? unlimited
>>>
>>> After more people started to connect, the admin #s got even more whacky.
>>>
>>> Then, I have the max clients set to 25, yet the mountpoint says 
>>> 'unlimited' listeners.? Why the difference here? Aren't listeners 
>>> also clients?
>>>
>>> <limits>
>>> ? <clients>25</clients>
>>> ? <sources>1</sources>
>>>
>>>
>>> Thanks,
>>> Justin
>>>
>>>
>>>
>>> _______________________________________________
>>> Icecast mailing list
>>> Icecast at xiph.org
>>> http://lists.xiph.org/mailman/listinfo/icecast
>> -- 
>> Communication Consultants 2020 Limited
>> 64 Warner Park Avenue
>> Laingholm
>> Auckland 0604
>> New Zealand
>>
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org <mailto:Icecast at xiph.org>
>> http://lists.xiph.org/mailman/listinfo/icecast

-- 
Communication Consultants 2020 Limited
64 Warner Park Avenue
Laingholm
Auckland 0604
New Zealand

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200328/27c521e7/attachment.htm>

From james at switchbladeuk.com  Sat Mar 28 09:33:21 2020
From: james at switchbladeuk.com (James Turner)
Date: Sat, 28 Mar 2020 09:33:21 -0000
Subject: [Icecast] Icecast SSL endpoint timeout issue
In-Reply-To: <1581884129.2179.297.camel@lion.leolix.org>
References: <003801d5e4af$7153e170$53fba450$@switchbladeuk.com>
 <1581884129.2179.297.camel@lion.leolix.org>
Message-ID: <027a01d604e3$ec41f080$c4c5d180$@switchbladeuk.com>

Hi team,

Have you folks made any progress with the below by chance?

Kind regards,

James

-----Original Message-----
From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Philipp Schafft
Sent: 16 February 2020 20:15
To: Icecast streaming server user discussions <icecast at xiph.org>
Subject: Re: [Icecast] Icecast SSL endpoint timeout issue


Good evening,

first of all thank you for the very good report. :)


On Sun, 2020-02-16 at 09:57 +0000, James Turner wrote:
> Hi team,
> 
> Please accent my apologies if this is NOT the place/distro list to be 
> raising this. I had major dramas with the standard forum - 
> registration and decided this may be a better route.

This is the *perfect* place beside opening a ticket on gitlab. :)


> My current instance icecast server has been built with  --with-curl 
> --with-openssl  options as outlined within this post:
> https://weekly-geekly.github.io/articles/350236/index.html and the 
> build version is 2.4.99.2

I only had a quick look at that link. I think it is better than most but it has some oddities. I would generally recommend to have a look at:
https://wiki.xiph.org/Icecast_Server/Installing_latest_version_(official_Xiph_repositories)

If you *really* want to build your own Icecast:
https://wiki.xiph.org/Icecast_Server/Git_workflow

However those two are "just" the install part, not the setup part.


> I'm using a valid certificate from letsencrypt on a Ubuntu 18 server 
> hosted by AWS. Icecast recognizes this without issue.

I wouldn't recommend AWS with Icecast as several of my clients had problems with their border gateways. However if it works for you that sounds fine.


> I'm having issues disconnecting  my source client  from Icecast when 
> the connections is via SSL. Non SSL source clients work as intended, 
> connecting and disconnecting without issues and Icecast shuts down the 
> mount points after client drop-outs as intended. See the logs outlined below for details.
> Using an SSL connection and once the client connection drops (for 
> whatever
> reason) Icecast does not recognize this and keeps the mount point 
> active forever - even when there's no data being sent by the client.  
> On a reconnect try  the client gets a 'mount point already in use' 
> message. To get over this state I either have to restart the Icecast 
> service OR manually kill the source from the admin interface. Once 
> done. I can reconnect again.repeating the process
> 
> Frustratingly, this (SSL) works (source>icecast>listener) - just about 
> - but I'd dearly like to understand the issue with the ssl connection 
> and mountpoint not being released. I would expect a source timeout to 
> occur, as defined in the Icecast config file thus releasing the mount 
> point. However, not to be.
> [...]

You are totally right here. In fact it's a bug we currently hunt. Had a debugging session yesterday about it. We are currently considering what the best route is to fix this.

What would help me is if you could provide your exact OpenSSL version:
$ openssl version
$ dpkg -l libssl-dev

Thank you very much. I expect that we fix this within the next week.

With best regards,

--
Philipp.
 (Rah of PH2)
_______________________________________________
Icecast mailing list
Icecast at xiph.org
http://lists.xiph.org/mailman/listinfo/icecast



From jayaubs89 at gmail.com  Sat Mar 28 19:36:09 2020
From: jayaubs89 at gmail.com (Jay George)
Date: Sat, 28 Mar 2020 19:36:09 +0000
Subject: [Icecast] Icecast SSL endpoint timeout issue
In-Reply-To: <003801d5e4af$7153e170$53fba450$@switchbladeuk.com>
References: <003801d5e4af$7153e170$53fba450$@switchbladeuk.com>
Message-ID: <CAJQJMxooQ_BS54+FKrgAnSvFyw3aUAz1b0Zf+xQqADzGcPbLMg@mail.gmail.com>

does anyone know how i can setup my own icecast server?


On Sun, Feb 16, 2020 at 9:57 AM James Turner <james at switchbladeuk.com>
wrote:

> Hi team,
>
> Please accent my apologies if this is NOT the place/distro list to be
> raising this. I had major dramas with the standard forum - registration and
> decided this may be a better route.
>
> My current instance icecast server has been built with  --with-curl
> --with-openssl  options as outlined within this post:
> https://weekly-geekly.github.io/articles/350236/index.html and the build
> version is 2.4.99.2
>
> I'm using a valid certificate from letsencrypt on a Ubuntu 18 server hosted
> by AWS. Icecast recognizes this without issue.
>
> I'm having issues disconnecting  my source client  from Icecast when the
> connections is via SSL. Non SSL source clients work as intended, connecting
> and disconnecting without issues and Icecast shuts down the mount points
> after client drop-outs as intended. See the logs outlined below for
> details.
> Using an SSL connection and once the client connection drops (for whatever
> reason) Icecast does not recognize this and keeps the mount point active
> forever - even when there's no data being sent by the client.  On a
> reconnect try  the client gets a 'mount point already in use' message. To
> get over this state I either have to restart the Icecast service OR
> manually
> kill the source from the admin interface. Once done. I can reconnect
> again.repeating the process
>
> Frustratingly, this (SSL) works (source>icecast>listener) - just about -
> but I'd dearly like to understand the issue with the ssl connection and
> mountpoint not being released. I would expect a source timeout to occur, as
> defined in the Icecast config file thus releasing the mount point. However,
> not to be.
>
> Connecting to unencrypted Icecast port (8000)
>
> Access.log
> xx.xx.xx.xxx- - [09/Feb/2020:17:56:50 +0000] "SOURCE /acdc.ogg HTTP/1.0"
> 401
> 777 "-" "libshout/2.4.1" 0
> Error.log
> [2020-02-09  17:56:50] EROR connection/_handle_authed_client Client
> (role=anonymous, username=(null)) not allowed to use this request method on
> /acdc.ogg
> [2020-02-09  17:56:50] EROR util/util_http_select_best Input string does
> not
> parse as KVA. Selecting first option.
> [2020-02-09  17:56:50] WARN reportxml/reportxml_database_build_report No
> matching definition for "25387198-0643-4577-9139-7c4f24f59d4a"
> [2020-02-09  17:56:50] INFO connection/_handle_source_request Source
> logging
> in at mountpoint "/acdc.ogg" using "SOURCE" from xx.xx.xx.xxx as role
> legacy-global-source
> [2020-02-09  17:56:50] INFO source/source_main listener count on /acdc.ogg
> now 0
> [2020-02-09  17:56:50] INFO format-opus/initial_opus_page seen initial opus
> header
>
> Source client disconnects.
> Access.log
> xx.xx.xx.xxx- source [09/Feb/2020:17:56:57 +0000] "SOURCE /acdc.ogg
> HTTP/1.0" 200 324 "-" "libshout/2.4.1" 7
>
> Error.log
> [2020-02-09  17:53:12] INFO source/get_next_buffer End of Stream /acdc.ogg
> [2020-02-09  17:53:12] INFO source/source_shutdown Source from xx.xx.xx.xxx
> at "/acdc.ogg" exiting
>
>
> Connection by source client Using SSL (port 8444):
> Connect:
> Access.log
> xx.xx.xx.xxx- source [09/Feb/2020:18:00:25 +0000] "GET /admin/metadata
> HTTP/1.1" 200 481 "-" "Mozilla/5.0" 0
> Error.log
>
> [2020-02-09  18:00:24] INFO connection/_handle_source_request Source
> logging
> in at mountpoint "/acdc.ogg" using "SOURCE" from xx.xx.xx.xxx as role
> legacy-global-source
> [2020-02-09  18:00:24] WARN format/format_get_type Unsupported or legacy
> stream type: "audio/mpeg". Falling back to generic minimal handler for best
> effort.
> [2020-02-09  18:00:25] INFO source/source_main listener count on /acdc.ogg
> now 0
> [2020-02-09  18:00:25] INFO admin/admin_handle_request Received admin
> command metadata on mount '/acdc.ogg'
> [2020-02-09  18:00:25] INFO util/util_conv_string converting metadata from
> utf-8 to ISO8859-1
> [2020-02-09  18:00:25] INFO admin/command_metadata Metadata on mountpoint
> /acdc.ogg changed to " - "
>
> Source disconnects here.
> .       No log entries - no source timeouts.
> .       Mountpoint (here acdc.ogg) still active and visible in the admin
> interface
> .       Source client cannot reconnect - see message below:
>
>
> Action: Source client tries to reconnect (port 8000 or 8444)
>
> Access.log
> xx.xx.xx.xxx- - [09/Feb/2020:18:03:53 +0000] "SOURCE /acdc.ogg HTTP/1.0"
> 401
> 777 "-" "libshout/2.4.1" 1
> xx.xx.xx.xxx- source [09/Feb/2020:18:03:53 +0000] "SOURCE /acdc.ogg
> HTTP/1.0" 409 706 "-" "libshout/2.4.1" 0
>
> Error.log
>
> [2020-02-09  18:03:52] EROR connection/_handle_authed_client Client
> (role=anonymous, username=(null)) not allowed to use this request method on
> /acdc.ogg
> [2020-02-09  18:03:52] EROR util/util_http_select_best Input string does
> not
> parse as KVA. Selecting first option.
> [2020-02-09  18:03:52] WARN reportxml/reportxml_database_build_report No
> matching definition for "25387198-0643-4577-9139-7c4f24f59d4a"
> [2020-02-09  18:03:53] INFO connection/_handle_source_request Source
> logging
> in at mountpoint "/acdc.ogg" using "SOURCE" from xx.xx.xx.xxx as role
> legacy-global-source
> [2020-02-09  18:03:53] EROR util/util_http_select_best Input string does
> not
> parse as KVA. Selecting first option.
> [2020-02-09  18:03:53] WARN reportxml/reportxml_database_build_report No
> matching definition for "c5724467-5f85-48c7-b45a-915c3150c292"
> [2020-02-09  18:03:53] WARN connection/source_startup Mountpoint /acdc.ogg
> in use
>
>
> Any pointers very welcome.
>
> Here is the config.xml file for the server used:
>
> <icecast>
>     <!-- 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>earth</location>
>     <admin>icemaster at localhost</admin>
>
>     <!-- 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/
>    -->
>
>     <limits>
>         <clients>100</clients>
>         <sources>2</sources>
>         <queue-size>524288</queue-size>
>         <client-timeout>30</client-timeout>
>         <header-timeout>15</header-timeout>
>         <source-timeout>10</source-timeout>
>         <!-- 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  -->
>         <burst-size>65535</burst-size>
>     </limits>
>
>     <authentication>
>         <!-- Sources log in with username 'source' -->
>         <source-password>hackme57</source-password>
>         <!-- Relays log in with username 'relay' -->
>         <relay-password>hackme58</relay-password>
>
>         <!-- Admin logs in with the username given below -->
>         <admin-user>admin</admin-user>
>         <admin-password>ITJShKNE0pRg</admin-password>
>     </authentication>
>
>     <!-- 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
>     <shoutcast-mount>/live.nsv</shoutcast-mount>
>     -->
>
>     <!-- Uncomment this if you want directory listings -->
>     <!--
>     <directory>
>         <yp-url-timeout>15</yp-url-timeout>
>         <yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url>
>     </directory>
>     -->
>
>     <!-- 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!
>     -->
>     <hostname>localhost</hostname>
>
>     <!-- You may have multiple <listener> elements -->
>     <listen-socket>
>            <port>8000</port>
>            <ssl>0</ssl>
>         <!-- <bind-address>127.0.0.1</bind-address> -->
>         <!-- <shoutcast-mount>/stream</shoutcast-mount> -->
>     </listen-socket>
>     <!--
>     <listen-socket>
>         <port>8080</port>
>     </listen-socket>
>     -->
>
>     <listen-socket>
>            <port>8444</port>
>         <ssl>1</ssl>
>     </listen-socket>
>
>
>     <!-- 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.
>     -->
>     <http-headers>
>         <header name="Access-Control-Allow-Origin" value="*" />
>     </http-headers>
>
>
>     <!-- Relaying:
>          You don't need this if you only have one server.
>          Please refer to the config for a detailed explanation.
>     -->
>     <!--<master-server>127.0.0.1</master-server>-->
>     <!--<master-server-port>8001</master-server-port>-->
>     <!--<master-update-interval>120</master-update-interval>-->
>     <!--<master-password>hackme</master-password>-->
>
>     <!-- 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 -->
>     <!--<relays-on-demand>1</relays-on-demand>-->
>
>     <!--
>     <relay>
>         <server>127.0.0.1</server>
>         <port>8080</port>
>         <mount>/example.ogg</mount>
>         <local-mount>/different.ogg</local-mount>
>         <on-demand>0</on-demand>
>
>         <relay-shoutcast-metadata>0</relay-shoutcast-metadata>
>     </relay>
>     -->
>
>
>     <!-- 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">
>         <public>0</public>
>         <intro>/server-wide-intro.ogg</intro>
>         <max-listener-duration>3600</max-listener-duration>
>         <authentication type="url">
>                 <option name="mount_add"
> value="http://auth.example.org/stream_start.php"/>
>         </authentication>
>         <http-headers>
>                 <header name="foo" value="bar" />
>         </http-headers>
>     </mount>
>     -->
>
>     <!-- Normal mounts -->
>
>     <mount type="normal">
>         <mount-name>/acdc.ogg</mount-name>
>
>         <!--username>othersource</username>
>         <password>hackme_1666</password-->
>
>         <max-listeners>1</max-listeners>
>         <!--dump-file>/tmp/dump-example1.ogg</dump-file-->
>         <burst-size>65536</burst-size>
>         <!--fallback-mount>/example2.ogg</fallback-mount>
>         <fallback-override>1</fallback-override>
>         <fallback-when-full>1</fallback-when-full>
>         <intro>/example_intro.ogg</intro-->
>         <hidden>0</hidden>
>         <public>0</public>
>         <authentication type="htpasswd">
>              <option name="filename" value="/var/log/icecast2/password"/>
>                 <option name="allow_duplicate_users" value="0"/>
>         </authentication>
>         <http-headers>
>                 <header name="Access-Control-Allow-Origin"
> value="http://webplayer.example.org" />
>         </http-headers>
>         <!--on-connect>/home/icecast/bin/stream-start</on-connect>
>         <on-disconnect>/home/icecast/bin/stream-stop</on-disconnect-->
>     </mount>
>
>
>     <fileserve>1</fileserve>
>
>     <paths>
>         <!-- basedir is only used if chroot is enabled -->
>         <basedir>./</basedir>
>
>         <!-- Note that if <chroot> is turned on below, these paths must
> both
>              be relative to the new root, not the original root -->
>         <logdir>/var/log/icecast2</logdir>
>        <webroot>/usr/local/share/icecast/web</webroot>
>        <adminroot>/usr/local/share/icecast/admin</adminroot>
>         <!-- <pidfile>/usr/share/icecast/icecast.pid</pidfile> -->
>
>         <!-- 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.
>     -->
>         <ssl-certificate>/var/log/icecast2/icecast.pem</ssl-certificate>
>     </paths>
>
>     <logging>
>         <accesslog>access.log</accesslog>
>         <errorlog>error.log</errorlog>
>         <!-- <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> -->
>     </logging>
>
>     <security>
>         <chroot>0</chroot>
>
>         <changeowner>
>             <user>icecast</user>
>             <group>icecast</group>
>         </changeowner>
>
>     </security>
> </icecast><?xml version="1.0" encoding="utf-8"?>
>
>
>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200328/f71e1766/attachment.htm>

From jordan at coolmic.net  Sat Mar 28 23:29:31 2020
From: jordan at coolmic.net (Jordan Erickson)
Date: Sat, 28 Mar 2020 16:29:31 -0700
Subject: [Icecast] Icecast SSL endpoint timeout issue
In-Reply-To: <CAJQJMxooQ_BS54+FKrgAnSvFyw3aUAz1b0Zf+xQqADzGcPbLMg@mail.gmail.com>
References: <003801d5e4af$7153e170$53fba450$@switchbladeuk.com>
 <CAJQJMxooQ_BS54+FKrgAnSvFyw3aUAz1b0Zf+xQqADzGcPbLMg@mail.gmail.com>
Message-ID: <87cd2b9d-dd20-105a-b971-8b56c860f877@coolmic.net>

Hi Jay,

Check out the very well written docs:
http://icecast.org/docs/icecast-2.4.1/


Cheers,
Jordan


On 3/28/20 12:36 PM, Jay George wrote:
> does anyone know how i can setup my own icecast server??
> 
> 
> On Sun, Feb 16, 2020 at 9:57 AM James Turner <james at switchbladeuk.com
> <mailto:james at switchbladeuk.com>> wrote:
> 
>     Hi team,
> 
>     Please accent my apologies if this is NOT the place/distro list to be
>     raising this. I had major dramas with the standard forum -
>     registration and
>     decided this may be a better route.
> 
>     My current instance icecast server has been built with? --with-curl
>     --with-openssl? options as outlined within this post:
>     https://weekly-geekly.github.io/articles/350236/index.html and the build
>     version is 2.4.99.2
> 
>     I'm using a valid certificate from letsencrypt on a Ubuntu 18 server
>     hosted
>     by AWS. Icecast recognizes this without issue.
> 
>     I'm having issues disconnecting? my source client? from Icecast when the
>     connections is via SSL. Non SSL source clients work as intended,
>     connecting
>     and disconnecting without issues and Icecast shuts down the mount points
>     after client drop-outs as intended. See the logs outlined below for
>     details.
>     Using an SSL connection and once the client connection drops (for
>     whatever
>     reason) Icecast does not recognize this and keeps the mount point active
>     forever - even when there's no data being sent by the client.? On a
>     reconnect try? the client gets a 'mount point already in use'
>     message. To
>     get over this state I either have to restart the Icecast service OR
>     manually
>     kill the source from the admin interface. Once done. I can reconnect
>     again.repeating the process
> 
>     Frustratingly, this (SSL) works (source>icecast>listener) - just about -
>     but I'd dearly like to understand the issue with the ssl connection and
>     mountpoint not being released. I would expect a source timeout to
>     occur, as
>     defined in the Icecast config file thus releasing the mount point.
>     However,
>     not to be.
> 
>     Connecting to unencrypted Icecast port (8000)
> 
>     Access.log
>     xx.xx.xx.xxx- - [09/Feb/2020:17:56:50 +0000] "SOURCE /acdc.ogg
>     HTTP/1.0" 401
>     777 "-" "libshout/2.4.1" 0
>     Error.log
>     [2020-02-09? 17:56:50] EROR connection/_handle_authed_client Client
>     (role=anonymous, username=(null)) not allowed to use this request
>     method on
>     /acdc.ogg
>     [2020-02-09? 17:56:50] EROR util/util_http_select_best Input string
>     does not
>     parse as KVA. Selecting first option.
>     [2020-02-09? 17:56:50] WARN reportxml/reportxml_database_build_report No
>     matching definition for "25387198-0643-4577-9139-7c4f24f59d4a"
>     [2020-02-09? 17:56:50] INFO connection/_handle_source_request Source
>     logging
>     in at mountpoint "/acdc.ogg" using "SOURCE" from xx.xx.xx.xxx as role
>     legacy-global-source
>     [2020-02-09? 17:56:50] INFO source/source_main listener count on
>     /acdc.ogg
>     now 0
>     [2020-02-09? 17:56:50] INFO format-opus/initial_opus_page seen
>     initial opus
>     header
> 
>     Source client disconnects.
>     Access.log
>     xx.xx.xx.xxx- source [09/Feb/2020:17:56:57 +0000] "SOURCE /acdc.ogg
>     HTTP/1.0" 200 324 "-" "libshout/2.4.1" 7
> 
>     Error.log
>     [2020-02-09? 17:53:12] INFO source/get_next_buffer End of Stream
>     /acdc.ogg
>     [2020-02-09? 17:53:12] INFO source/source_shutdown Source from
>     xx.xx.xx.xxx
>     at "/acdc.ogg" exiting
> 
> 
>     Connection by source client Using SSL (port 8444):
>     Connect:
>     Access.log
>     xx.xx.xx.xxx- source [09/Feb/2020:18:00:25 +0000] "GET /admin/metadata
>     HTTP/1.1" 200 481 "-" "Mozilla/5.0" 0
>     Error.log
> 
>     [2020-02-09? 18:00:24] INFO connection/_handle_source_request Source
>     logging
>     in at mountpoint "/acdc.ogg" using "SOURCE" from xx.xx.xx.xxx as role
>     legacy-global-source
>     [2020-02-09? 18:00:24] WARN format/format_get_type Unsupported or legacy
>     stream type: "audio/mpeg". Falling back to generic minimal handler
>     for best
>     effort.
>     [2020-02-09? 18:00:25] INFO source/source_main listener count on
>     /acdc.ogg
>     now 0
>     [2020-02-09? 18:00:25] INFO admin/admin_handle_request Received admin
>     command metadata on mount '/acdc.ogg'
>     [2020-02-09? 18:00:25] INFO util/util_conv_string converting
>     metadata from
>     utf-8 to ISO8859-1
>     [2020-02-09? 18:00:25] INFO admin/command_metadata Metadata on
>     mountpoint
>     /acdc.ogg changed to " - "
> 
>     Source disconnects here.
>     .? ? ? ?No log entries - no source timeouts.
>     .? ? ? ?Mountpoint (here acdc.ogg) still active and visible in the admin
>     interface
>     .? ? ? ?Source client cannot reconnect - see message below:
> 
> 
>     Action: Source client tries to reconnect (port 8000 or 8444)
> 
>     Access.log
>     xx.xx.xx.xxx- - [09/Feb/2020:18:03:53 +0000] "SOURCE /acdc.ogg
>     HTTP/1.0" 401
>     777 "-" "libshout/2.4.1" 1
>     xx.xx.xx.xxx- source [09/Feb/2020:18:03:53 +0000] "SOURCE /acdc.ogg
>     HTTP/1.0" 409 706 "-" "libshout/2.4.1" 0
> 
>     Error.log
> 
>     [2020-02-09? 18:03:52] EROR connection/_handle_authed_client Client
>     (role=anonymous, username=(null)) not allowed to use this request
>     method on
>     /acdc.ogg
>     [2020-02-09? 18:03:52] EROR util/util_http_select_best Input string
>     does not
>     parse as KVA. Selecting first option.
>     [2020-02-09? 18:03:52] WARN reportxml/reportxml_database_build_report No
>     matching definition for "25387198-0643-4577-9139-7c4f24f59d4a"
>     [2020-02-09? 18:03:53] INFO connection/_handle_source_request Source
>     logging
>     in at mountpoint "/acdc.ogg" using "SOURCE" from xx.xx.xx.xxx as role
>     legacy-global-source
>     [2020-02-09? 18:03:53] EROR util/util_http_select_best Input string
>     does not
>     parse as KVA. Selecting first option.
>     [2020-02-09? 18:03:53] WARN reportxml/reportxml_database_build_report No
>     matching definition for "c5724467-5f85-48c7-b45a-915c3150c292"
>     [2020-02-09? 18:03:53] WARN connection/source_startup Mountpoint
>     /acdc.ogg
>     in use
> 
> 
>     Any pointers very welcome.
> 
>     Here is the config.xml file for the server used:
> 
>     <icecast>
>     ? ? <!-- 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>earth</location>
>     ? ? <admin>icemaster at localhost</admin>
> 
>     ? ? <!-- 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/
>     ? ?-->
> 
>     ? ? <limits>
>     ? ? ? ? <clients>100</clients>
>     ? ? ? ? <sources>2</sources>
>     ? ? ? ? <queue-size>524288</queue-size>
>     ? ? ? ? <client-timeout>30</client-timeout>
>     ? ? ? ? <header-timeout>15</header-timeout>
>     ? ? ? ? <source-timeout>10</source-timeout>
>     ? ? ? ? <!-- 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? -->
>     ? ? ? ? <burst-size>65535</burst-size>
>     ? ? </limits>
> 
>     ? ? <authentication>
>     ? ? ? ? <!-- Sources log in with username 'source' -->
>     ? ? ? ? <source-password>hackme57</source-password>
>     ? ? ? ? <!-- Relays log in with username 'relay' -->
>     ? ? ? ? <relay-password>hackme58</relay-password>
> 
>     ? ? ? ? <!-- Admin logs in with the username given below -->
>     ? ? ? ? <admin-user>admin</admin-user>
>     ? ? ? ? <admin-password>ITJShKNE0pRg</admin-password>
>     ? ? </authentication>
> 
>     ? ? <!-- 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
>     ? ? <shoutcast-mount>/live.nsv</shoutcast-mount>
>     ? ? -->
> 
>     ? ? <!-- Uncomment this if you want directory listings -->
>     ? ? <!--
>     ? ? <directory>
>     ? ? ? ? <yp-url-timeout>15</yp-url-timeout>
>     ? ? ? ? <yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url>
>     ? ? </directory>
>     ? ? -->
> 
>     ? ? <!-- 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!
>     ? ? -->
>     ? ? <hostname>localhost</hostname>
> 
>     ? ? <!-- You may have multiple <listener> elements -->
>     ? ? <listen-socket>
>     ? ? ? ? ? ?<port>8000</port>
>     ? ? ? ? ? ?<ssl>0</ssl>
>     ? ? ? ? <!-- <bind-address>127.0.0.1</bind-address> -->
>     ? ? ? ? <!-- <shoutcast-mount>/stream</shoutcast-mount> -->
>     ? ? </listen-socket>
>     ? ? <!--
>     ? ? <listen-socket>
>     ? ? ? ? <port>8080</port>
>     ? ? </listen-socket>
>     ? ? -->
> 
>     ? ? <listen-socket>
>     ? ? ? ? ? ?<port>8444</port>
>     ? ? ? ? <ssl>1</ssl>
>     ? ? </listen-socket>
> 
> 
>     ? ? <!-- 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.
>     ? ? -->
>     ? ? <http-headers>
>     ? ? ? ? <header name="Access-Control-Allow-Origin" value="*" />
>     ? ? </http-headers>
> 
> 
>     ? ? <!-- Relaying:
>     ? ? ? ? ?You don't need this if you only have one server.
>     ? ? ? ? ?Please refer to the config for a detailed explanation.
>     ? ? -->
>     ? ? <!--<master-server>127.0.0.1</master-server>-->
>     ? ? <!--<master-server-port>8001</master-server-port>-->
>     ? ? <!--<master-update-interval>120</master-update-interval>-->
>     ? ? <!--<master-password>hackme</master-password>-->
> 
>     ? ? <!-- 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 -->
>     ? ? <!--<relays-on-demand>1</relays-on-demand>-->
> 
>     ? ? <!--
>     ? ? <relay>
>     ? ? ? ? <server>127.0.0.1</server>
>     ? ? ? ? <port>8080</port>
>     ? ? ? ? <mount>/example.ogg</mount>
>     ? ? ? ? <local-mount>/different.ogg</local-mount>
>     ? ? ? ? <on-demand>0</on-demand>
> 
>     ? ? ? ? <relay-shoutcast-metadata>0</relay-shoutcast-metadata>
>     ? ? </relay>
>     ? ? -->
> 
> 
>     ? ? <!-- 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">
>     ? ? ? ? <public>0</public>
>     ? ? ? ? <intro>/server-wide-intro.ogg</intro>
>     ? ? ? ? <max-listener-duration>3600</max-listener-duration>
>     ? ? ? ? <authentication type="url">
>     ? ? ? ? ? ? ? ? <option name="mount_add"
>     value="http://auth.example.org/stream_start.php"/>
>     ? ? ? ? </authentication>
>     ? ? ? ? <http-headers>
>     ? ? ? ? ? ? ? ? <header name="foo" value="bar" />
>     ? ? ? ? </http-headers>
>     ? ? </mount>
>     ? ? -->
> 
>     ? ? <!-- Normal mounts -->
> 
>     ? ? <mount type="normal">
>     ? ? ? ? <mount-name>/acdc.ogg</mount-name>
> 
>     ? ? ? ? <!--username>othersource</username>
>     ? ? ? ? <password>hackme_1666</password-->
> 
>     ? ? ? ? <max-listeners>1</max-listeners>
>     ? ? ? ? <!--dump-file>/tmp/dump-example1.ogg</dump-file-->
>     ? ? ? ? <burst-size>65536</burst-size>
>     ? ? ? ? <!--fallback-mount>/example2.ogg</fallback-mount>
>     ? ? ? ? <fallback-override>1</fallback-override>
>     ? ? ? ? <fallback-when-full>1</fallback-when-full>
>     ? ? ? ? <intro>/example_intro.ogg</intro-->
>     ? ? ? ? <hidden>0</hidden>
>     ? ? ? ? <public>0</public>
>     ? ? ? ? <authentication type="htpasswd">
>     ? ? ? ? ? ? ?<option name="filename"
>     value="/var/log/icecast2/password"/>
>     ? ? ? ? ? ? ? ? <option name="allow_duplicate_users" value="0"/>
>     ? ? ? ? </authentication>
>     ? ? ? ? <http-headers>
>     ? ? ? ? ? ? ? ? <header name="Access-Control-Allow-Origin"
>     value="http://webplayer.example.org" />
>     ? ? ? ? </http-headers>
>     ? ? ? ? <!--on-connect>/home/icecast/bin/stream-start</on-connect>
>     ? ? ? ? <on-disconnect>/home/icecast/bin/stream-stop</on-disconnect-->
>     ? ? </mount>
> 
> 
>     ? ? <fileserve>1</fileserve>
> 
>     ? ? <paths>
>     ? ? ? ? <!-- basedir is only used if chroot is enabled -->
>     ? ? ? ? <basedir>./</basedir>
> 
>     ? ? ? ? <!-- Note that if <chroot> is turned on below, these paths
>     must both
>     ? ? ? ? ? ? ?be relative to the new root, not the original root -->
>     ? ? ? ? <logdir>/var/log/icecast2</logdir>
>     ? ? ? ?<webroot>/usr/local/share/icecast/web</webroot>
>     ? ? ? ?<adminroot>/usr/local/share/icecast/admin</adminroot>
>     ? ? ? ? <!-- <pidfile>/usr/share/icecast/icecast.pid</pidfile> -->
> 
>     ? ? ? ? <!-- 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.
>     ? ? -->
>     ? ? ? ? <ssl-certificate>/var/log/icecast2/icecast.pem</ssl-certificate>
>     ? ? </paths>
> 
>     ? ? <logging>
>     ? ? ? ? <accesslog>access.log</accesslog>
>     ? ? ? ? <errorlog>error.log</errorlog>
>     ? ? ? ? <!-- <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> -->
>     ? ? </logging>
> 
>     ? ? <security>
>     ? ? ? ? <chroot>0</chroot>
> 
>     ? ? ? ? <changeowner>
>     ? ? ? ? ? ? <user>icecast</user>
>     ? ? ? ? ? ? <group>icecast</group>
>     ? ? ? ? </changeowner>
> 
>     ? ? </security>
>     </icecast><?xml version="1.0" encoding="utf-8"?>
> 
> 
> 
> 
>     _______________________________________________
>     Icecast mailing list
>     Icecast at xiph.org <mailto:Icecast at xiph.org>
>     http://lists.xiph.org/mailman/listinfo/icecast
> 
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
> 


From abores at gmail.com  Tue Mar 31 23:24:04 2020
From: abores at gmail.com (=?utf-8?Q?Alex_Bor=C3=A9s?=)
Date: Wed, 1 Apr 2020 01:24:04 +0200
Subject: [Icecast] SSL connection fails: Invalid or missing password
Message-ID: <8F8F4687-52AB-492D-B023-A533C361D01E@gmail.com>

Hello, 

I have installed and configured Icecast 2.4.4 with SSL in Ubuntu 18.04.3. 

I can successfully connect to the server using the web browser and everything seems fine.

However, when I try to connect using an Icecast client such as LadioCast I see the following logs (server side):

[2020-03-31  16:50:29] INFO connection/get_ssl_certificate SSL certificate found at /etc/icecast2/bundle.pem
[2020-03-31  16:50:29] INFO connection/get_ssl_certificate SSL using ciphers (key)
[2020-03-31  16:51:07] INFO connection/_handle_source_request Source logging in at mountpoint "/live" from (ip address)
[2020-03-31  16:51:07] INFO connection/_handle_source_request Source (/live) attempted to login with invalid or missing password

The credentials are correctly set in the client and obviously not empty. Actually, if I just remove the <ssl>1</ssl> line from the config file the connection gets established.

Any ideas?

Please let me know if you need any additional context info. 

Thanks in advance.

Alex