From WillR at rice.edu  Wed Aug  9 03:46:01 2017
From: WillR at rice.edu (Will Robedee)
Date: Tue, 8 Aug 2017 22:46:01 -0500
Subject: [Icecast] Newbie Questions
Message-ID: <036d01d310c2$05091ee0$0f1b5ca0$@rice.edu>

I inherited an icecast server at a radio station.  I am not a linux/unix
person.  I am able to use putty and winscp to gain access.  I can use sudo
-s -H to gain root level access (dangerous, I know), but I do not know the
OS (or even which OS variant). 
 
First question, how do I determine what OS is being used?
 
Next question, I want to use logrotate.d to rotate (and archive) logs on a
monthly basis.  How is that done? 
 
What is a PID?
 
(Yes, I am a newbie!)
 
Will R
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20170808/dc055c36/attachment.htm>

From jake at jakebriggs.com  Wed Aug  9 06:21:50 2017
From: jake at jakebriggs.com (Jake)
Date: Wed, 09 Aug 2017 18:21:50 +1200
Subject: [Icecast] Newbie Question
In-Reply-To: <036d01d310c2$05091ee0$0f1b5ca0$@rice.edu>
References: <036d01d310c2$05091ee0$0f1b5ca0$@rice.edu>
Message-ID: <1098CE68-01E2-438F-87AB-2C52B122CE1C@jakebriggs.com>

Well first I guess Google :P 

Run 'uname -a' and that might give you a hint if the kernel isn't custom.

Also you could try the following:

'cat?/etc/*version'
'cat?/etc/debian_version'
'lsb_release -a:
'cat /etc/redhat-release'
'cat /etc/fedora-release'

If none of those commands help, then it might be something more exotic - but let's try the easy ones first.

A PID is a process id - every process has one, and they are assigned depending on when they run.

The logrotate question might be better answered once you know the version of linux that's running.

Jake



On 9 August 2017 3:46:01 PM NZST, Will Robedee <WillR at rice.edu> wrote:
>I inherited an icecast server at a radio station.  I am not a
>linux/unix
>person.  I am able to use putty and winscp to gain access.  I can use
>sudo
>-s -H to gain root level access (dangerous, I know), but I do not know
>the
>OS (or even which OS variant). 
> 
>First question, how do I determine what OS is being used?
> 
>Next question, I want to use logrotate.d to rotate (and archive) logs
>on a
>monthly basis.  How is that done? 
> 
>What is a PID?
> 
>(Yes, I am a newbie!)
> 
>Will R
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20170809/3769c2af/attachment.htm>

From willr at rice.edu  Wed Aug  9 19:33:27 2017
From: willr at rice.edu (Will R)
Date: Wed, 9 Aug 2017 14:33:27 -0500
Subject: [Icecast] Newbie Questions
Message-ID: <014b01d31146$5fa0e840$1ee2b8c0$@rice.edu>

[Will R] Appears to be Redhat. 

Will R
----------------------------------------------------------------------

Message: 1
Date: Tue, 8 Aug 2017 22:46:01 -0500
From: "Will Robedee" <WillR at rice.edu>
To: <icecast at xiph.org>
Subject: [Icecast] Newbie Questions
Message-ID: <036d01d310c2$05091ee0$0f1b5ca0$@rice.edu>
Content-Type: text/plain; charset="utf-8"

I inherited an icecast server at a radio station.  I am not a linux/unix person.  I am able to use putty and winscp to gain access.  I can use sudo -s -H to gain root level access (dangerous, I know), but I do not know the OS (or even which OS variant). 
 
First question, how do I determine what OS is being used?
 
Next question, I want to use logrotate.d to rotate (and archive) logs on a monthly basis.  How is that done? 
 
What is a PID?
 
(Yes, I am a newbie!)
 
Will R
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20170808/dc055c36/attachment-0001.html>

------------------------------

Message: 2
Date: Wed, 09 Aug 2017 18:21:50 +1200
From: Jake <jake at jakebriggs.com>
To: Icecast streaming server user discussions <icecast at xiph.org>
Subject: Re: [Icecast] Newbie Question
Message-ID: <1098CE68-01E2-438F-87AB-2C52B122CE1C at jakebriggs.com>
Content-Type: text/plain; charset="utf-8"

Well first I guess Google :P 

Run 'uname -a' and that might give you a hint if the kernel isn't custom.

Also you could try the following:

'cat /etc/*version'
'cat /etc/debian_version'
'lsb_release -a:
'cat /etc/redhat-release'
'cat /etc/fedora-release'

If none of those commands help, then it might be something more exotic - but let's try the easy ones first.

A PID is a process id - every process has one, and they are assigned depending on when they run.

The logrotate question might be better answered once you know the version of linux that's running.

Jake



On 9 August 2017 3:46:01 PM NZST, Will Robedee <WillR at rice.edu> wrote:
>I inherited an icecast server at a radio station.  I am not a 
>linux/unix person.  I am able to use putty and winscp to gain access.  
>I can use sudo -s -H to gain root level access (dangerous, I know), but 
>I do not know the OS (or even which OS variant).
> 
>First question, how do I determine what OS is being used?
> 
>Next question, I want to use logrotate.d to rotate (and archive) logs 
>on a monthly basis.  How is that done?
> 
>What is a PID?
> 
>(Yes, I am a newbie!)
> 
>Will R
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20170809/3769c2af/attachment.html>

------------------------------

Subject: Digest Footer

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


------------------------------

End of Icecast Digest, Vol 158, Issue 1
***************************************



From abitar.com at gmail.com  Thu Aug 10 16:46:47 2017
From: abitar.com at gmail.com (David Saunders)
Date: Thu, 10 Aug 2017 12:46:47 -0400
Subject: [Icecast] Newbie Questions
In-Reply-To: <014b01d31146$5fa0e840$1ee2b8c0$@rice.edu>
References: <014b01d31146$5fa0e840$1ee2b8c0$@rice.edu>
Message-ID: <CAOjZz+kL1U-R-D6tDnTCxOVGWt=L3k_V0W9GZU-Y8+r-+n8_uQ@mail.gmail.com>

Hey,

   Welcome to the world of servers. : Once you get it all setup it should
not be allot of work for you. It runs with very low maintenance.

  Most the Linux I seen do already rotate the logs.  You just have to
sometimes tell the programs where your icecast logs are to be rotated.

David.

On Wed, Aug 9, 2017 at 3:33 PM, Will R <willr at rice.edu> wrote:

> [Will R] Appears to be Redhat.
>
> Will R
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 8 Aug 2017 22:46:01 -0500
> From: "Will Robedee" <WillR at rice.edu>
> To: <icecast at xiph.org>
> Subject: [Icecast] Newbie Questions
> Message-ID: <036d01d310c2$05091ee0$0f1b5ca0$@rice.edu>
> Content-Type: text/plain; charset="utf-8"
>
> I inherited an icecast server at a radio station.  I am not a linux/unix
> person.  I am able to use putty and winscp to gain access.  I can use sudo
> -s -H to gain root level access (dangerous, I know), but I do not know the
> OS (or even which OS variant).
>
> First question, how do I determine what OS is being used?
>
> Next question, I want to use logrotate.d to rotate (and archive) logs on a
> monthly basis.  How is that done?
>
> What is a PID?
>
> (Yes, I am a newbie!)
>
> Will R
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.xiph.org/pipermail/icecast/attachments/
> 20170808/dc055c36/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 09 Aug 2017 18:21:50 +1200
> From: Jake <jake at jakebriggs.com>
> To: Icecast streaming server user discussions <icecast at xiph.org>
> Subject: Re: [Icecast] Newbie Question
> Message-ID: <1098CE68-01E2-438F-87AB-2C52B122CE1C at jakebriggs.com>
> Content-Type: text/plain; charset="utf-8"
>
> Well first I guess Google :P
>
> Run 'uname -a' and that might give you a hint if the kernel isn't custom.
>
> Also you could try the following:
>
> 'cat /etc/*version'
> 'cat /etc/debian_version'
> 'lsb_release -a:
> 'cat /etc/redhat-release'
> 'cat /etc/fedora-release'
>
> If none of those commands help, then it might be something more exotic -
> but let's try the easy ones first.
>
> A PID is a process id - every process has one, and they are assigned
> depending on when they run.
>
> The logrotate question might be better answered once you know the version
> of linux that's running.
>
> Jake
>
>
>
> On 9 August 2017 3:46:01 PM NZST, Will Robedee <WillR at rice.edu> wrote:
> >I inherited an icecast server at a radio station.  I am not a
> >linux/unix person.  I am able to use putty and winscp to gain access.
> >I can use sudo -s -H to gain root level access (dangerous, I know), but
> >I do not know the OS (or even which OS variant).
> >
> >First question, how do I determine what OS is being used?
> >
> >Next question, I want to use logrotate.d to rotate (and archive) logs
> >on a monthly basis.  How is that done?
> >
> >What is a PID?
> >
> >(Yes, I am a newbie!)
> >
> >Will R
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.xiph.org/pipermail/icecast/attachments/
> 20170809/3769c2af/attachment.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
>
> ------------------------------
>
> End of Icecast Digest, Vol 158, Issue 1
> ***************************************
>
> _______________________________________________
> 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/20170810/d765b3ac/attachment.htm>

From artuch at speedy.com.ar  Fri Aug 11 18:28:11 2017
From: artuch at speedy.com.ar (=?ISO-8859-1?Q?Jos=E9?= Luis Artuch)
Date: Fri, 11 Aug 2017 15:28:11 -0300
Subject: [Icecast] SSL Setup
In-Reply-To: <1500659727.4083.0.camel@gmail.com>
References: <ojul1i$lu4$1@blaine.gmane.org>
 <1499685764.1836.3.camel@de.loewenfelsen.net>
 <1500655290.1748.5.camel@speedy.com.ar> <1500657006.2948.3.camel@gmail.com>
 <1500658061.2948.5.camel@speedy.com.ar> <1500659727.4083.0.camel@gmail.com>
Message-ID: <1502476091.10092.2.camel@speedy.com.ar>

Hi !
Still fighting here :)

/var/log/icecast2/error.log
...
[2017-08-08??03:05:34] INFO main/main Icecast 2.4.2 server started
[2017-08-08??03:05:34] INFO connection/get_ssl_certificate No SSL
capability ***
[2017-08-08??03:05:34] INFO yp/yp_update_thread YP update thread
started
...

What exactly does *** mean ?.

Thanks !
Jos? Luis

El vie, 21-07-2017 a las 19:44 +0200, Marvin Scholz escribi?:
> 
> On 21 Jul 2017, at 19:27, Jos? Luis Artuch wrote:
> 
> > El vie, 21-07-2017 a las 19:07 +0200, Marvin Scholz escribi?:
> > > 
> > > On 21 Jul 2017, at 18:41, Jos? Luis Artuch wrote:
> > > 
> > > > Hello !
> > > > 
> > > > El lun, 10-07-2017 a las 09:31 +0000, Philipp Schafft escribi?:
> > > > > Good morning,
> > > > > 
> > > > > 
> > > > > On Mon, 2017-07-10 at 01:25 +0000, ScanCaster wrote:
> > > > > > IceCast is one of the last services I have that doesn't
> > > > > > connect
> > > > > > securely,?
> > > > > > and I am looking to close that hole....
> > > > > > [...]
> > > > > > OK... add a port for SSL for IceCast in icecast.xml...path
> > > > > > for
> > > > > > cert
> > > > > > file?
> > > > > > in same.... no biggie
> > > > > 
> > > > > The <ssl-certificate> belongs in the <paths> section of the
> > > > > config
> > > > > file.
> > > > > (I'm not sure what you mean with 'in same', just wanted to
> > > > > make
> > > > > it
> > > > > clear.)
> > > > > 
> > > > > 
> > > > > > The key/cert needs to be in a dir and file with applicable
> > > > > > permissions?
> > > > > > for the IceCast user... no biggie..
> > > > > > 
> > > > > > chown icecastusergroup:icecastusergroup??certfile
> > > > > 
> > > > > 
> > > > > > What I am looking to confirm is that the cert file needs to
> > > > > > contain:
> > > > > > 
> > > > > > -----BEGIN RSA PRIVATE KEY-----
> > > > > > MII
> > > > > > -----END RSA PRIVATE KEY-----
> > > > > > 
> > > > > > -----BEGIN CERTIFICATE-----
> > > > > > MI
> > > > > > -----END CERTIFICATE-----?
> > > > > > 
> > > > > > Where the Cert is the file/text Comodo sends me, and the
> > > > > > key is
> > > > > > the
> > > > > > one?
> > > > > > openssl spit out earlier,?
> > > > > > 
> > > > > > Combine them up in certfile, Correct? Special order?? KEY
> > > > > > then
> > > > > > Cert, or v-
> > > > > > v? Line separating them?
> > > > > 
> > > > > The format is the OpenSSL format: key, blank line, cert
> > > > > (chain).
> > > > > echo | cat key.pem - cert.pem > combo.pem
> > > > > 
> > > > > 
> > > > > > kill -HUP pidOfIcecast
> > > > > 
> > > > > As of Icecast2 2.4.x you need to restart Icecast to reload
> > > > > the
> > > > > cert.
> > > > > There is however a fix in 2.5.x (development) which is
> > > > > hopefully
> > > > > released with the next development update.
> > > > > 
> > > > > 
> > > > > > And good????
> > > > > > 
> > > > > > One thing can the web server spit out just a text file that
> > > > > > is
> > > > > > used
> > > > > > by?
> > > > > > Comodo to verify ownership of the domain? The DNS method
> > > > > > normally?
> > > > > > fails....
> > > > > 
> > > > > Sure. Just put it into the webroot (<webroot> in <paths>).
> > > > > Icecast
> > > > > handles files in webroot according to your operating system's
> > > > > mine-
> > > > > type
> > > > > table.
> > > > > 
> > > > 
> > > > On Debian 9, in the configuration file it says:
> > > > 
> > > > <webroot>/usr/share/icecast2/web</webroot>
> > > > <ssl-certificate>/usr/share/icecast2/icecast.pem</ssl-
> > > > certificate>
> > > > 
> > > > What should be the correct path of the icecast.pem file ?.
> > > > Should it be /usr/share/icecast2/web/icecast.pem ?.
> > > 
> > > You certainly do not want to put your private key in your public
> > > webroot...
> > > 
> > 
> > Thanks Marvin. Is ok into any other directory, for example
> > /etc/icecast2/ssl ?.
> 
> I think so, yes.
> 
> > > > 
> > > > Thanks.
> > > > > 
> > > > > > ie: http://icecast.domain.invalid/somestringofletersnumbers
> > > > > > .txt
> > > > > > That they?
> > > > > > request if its dumped in the webroot stuff of Icecast? With
> > > > > > out
> > > > > > any
> > > > > > XSLT?
> > > > > > markup?
> > > > > 
> > > > > Icecast only processes XSLT files as XSLT.
> > > > > 
> > > > > 
> > > > > > So if I added a listening port on 80 for this, then took it
> > > > > > away,?
> > > > > > since I don't use that for Icecast... Icecast is on its own
> > > > > > server
> > > > > > which?
> > > > > > does not have Apache... web stuff for other things is on
> > > > > > its
> > > > > > own
> > > > > > box. I?
> > > > > > never have used the Icecast to server up anything other
> > > > > > than
> > > > > > the
> > > > > > default?
> > > > > > admin etc. stuff it does by default...
> > > > > 
> > > > > To avoid the need to run Icecast as privileged user in oder
> > > > > to
> > > > > bind
> > > > > to
> > > > > low ports (if Comodo really insists in using port 80) you can
> > > > > use
> > > > > your
> > > > > firewall to do a local redirect.
> > > > > 
> > > > > 
> > > > > Hope this is of help to you,
> > > > > 
> > > > > with best regards,
> > > > > 
> > > > > 
> > > > > _______________________________________________
> > > > > 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
> > 
> > _______________________________________________
> > 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 bubba4lyfe at gmail.com  Fri Aug 11 18:37:42 2017
From: bubba4lyfe at gmail.com (bubba watson)
Date: Fri, 11 Aug 2017 13:37:42 -0500
Subject: [Icecast] SSL Setup
In-Reply-To: <1502476091.10092.2.camel@speedy.com.ar>
References: <ojul1i$lu4$1@blaine.gmane.org>
 <1499685764.1836.3.camel@de.loewenfelsen.net>
 <1500655290.1748.5.camel@speedy.com.ar> <1500657006.2948.3.camel@gmail.com>
 <1500658061.2948.5.camel@speedy.com.ar> <1500659727.4083.0.camel@gmail.com>
 <1502476091.10092.2.camel@speedy.com.ar>
Message-ID: <7F62B1EB-225E-4E18-9036-7A2C0847057E@gmail.com>

It is a server message indicator. It is used to distinguish server messages.

Sent from my iPhone

> On Aug 11, 2017, at 13:28, Jos? Luis Artuch <artuch at speedy.com.ar> wrote:
> 
> Hi !
> Still fighting here :)
> 
> /var/log/icecast2/error.log
> ...
> [2017-08-08  03:05:34] INFO main/main Icecast 2.4.2 server started
> [2017-08-08  03:05:34] INFO connection/get_ssl_certificate No SSL
> capability ***
> [2017-08-08  03:05:34] INFO yp/yp_update_thread YP update thread
> started
> ...
> 
> What exactly does *** mean ?.
> 
> Thanks !
> Jos? Luis
> 
>> El vie, 21-07-2017 a las 19:44 +0200, Marvin Scholz escribi?:
>> 
>>> On 21 Jul 2017, at 19:27, Jos? Luis Artuch wrote:
>>> 
>>>> El vie, 21-07-2017 a las 19:07 +0200, Marvin Scholz escribi?:
>>>> 
>>>>> On 21 Jul 2017, at 18:41, Jos? Luis Artuch wrote:
>>>>> 
>>>>> Hello !
>>>>> 
>>>>>> El lun, 10-07-2017 a las 09:31 +0000, Philipp Schafft escribi?:
>>>>>> Good morning,
>>>>>> 
>>>>>> 
>>>>>>> On Mon, 2017-07-10 at 01:25 +0000, ScanCaster wrote:
>>>>>>> IceCast is one of the last services I have that doesn't
>>>>>>> connect
>>>>>>> securely, 
>>>>>>> and I am looking to close that hole....
>>>>>>> [...]
>>>>>>> OK... add a port for SSL for IceCast in icecast.xml...path
>>>>>>> for
>>>>>>> cert
>>>>>>> file 
>>>>>>> in same.... no biggie
>>>>>> 
>>>>>> The <ssl-certificate> belongs in the <paths> section of the
>>>>>> config
>>>>>> file.
>>>>>> (I'm not sure what you mean with 'in same', just wanted to
>>>>>> make
>>>>>> it
>>>>>> clear.)
>>>>>> 
>>>>>> 
>>>>>>> The key/cert needs to be in a dir and file with applicable
>>>>>>> permissions 
>>>>>>> for the IceCast user... no biggie..
>>>>>>> 
>>>>>>> chown icecastusergroup:icecastusergroup  certfile
>>>>>> 
>>>>>> 
>>>>>>> What I am looking to confirm is that the cert file needs to
>>>>>>> contain:
>>>>>>> 
>>>>>>> -----BEGIN RSA PRIVATE KEY-----
>>>>>>> MII
>>>>>>> -----END RSA PRIVATE KEY-----
>>>>>>> 
>>>>>>> -----BEGIN CERTIFICATE-----
>>>>>>> MI
>>>>>>> -----END CERTIFICATE----- 
>>>>>>> 
>>>>>>> Where the Cert is the file/text Comodo sends me, and the
>>>>>>> key is
>>>>>>> the
>>>>>>> one 
>>>>>>> openssl spit out earlier, 
>>>>>>> 
>>>>>>> Combine them up in certfile, Correct? Special order?? KEY
>>>>>>> then
>>>>>>> Cert, or v-
>>>>>>> v? Line separating them?
>>>>>> 
>>>>>> The format is the OpenSSL format: key, blank line, cert
>>>>>> (chain).
>>>>>> echo | cat key.pem - cert.pem > combo.pem
>>>>>> 
>>>>>> 
>>>>>>> kill -HUP pidOfIcecast
>>>>>> 
>>>>>> As of Icecast2 2.4.x you need to restart Icecast to reload
>>>>>> the
>>>>>> cert.
>>>>>> There is however a fix in 2.5.x (development) which is
>>>>>> hopefully
>>>>>> released with the next development update.
>>>>>> 
>>>>>> 
>>>>>>> And good????
>>>>>>> 
>>>>>>> One thing can the web server spit out just a text file that
>>>>>>> is
>>>>>>> used
>>>>>>> by 
>>>>>>> Comodo to verify ownership of the domain? The DNS method
>>>>>>> normally 
>>>>>>> fails....
>>>>>> 
>>>>>> Sure. Just put it into the webroot (<webroot> in <paths>).
>>>>>> Icecast
>>>>>> handles files in webroot according to your operating system's
>>>>>> mine-
>>>>>> type
>>>>>> table.
>>>>>> 
>>>>> 
>>>>> On Debian 9, in the configuration file it says:
>>>>> 
>>>>> <webroot>/usr/share/icecast2/web</webroot>
>>>>> <ssl-certificate>/usr/share/icecast2/icecast.pem</ssl-
>>>>> certificate>
>>>>> 
>>>>> What should be the correct path of the icecast.pem file ?.
>>>>> Should it be /usr/share/icecast2/web/icecast.pem ?.
>>>> 
>>>> You certainly do not want to put your private key in your public
>>>> webroot...
>>>> 
>>> 
>>> Thanks Marvin. Is ok into any other directory, for example
>>> /etc/icecast2/ssl ?.
>> 
>> I think so, yes.
>> 
>>>>> 
>>>>> Thanks.
>>>>>> 
>>>>>>> ie: http://icecast.domain.invalid/somestringofletersnumbers
>>>>>>> .txt
>>>>>>> That they 
>>>>>>> request if its dumped in the webroot stuff of Icecast? With
>>>>>>> out
>>>>>>> any
>>>>>>> XSLT 
>>>>>>> markup?
>>>>>> 
>>>>>> Icecast only processes XSLT files as XSLT.
>>>>>> 
>>>>>> 
>>>>>>> So if I added a listening port on 80 for this, then took it
>>>>>>> away, 
>>>>>>> since I don't use that for Icecast... Icecast is on its own
>>>>>>> server
>>>>>>> which 
>>>>>>> does not have Apache... web stuff for other things is on
>>>>>>> its
>>>>>>> own
>>>>>>> box. I 
>>>>>>> never have used the Icecast to server up anything other
>>>>>>> than
>>>>>>> the
>>>>>>> default 
>>>>>>> admin etc. stuff it does by default...
>>>>>> 
>>>>>> To avoid the need to run Icecast as privileged user in oder
>>>>>> to
>>>>>> bind
>>>>>> to
>>>>>> low ports (if Comodo really insists in using port 80) you can
>>>>>> use
>>>>>> your
>>>>>> firewall to do a local redirect.
>>>>>> 
>>>>>> 
>>>>>> Hope this is of help to you,
>>>>>> 
>>>>>> with best regards,
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> 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
>>> 
>>> _______________________________________________
>>> 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


From artuch at speedy.com.ar  Fri Aug 11 18:52:35 2017
From: artuch at speedy.com.ar (=?ISO-8859-1?Q?Jos=E9?= Luis Artuch)
Date: Fri, 11 Aug 2017 15:52:35 -0300
Subject: [Icecast] SSL Setup
In-Reply-To: <1502477250.10092.5.camel@gmail.com>
References: <ojul1i$lu4$1@blaine.gmane.org>
 <1499685764.1836.3.camel@de.loewenfelsen.net>
 <1500655290.1748.5.camel@speedy.com.ar> <1500657006.2948.3.camel@gmail.com>
 <1500658061.2948.5.camel@speedy.com.ar> <1500659727.4083.0.camel@gmail.com>
 <1502476091.10092.2.camel@speedy.com.ar>
 <1502477250.10092.5.camel@gmail.com>
Message-ID: <1502477555.10092.7.camel@speedy.com.ar>

Thanks bubba, but I am referring to the meaning of the line:
"... INFO connection/get_ssl_certificate No SSL capability"

El vie, 11-08-2017 a las 13:37 -0500, bubba watson escribi?:
> It is a server message indicator. It is used to distinguish server
> messages.
> 
> Sent from my iPhone
> 
> > On Aug 11, 2017, at 13:28, Jos? Luis Artuch <artuch at speedy.com.ar>
> > wrote:
> > 
> > Hi !
> > Still fighting here :)
> > 
> > /var/log/icecast2/error.log
> > ...
> > [2017-08-08??03:05:34] INFO main/main Icecast 2.4.2 server started
> > [2017-08-08??03:05:34] INFO connection/get_ssl_certificate No SSL
> > capability ***
> > [2017-08-08??03:05:34] INFO yp/yp_update_thread YP update thread
> > started
> > ...
> > 
> > What exactly does *** mean ?.
> > 
> > Thanks !
> > Jos? Luis
> > 
> > > El vie, 21-07-2017 a las 19:44 +0200, Marvin Scholz escribi?:
> > > 
> > > > On 21 Jul 2017, at 19:27, Jos? Luis Artuch wrote:
> > > > 
> > > > > El vie, 21-07-2017 a las 19:07 +0200, Marvin Scholz escribi?:
> > > > > 
> > > > > > On 21 Jul 2017, at 18:41, Jos? Luis Artuch wrote:
> > > > > > 
> > > > > > Hello !
> > > > > > 
> > > > > > > El lun, 10-07-2017 a las 09:31 +0000, Philipp Schafft
> > > > > > > escribi?:
> > > > > > > Good morning,
> > > > > > > 
> > > > > > > 
> > > > > > > > On Mon, 2017-07-10 at 01:25 +0000, ScanCaster wrote:
> > > > > > > > IceCast is one of the last services I have that doesn't
> > > > > > > > connect
> > > > > > > > securely,?
> > > > > > > > and I am looking to close that hole....
> > > > > > > > [...]
> > > > > > > > OK... add a port for SSL for IceCast in
> > > > > > > > icecast.xml...path
> > > > > > > > for
> > > > > > > > cert
> > > > > > > > file?
> > > > > > > > in same.... no biggie
> > > > > > > 
> > > > > > > The <ssl-certificate> belongs in the <paths> section of
> > > > > > > the
> > > > > > > config
> > > > > > > file.
> > > > > > > (I'm not sure what you mean with 'in same', just wanted
> > > > > > > to
> > > > > > > make
> > > > > > > it
> > > > > > > clear.)
> > > > > > > 
> > > > > > > 
> > > > > > > > The key/cert needs to be in a dir and file with
> > > > > > > > applicable
> > > > > > > > permissions?
> > > > > > > > for the IceCast user... no biggie..
> > > > > > > > 
> > > > > > > > chown icecastusergroup:icecastusergroup??certfile
> > > > > > > 
> > > > > > > 
> > > > > > > > What I am looking to confirm is that the cert file
> > > > > > > > needs to
> > > > > > > > contain:
> > > > > > > > 
> > > > > > > > -----BEGIN RSA PRIVATE KEY-----
> > > > > > > > MII
> > > > > > > > -----END RSA PRIVATE KEY-----
> > > > > > > > 
> > > > > > > > -----BEGIN CERTIFICATE-----
> > > > > > > > MI
> > > > > > > > -----END CERTIFICATE-----?
> > > > > > > > 
> > > > > > > > Where the Cert is the file/text Comodo sends me, and
> > > > > > > > the
> > > > > > > > key is
> > > > > > > > the
> > > > > > > > one?
> > > > > > > > openssl spit out earlier,?
> > > > > > > > 
> > > > > > > > Combine them up in certfile, Correct? Special order??
> > > > > > > > KEY
> > > > > > > > then
> > > > > > > > Cert, or v-
> > > > > > > > v? Line separating them?
> > > > > > > 
> > > > > > > The format is the OpenSSL format: key, blank line, cert
> > > > > > > (chain).
> > > > > > > echo | cat key.pem - cert.pem > combo.pem
> > > > > > > 
> > > > > > > 
> > > > > > > > kill -HUP pidOfIcecast
> > > > > > > 
> > > > > > > As of Icecast2 2.4.x you need to restart Icecast to
> > > > > > > reload
> > > > > > > the
> > > > > > > cert.
> > > > > > > There is however a fix in 2.5.x (development) which is
> > > > > > > hopefully
> > > > > > > released with the next development update.
> > > > > > > 
> > > > > > > 
> > > > > > > > And good????
> > > > > > > > 
> > > > > > > > One thing can the web server spit out just a text file
> > > > > > > > that
> > > > > > > > is
> > > > > > > > used
> > > > > > > > by?
> > > > > > > > Comodo to verify ownership of the domain? The DNS
> > > > > > > > method
> > > > > > > > normally?
> > > > > > > > fails....
> > > > > > > 
> > > > > > > Sure. Just put it into the webroot (<webroot> in
> > > > > > > <paths>).
> > > > > > > Icecast
> > > > > > > handles files in webroot according to your operating
> > > > > > > system's
> > > > > > > mine-
> > > > > > > type
> > > > > > > table.
> > > > > > > 
> > > > > > 
> > > > > > On Debian 9, in the configuration file it says:
> > > > > > 
> > > > > > <webroot>/usr/share/icecast2/web</webroot>
> > > > > > <ssl-certificate>/usr/share/icecast2/icecast.pem</ssl-
> > > > > > certificate>
> > > > > > 
> > > > > > What should be the correct path of the icecast.pem file ?.
> > > > > > Should it be /usr/share/icecast2/web/icecast.pem ?.
> > > > > 
> > > > > You certainly do not want to put your private key in your
> > > > > public
> > > > > webroot...
> > > > > 
> > > > 
> > > > Thanks Marvin. Is ok into any other directory, for example
> > > > /etc/icecast2/ssl ?.
> > > 
> > > I think so, yes.
> > > 
> > > > > > 
> > > > > > Thanks.
> > > > > > > 
> > > > > > > > ie: http://icecast.domain.invalid/somestringofletersnum
> > > > > > > > bers
> > > > > > > > .txt
> > > > > > > > That they?
> > > > > > > > request if its dumped in the webroot stuff of Icecast?
> > > > > > > > With
> > > > > > > > out
> > > > > > > > any
> > > > > > > > XSLT?
> > > > > > > > markup?
> > > > > > > 
> > > > > > > Icecast only processes XSLT files as XSLT.
> > > > > > > 
> > > > > > > 
> > > > > > > > So if I added a listening port on 80 for this, then
> > > > > > > > took it
> > > > > > > > away,?
> > > > > > > > since I don't use that for Icecast... Icecast is on its
> > > > > > > > own
> > > > > > > > server
> > > > > > > > which?
> > > > > > > > does not have Apache... web stuff for other things is
> > > > > > > > on
> > > > > > > > its
> > > > > > > > own
> > > > > > > > box. I?
> > > > > > > > never have used the Icecast to server up anything other
> > > > > > > > than
> > > > > > > > the
> > > > > > > > default?
> > > > > > > > admin etc. stuff it does by default...
> > > > > > > 
> > > > > > > To avoid the need to run Icecast as privileged user in
> > > > > > > oder
> > > > > > > to
> > > > > > > bind
> > > > > > > to
> > > > > > > low ports (if Comodo really insists in using port 80) you
> > > > > > > can
> > > > > > > use
> > > > > > > your
> > > > > > > firewall to do a local redirect.
> > > > > > > 
> > > > > > > 
> > > > > > > Hope this is of help to you,
> > > > > > > 
> > > > > > > with best regards,
> > > > > > > 
> > > > > > > 
> > > > > > > _______________________________________________
> > > > > > > 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
> > > > 
> > > > _______________________________________________
> > > > 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
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From hoggins at radiom.fr  Fri Aug 18 08:51:58 2017
From: hoggins at radiom.fr (Hoggins!)
Date: Fri, 18 Aug 2017 10:51:58 +0200
Subject: [Icecast] dir.xiph.org : Incorrect <hostname> when listenurl scheme
	is https
Message-ID: <eb8e368c-6727-8141-af57-f3cc8a9d723f@radiom.fr>

Hello,

Title says it all : dir.xiph.org rejects add / update requests when we
put https instead of http in our listenurl.

Is that expected ?

    Thanks !

        Hoggins!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20170818/dbb29de1/attachment.sig>

From artuch at speedy.com.ar  Wed Aug 23 12:08:27 2017
From: artuch at speedy.com.ar (=?ISO-8859-1?Q?Jos=E9?= Luis Artuch)
Date: Wed, 23 Aug 2017 09:08:27 -0300
Subject: [Icecast] Change bitrate
In-Reply-To: <1500659727.4083.0.camel@gmail.com>
References: <ojul1i$lu4$1@blaine.gmane.org>
 <1499685764.1836.3.camel@de.loewenfelsen.net>
 <1500655290.1748.5.camel@speedy.com.ar> <1500657006.2948.3.camel@gmail.com>
 <1500658061.2948.5.camel@speedy.com.ar> <1500659727.4083.0.camel@gmail.com>
Message-ID: <1503490107.1615.6.camel@speedy.com.ar>

Hello, good morning !
Running Icecast2 and Ices2 with live audio from Line IN, what is the
correct way to change the bitrate ?.
In the Icecast2 configuration file I set:

<mount type="normal">
????<mount-name>/entzun.opus</mount-name>
????<bitrate>128</bitrate>
</mount>

But it seems that is not enough since the bitrate does not change.
Receiving the stream with Rhythmbox,?after restart the server the
bitrate is not 128 kbps.
If required, how should I set the Ices2 configuration file ?.
Thanks !.
Jos? Luis


From epirat07 at gmail.com  Wed Aug 23 12:13:51 2017
From: epirat07 at gmail.com (Marvin Scholz)
Date: Wed, 23 Aug 2017 14:13:51 +0200
Subject: [Icecast] Change bitrate
In-Reply-To: <1503490107.1615.6.camel@speedy.com.ar>
References: <ojul1i$lu4$1@blaine.gmane.org>
 <1499685764.1836.3.camel@de.loewenfelsen.net>
 <1500655290.1748.5.camel@speedy.com.ar> <1500657006.2948.3.camel@gmail.com>
 <1500658061.2948.5.camel@speedy.com.ar> <1500659727.4083.0.camel@gmail.com>
 <1503490107.1615.6.camel@speedy.com.ar>
Message-ID: <25AAE2C1-1547-4394-BC71-148B2EE52C8B@gmail.com>



On 23 Aug 2017, at 14:08, Jos? Luis Artuch wrote:

> Hello, good morning !
> Running Icecast2 and Ices2 with live audio from Line IN, what is the
> correct way to change the bitrate ?.
> In the Icecast2 configuration file I set:
>
> <mount type="normal">
> ????<mount-name>/entzun.opus</mount-name>
> ????<bitrate>128</bitrate>
> </mount>

This option should not be used and does not do what you expect it does.
Icecast can't change the bitrate, the source client needs to do that.

>
> But it seems that is not enough since the bitrate does not change.
> Receiving the stream with Rhythmbox,?after restart the server the
> bitrate is not 128 kbps.
> If required, how should I set the Ices2 configuration file ?.
> Thanks !.
> Jos? Luis
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From artuch at speedy.com.ar  Wed Aug 23 12:40:49 2017
From: artuch at speedy.com.ar (=?ISO-8859-1?Q?Jos=E9?= Luis Artuch)
Date: Wed, 23 Aug 2017 09:40:49 -0300
Subject: [Icecast] Change bitrate
In-Reply-To: <25AAE2C1-1547-4394-BC71-148B2EE52C8B@gmail.com>
References: <ojul1i$lu4$1@blaine.gmane.org>
 <1499685764.1836.3.camel@de.loewenfelsen.net>
 <1500655290.1748.5.camel@speedy.com.ar> <1500657006.2948.3.camel@gmail.com>
 <1500658061.2948.5.camel@speedy.com.ar> <1500659727.4083.0.camel@gmail.com>
 <1503490107.1615.6.camel@speedy.com.ar>
 <25AAE2C1-1547-4394-BC71-148B2EE52C8B@gmail.com>
Message-ID: <1503492049.1615.11.camel@speedy.com.ar>

El mi?, 23-08-2017 a las 14:13 +0200, Marvin Scholz escribi?:
> 
> On 23 Aug 2017, at 14:08, Jos? Luis Artuch wrote:
> 
> > Hello, good morning !
> > Running Icecast2 and Ices2 with live audio from Line IN, what is
> > the
> > correct way to change the bitrate ?.
> > In the Icecast2 configuration file I set:
> > 
> > <mount type="normal">
> > ????<mount-name>/entzun.opus</mount-name>
> > ????<bitrate>128</bitrate>
> > </mount>
> 
> This option should not be used and does not do what you expect it
> does.
> Icecast can't change the bitrate, the source client needs to do that.
> 
Thanks Marvin,
I also made a test with the Ices2 configuration file:

<encode>
????<bitrate>128</bitrate>
????<samplerate>44100</samplerate>
????<channels>2</channels>
</encode>

But the bitrate did not change.
> > 
> > But it seems that is not enough since the bitrate does not change.
> > Receiving the stream with Rhythmbox,?after restart the server the
> > bitrate is not 128 kbps.
> > If required, how should I set the Ices2 configuration file ?.
> > 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 epirat07 at gmail.com  Wed Aug 23 12:42:03 2017
From: epirat07 at gmail.com (Marvin Scholz)
Date: Wed, 23 Aug 2017 14:42:03 +0200
Subject: [Icecast] Change bitrate
In-Reply-To: <1503492049.1615.11.camel@speedy.com.ar>
References: <ojul1i$lu4$1@blaine.gmane.org>
 <1499685764.1836.3.camel@de.loewenfelsen.net>
 <1500655290.1748.5.camel@speedy.com.ar> <1500657006.2948.3.camel@gmail.com>
 <1500658061.2948.5.camel@speedy.com.ar> <1500659727.4083.0.camel@gmail.com>
 <1503490107.1615.6.camel@speedy.com.ar>
 <25AAE2C1-1547-4394-BC71-148B2EE52C8B@gmail.com>
 <1503492049.1615.11.camel@speedy.com.ar>
Message-ID: <2CAE19E9-4915-44D2-8D83-85E67C25208C@gmail.com>



On 23 Aug 2017, at 14:40, Jos? Luis Artuch wrote:

> El mi?, 23-08-2017 a las 14:13 +0200, Marvin Scholz escribi?:
>>
>> On 23 Aug 2017, at 14:08, Jos? Luis Artuch wrote:
>>
>>> Hello, good morning !
>>> Running Icecast2 and Ices2 with live audio from Line IN, what is
>>> the
>>> correct way to change the bitrate ?.
>>> In the Icecast2 configuration file I set:
>>>
>>> <mount type="normal">
>>> ????<mount-name>/entzun.opus</mount-name>
>>> ????<bitrate>128</bitrate>
>>> </mount>
>>
>> This option should not be used and does not do what you expect it
>> does.
>> Icecast can't change the bitrate, the source client needs to do that.
>>
> Thanks Marvin,
> I also made a test with the Ices2 configuration file:
>
> <encode>
> ????<bitrate>128</bitrate>
> ????<samplerate>44100</samplerate>
> ????<channels>2</channels>
> </encode>
>
> But the bitrate did not change.

AFAIK Ices2 does not re-encode therefore it is unable to change
the bitrate.

>>>
>>> But it seems that is not enough since the bitrate does not change.
>>> Receiving the stream with Rhythmbox,?after restart the server the
>>> bitrate is not 128 kbps.
>>> If required, how should I set the Ices2 configuration file ?.
>>> 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


From artuch at speedy.com.ar  Wed Aug 23 12:50:51 2017
From: artuch at speedy.com.ar (=?ISO-8859-1?Q?Jos=E9?= Luis Artuch)
Date: Wed, 23 Aug 2017 09:50:51 -0300
Subject: [Icecast] Change bitrate
In-Reply-To: <2CAE19E9-4915-44D2-8D83-85E67C25208C@gmail.com>
References: <ojul1i$lu4$1@blaine.gmane.org>
 <1499685764.1836.3.camel@de.loewenfelsen.net>
 <1500655290.1748.5.camel@speedy.com.ar> <1500657006.2948.3.camel@gmail.com>
 <1500658061.2948.5.camel@speedy.com.ar> <1500659727.4083.0.camel@gmail.com>
 <1503490107.1615.6.camel@speedy.com.ar>
 <25AAE2C1-1547-4394-BC71-148B2EE52C8B@gmail.com>
 <1503492049.1615.11.camel@speedy.com.ar>
 <2CAE19E9-4915-44D2-8D83-85E67C25208C@gmail.com>
Message-ID: <1503492651.1615.14.camel@speedy.com.ar>

El mi?, 23-08-2017 a las 14:42 +0200, Marvin Scholz escribi?:
> 
> On 23 Aug 2017, at 14:40, Jos? Luis Artuch wrote:
> 
> > El mi?, 23-08-2017 a las 14:13 +0200, Marvin Scholz escribi?:
> > > 
> > > On 23 Aug 2017, at 14:08, Jos? Luis Artuch wrote:
> > > 
> > > > Hello, good morning !
> > > > Running Icecast2 and Ices2 with live audio from Line IN, what
> > > > is
> > > > the
> > > > correct way to change the bitrate ?.
> > > > In the Icecast2 configuration file I set:
> > > > 
> > > > <mount type="normal">
> > > > ????<mount-name>/entzun.opus</mount-name>
> > > > ????<bitrate>128</bitrate>
> > > > </mount>
> > > 
> > > This option should not be used and does not do what you expect it
> > > does.
> > > Icecast can't change the bitrate, the source client needs to do
> > > that.
> > > 
> > 
> > Thanks Marvin,
> > I also made a test with the Ices2 configuration file:
> > 
> > <encode>
> > ????<bitrate>128</bitrate>
> > ????<samplerate>44100</samplerate>
> > ????<channels>2</channels>
> > </encode>
> > 
> > But the bitrate did not change.
> 
> AFAIK Ices2 does not re-encode therefore it is unable to change
> the bitrate.
> 
Then I should look for another source client. Do you know of anyone who
does ?.
Thanks.
> > > > 
> > > > But it seems that is not enough since the bitrate does not
> > > > change.
> > > > Receiving the stream with Rhythmbox,?after restart the server
> > > > the
> > > > bitrate is not 128 kbps.
> > > > If required, how should I set the Ices2 configuration file ?.
> > > > 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
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From jordan at coolmic.net  Wed Aug 23 16:52:40 2017
From: jordan at coolmic.net (Jordan Erickson)
Date: Wed, 23 Aug 2017 09:52:40 -0700
Subject: [Icecast] Change bitrate
In-Reply-To: <1503492651.1615.14.camel@speedy.com.ar>
References: <ojul1i$lu4$1@blaine.gmane.org>
 <1499685764.1836.3.camel@de.loewenfelsen.net>
 <1500655290.1748.5.camel@speedy.com.ar> <1500657006.2948.3.camel@gmail.com>
 <1500658061.2948.5.camel@speedy.com.ar> <1500659727.4083.0.camel@gmail.com>
 <1503490107.1615.6.camel@speedy.com.ar>
 <25AAE2C1-1547-4394-BC71-148B2EE52C8B@gmail.com>
 <1503492049.1615.11.camel@speedy.com.ar>
 <2CAE19E9-4915-44D2-8D83-85E67C25208C@gmail.com>
 <1503492651.1615.14.camel@speedy.com.ar>
Message-ID: <9c43b90a-44e8-cec1-9bea-9914d6da0fe7@coolmic.net>

Hi Jos?,

You can use Ices2 to accomplish this - take a look at the docs:

http://icecast.org/ices/docs/ices-2.0.2/config.html

(Specifically the <encode> section - looks like you were using some
incorrect parameters which would explain why it wasn't working).



Sincerely,
Jordan Erickson


On 08/23/2017 05:50 AM, Jos? Luis Artuch wrote:
> El mi?, 23-08-2017 a las 14:42 +0200, Marvin Scholz escribi?:
>>
>> On 23 Aug 2017, at 14:40, Jos? Luis Artuch wrote:
>>
>>> El mi?, 23-08-2017 a las 14:13 +0200, Marvin Scholz escribi?:
>>>>
>>>> On 23 Aug 2017, at 14:08, Jos? Luis Artuch wrote:
>>>>
>>>>> Hello, good morning !
>>>>> Running Icecast2 and Ices2 with live audio from Line IN, what
>>>>> is
>>>>> the
>>>>> correct way to change the bitrate ?.
>>>>> In the Icecast2 configuration file I set:
>>>>>
>>>>> <mount type="normal">
>>>>>     <mount-name>/entzun.opus</mount-name>
>>>>>     <bitrate>128</bitrate>
>>>>> </mount>
>>>>
>>>> This option should not be used and does not do what you expect it
>>>> does.
>>>> Icecast can't change the bitrate, the source client needs to do
>>>> that.
>>>>
>>>
>>> Thanks Marvin,
>>> I also made a test with the Ices2 configuration file:
>>>
>>> <encode>
>>>     <bitrate>128</bitrate>
>>>     <samplerate>44100</samplerate>
>>>     <channels>2</channels>
>>> </encode>
>>>
>>> But the bitrate did not change.
>>
>> AFAIK Ices2 does not re-encode therefore it is unable to change
>> the bitrate.
>>
> Then I should look for another source client. Do you know of anyone who
> does ?.
> Thanks.
>>>>>
>>>>> But it seems that is not enough since the bitrate does not
>>>>> change.
>>>>> Receiving the stream with Rhythmbox, after restart the server
>>>>> the
>>>>> bitrate is not 128 kbps.
>>>>> If required, how should I set the Ices2 configuration file ?.
>>>>> 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
>>
>> _______________________________________________
>> 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
> 

-- 
Jordan Erickson (PGP: 0x78DD41CB)
Logical Networking Solutions, 707-636-5678


From artuch at speedy.com.ar  Wed Aug 23 17:16:40 2017
From: artuch at speedy.com.ar (=?ISO-8859-1?Q?Jos=E9?= Luis Artuch)
Date: Wed, 23 Aug 2017 14:16:40 -0300
Subject: [Icecast] Change bitrate
In-Reply-To: <e743302e-64b9-a3c4-3877-3d7cccb9cdd4@logicalnetworking.net>
References: <ojul1i$lu4$1@blaine.gmane.org>
 <1499685764.1836.3.camel@de.loewenfelsen.net>
 <1500655290.1748.5.camel@speedy.com.ar> <1500657006.2948.3.camel@gmail.com>
 <1500658061.2948.5.camel@speedy.com.ar> <1500659727.4083.0.camel@gmail.com>
 <1503490107.1615.6.camel@speedy.com.ar>
 <25AAE2C1-1547-4394-BC71-148B2EE52C8B@gmail.com>
 <1503492049.1615.11.camel@speedy.com.ar>
 <2CAE19E9-4915-44D2-8D83-85E67C25208C@gmail.com>
 <1503492651.1615.14.camel@speedy.com.ar>
 <e743302e-64b9-a3c4-3877-3d7cccb9cdd4@logicalnetworking.net>
Message-ID: <1503508600.8269.2.camel@speedy.com.ar>

El mi?, 23-08-2017 a las 08:08 -0700, Jordan Erickson escribi?:
> Hi Jos?,
> 
> You can use Ices2 to accomplish this - take a look at the docs:
> 
> http://icecast.org/ices/docs/ices-2.0.2/config.html
> 
> (Specifically the <encode> section - looks like you were using some
> incorrect parameters which would explain why it wasn't working).
> 
> 
> 
> Sincerely,
> Jordan Erickson
> 
Thanks Jordan,
Exactly, I was already doing some tests with <encode> section into the
Ices2 configuration file, but I did not get the result sought.
I will do tests again, especially with <quality> and <nominal-bitrate>
Maybe I should not define both parameters at the same time.
I listen to radio stations with 64 kbps and good audio quality. I want
to achieve something similar by reducing the current bitrate to consume
a smaller amount of data.
Best regards.
Jos? Luis
> 
> On 08/23/2017 05:50 AM, Jos? Luis Artuch wrote:
> > El mi?, 23-08-2017 a las 14:42 +0200, Marvin Scholz escribi?:
> > > 
> > > On 23 Aug 2017, at 14:40, Jos? Luis Artuch wrote:
> > > 
> > > > El mi?, 23-08-2017 a las 14:13 +0200, Marvin Scholz escribi?:
> > > > > 
> > > > > On 23 Aug 2017, at 14:08, Jos? Luis Artuch wrote:
> > > > > 
> > > > > > Hello, good morning !
> > > > > > Running Icecast2 and Ices2 with live audio from Line IN,
> > > > > > what
> > > > > > is
> > > > > > the
> > > > > > correct way to change the bitrate ?.
> > > > > > In the Icecast2 configuration file I set:
> > > > > > 
> > > > > > <mount type="normal">
> > > > > > ????<mount-name>/entzun.opus</mount-name>
> > > > > > ????<bitrate>128</bitrate>
> > > > > > </mount>
> > > > > 
> > > > > This option should not be used and does not do what you
> > > > > expect it
> > > > > does.
> > > > > Icecast can't change the bitrate, the source client needs to
> > > > > do
> > > > > that.
> > > > > 
> > > > 
> > > > Thanks Marvin,
> > > > I also made a test with the Ices2 configuration file:
> > > > 
> > > > <encode>
> > > > ????<bitrate>128</bitrate>
> > > > ????<samplerate>44100</samplerate>
> > > > ????<channels>2</channels>
> > > > </encode>
> > > > 
> > > > But the bitrate did not change.
> > > 
> > > AFAIK Ices2 does not re-encode therefore it is unable to change
> > > the bitrate.
> > > 
> > 
> > Then I should look for another source client. Do you know of anyone
> > who
> > does ?.
> > Thanks.
> > > > > > 
> > > > > > But it seems that is not enough since the bitrate does not
> > > > > > change.
> > > > > > Receiving the stream with Rhythmbox, after restart the
> > > > > > server
> > > > > > the
> > > > > > bitrate is not 128 kbps.
> > > > > > If required, how should I set the Ices2 configuration file
> > > > > > ?.
> > > > > > 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
> > > 
> > > _______________________________________________
> > > 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 dennis at heerema.net  Wed Aug 23 17:35:14 2017
From: dennis at heerema.net (=?utf-8?Q?=44=65=6E=6E=69=73=20=48=65=65=72=65=6D=61?=)
Date: Wed, 23 Aug 2017 19:35:14 +0200
Subject: [Icecast] Change bitrate
Message-ID: <43b9e4fe-5d75-4bb0-92ee-8fd9673e7ea2@email.android.com>

An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20170823/5bc676e3/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 485 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20170823/5bc676e3/attachment.sig>

From artuch at speedy.com.ar  Wed Aug 23 18:03:25 2017
From: artuch at speedy.com.ar (=?ISO-8859-1?Q?Jos=E9?= Luis Artuch)
Date: Wed, 23 Aug 2017 15:03:25 -0300
Subject: [Icecast] Change bitrate
In-Reply-To: <43b9e4fe-5d75-4bb0-92ee-8fd9673e7ea2@email.android.com>
References: <43b9e4fe-5d75-4bb0-92ee-8fd9673e7ea2@email.android.com>
Message-ID: <1503511405.8269.5.camel@speedy.com.ar>

El mi?, 23-08-2017 a las 19:35 +0200, Dennis Heerema escribi?:
> Hello,
> 
> You can also take a look at liquidsoap, this tool van convert and
> invluence streams in many ways and is also opensource.
> 
> Kind regards,
> 
> Dennis
> 
Thanks Dennis,
I see that I can run Liquidsoap from the command line, then I will also
do some tests with this opensource tool.
Best regards.
Jos? Luis

> Op 23 aug. 2017 19:17 schreef "artuch at speedy.com.ar -- Jos? Luis
> Artuch" <artuch at speedy.com.ar>:
> El mi?, 23-08-2017 a las 08:08 -0700, Jordan Erickson escribi?:
> > Hi Jos?,
> >?
> > You can use Ices2 to accomplish this - take a look at the docs:
> >?
> > http://icecast.org/ices/docs/ices-2.0.2/config.html
> >?
> > (Specifically the??section - looks like you were using some
> > incorrect parameters which would explain why it wasn't working).
> >?
> >?
> >?
> > Sincerely,
> > Jordan Erickson
> >?
> Thanks Jordan,
> Exactly, I was already doing some tests with??section into the
> Ices2 configuration file, but I did not get the result sought.
> I will do tests again, especially with??and?
> Maybe I should not define both parameters at the same time.
> I listen to radio stations with 64 kbps and good audio quality. I
> want
> to achieve something similar by reducing the current bitrate to
> consume
> a smaller amount of data.
> Best regards.
> Jos? Luis
> >?
> > On 08/23/2017 05:50 AM, Jos? Luis Artuch wrote:
> > > El mi?, 23-08-2017 a las 14:42 +0200, Marvin Scholz escribi?:
> > > >?
> > > > On 23 Aug 2017, at 14:40, Jos? Luis Artuch wrote:
> > > >?
> > > > > El mi?, 23-08-2017 a las 14:13 +0200, Marvin Scholz escribi?:
> > > > > >?
> > > > > > On 23 Aug 2017, at 14:08, Jos? Luis Artuch wrote:
> > > > > >?
> > > > > > > Hello, good morning !
> > > > > > > Running Icecast2 and Ices2 with live audio from Line IN,
> > > > > > > what
> > > > > > > is
> > > > > > > the
> > > > > > > correct way to change the bitrate ?.
> > > > > > > In the Icecast2 configuration file I set:
> > > > > > >?
> > > > > > >?
> > > > > > > ????/entzun.opus
> > > > > > > ????128
> > > > > > >?
> > > > > >?
> > > > > > This option should not be used and does not do what you
> > > > > > expect it
> > > > > > does.
> > > > > > Icecast can't change the bitrate, the source client needs
> to
> > > > > > do
> > > > > > that.
> > > > > >?
> > > > >?
> > > > > Thanks Marvin,
> > > > > I also made a test with the Ices2 configuration file:
> > > > >?
> > > > >?
> > > > > ????128
> > > > > ????44100
> > > > > ????2
> > > > >?
> > > > >?
> > > > > But the bitrate did not change.
> > > >?
> > > > AFAIK Ices2 does not re-encode therefore it is unable to change
> > > > the bitrate.
> > > >?
> > >?
> > > Then I should look for another source client. Do you know of
> anyone
> > > who
> > > does ?.
> > > Thanks.
> > > > > > >?
> > > > > > > But it seems that is not enough since the bitrate does
> not
> > > > > > > change.
> > > > > > > Receiving the stream with Rhythmbox, after restart the
> > > > > > > server
> > > > > > > the
> > > > > > > bitrate is not 128 kbps.
> > > > > > > If required, how should I set the Ices2 configuration
> file
> > > > > > > ?.
> > > > > > > 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
> > > >?
> > > > _______________________________________________
> > > > 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
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From jeffares.robert at gmail.com  Wed Aug 23 20:16:26 2017
From: jeffares.robert at gmail.com (Robert Jeffares)
Date: Thu, 24 Aug 2017 08:16:26 +1200
Subject: [Icecast] Change bitrate
In-Reply-To: <1503492651.1615.14.camel@speedy.com.ar>
References: <ojul1i$lu4$1@blaine.gmane.org>
 <1499685764.1836.3.camel@de.loewenfelsen.net>
 <1500655290.1748.5.camel@speedy.com.ar> <1500657006.2948.3.camel@gmail.com>
 <1500658061.2948.5.camel@speedy.com.ar> <1500659727.4083.0.camel@gmail.com>
 <1503490107.1615.6.camel@speedy.com.ar>
 <25AAE2C1-1547-4394-BC71-148B2EE52C8B@gmail.com>
 <1503492049.1615.11.camel@speedy.com.ar>
 <2CAE19E9-4915-44D2-8D83-85E67C25208C@gmail.com>
 <1503492651.1615.14.camel@speedy.com.ar>
Message-ID: <8f4cebc4-413f-4e15-1ecd-7789a3fbaf40@gmail.com>



On 24/08/17 00:50, Jos? Luis Artuch wrote:
> Then I should look for another source client. Do you know of anyone who
> does ?.
> Thanks.
I use Darkice which can deliver streams in a number of formats and 
bitrates.
Works well with Icecast2

regards
Robert


From artuch at speedy.com.ar  Wed Aug 23 21:44:43 2017
From: artuch at speedy.com.ar (=?ISO-8859-1?Q?Jos=E9?= Luis Artuch)
Date: Wed, 23 Aug 2017 18:44:43 -0300
Subject: [Icecast] Change bitrate
In-Reply-To: <8f4cebc4-413f-4e15-1ecd-7789a3fbaf40@gmail.com>
References: <ojul1i$lu4$1@blaine.gmane.org>
 <1499685764.1836.3.camel@de.loewenfelsen.net>
 <1500655290.1748.5.camel@speedy.com.ar> <1500657006.2948.3.camel@gmail.com>
 <1500658061.2948.5.camel@speedy.com.ar> <1500659727.4083.0.camel@gmail.com>
 <1503490107.1615.6.camel@speedy.com.ar>
 <25AAE2C1-1547-4394-BC71-148B2EE52C8B@gmail.com>
 <1503492049.1615.11.camel@speedy.com.ar>
 <2CAE19E9-4915-44D2-8D83-85E67C25208C@gmail.com>
 <1503492651.1615.14.camel@speedy.com.ar>
 <8f4cebc4-413f-4e15-1ecd-7789a3fbaf40@gmail.com>
Message-ID: <1503524683.8269.23.camel@speedy.com.ar>

El jue, 24-08-2017 a las 08:16 +1200, Robert Jeffares escribi?:
> 
> On 24/08/17 00:50, Jos? Luis Artuch wrote:
> > Then I should look for another source client. Do you know of anyone
> > who
> > does ?.
> > Thanks.
> 
> I use Darkice which can deliver streams in a number of formats and?
> bitrates.
> Works well with Icecast2
> 
> regards
> Robert
Thank you Robert, another tool to do tests from the command line.
Scheduled for the weekend :)
Best regards.
Jos? Luis
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From WillR at rice.edu  Thu Aug 24 03:47:34 2017
From: WillR at rice.edu (Will Robedee)
Date: Wed, 23 Aug 2017 22:47:34 -0500
Subject: [Icecast] How to Rotate Logs Monthly (newbie question)
Message-ID: <047801d31c8b$b8651320$292f3960$@rice.edu>

I am having trouble getting icecast logs to rotate monthly.  
[] 
Any tips would be greatly appreciated.  

I am running Linux redhat with Icecast. 


Will R




From andy.speagle at wichita.edu  Fri Aug 25 16:49:39 2017
From: andy.speagle at wichita.edu (Speagle, Andy)
Date: Fri, 25 Aug 2017 16:49:39 +0000
Subject: [Icecast] SSL Cert Woes
Message-ID: <274cc42426c4484cbae6f986a7d82af3@mbxsvc-303.ad.wichita.edu>

Hi Folks,

I'm having a problem getting a the SSL cert file formatted just like icecast wants... I'm running 2.4.2 ... and it doesn't seem to want to use my combined key + cert chain no matter in what order I put it.  Presently, I have it in this format.. with spaces between each key/cert...

KEY

CERTCHAIN-1

CERTCHAIN-2

CERTCHAIN-3

MYCERT

And... well... not sure what else to do here.  I have the file owned by icecast:icecast ... and ... it should be readable in its present location... so, not sure what else would be wrong.

Thoughts?

Andy Speagle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20170825/f5ae0c64/attachment.htm>

From artuch at speedy.com.ar  Sun Aug 27 19:34:09 2017
From: artuch at speedy.com.ar (=?ISO-8859-1?Q?Jos=E9?= Luis Artuch)
Date: Sun, 27 Aug 2017 16:34:09 -0300
Subject: [Icecast] SSL Cert Woes
In-Reply-To: <274cc42426c4484cbae6f986a7d82af3@mbxsvc-303.ad.wichita.edu>
References: <274cc42426c4484cbae6f986a7d82af3@mbxsvc-303.ad.wichita.edu>
Message-ID: <1503862449.3606.2.camel@speedy.com.ar>

Good afternoon Andy,

El vie, 25-08-2017 a las 16:49 +0000, Speagle, Andy escribi?:
> Hi Folks,
> ?
> I?m having a problem getting a the SSL cert file formatted just like
> icecast wants? I?m running 2.4.2 ? and it doesn?t seem to want to use
> my combined key + cert chain no matter in what order I put it.?
> Presently, I have it in this format.. with spaces between each
> key/cert?
> ?
> KEY
> ?
> CERTCHAIN-1
> ?
> CERTCHAIN-2
> ?
> CERTCHAIN-3
> ?
> MYCERT
> ?
> And? well? not sure what else to do here.? I have the file owned by
> icecast:icecast ? and ? it should be readable in its present
> location? so, not sure what else would be wrong.
> ?
Firtsly, what operative system are you running ?. On Debian GNU/Linux
user icecast2 and group icecast, then icecast2:icecast.

Secondly, check the Icecast2's error.log looking about SSL or TLS
capability. On Debian GNU/Linux /var/log/icecast2/error.log.

Regards.
Jos? Luis
> Thoughts?
> ?
> Andy Speagle
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From erwin589 at gmail.com  Mon Aug 28 07:39:27 2017
From: erwin589 at gmail.com (Erwin Pannecoucke)
Date: Mon, 28 Aug 2017 09:39:27 +0200
Subject: [Icecast] Fallback stream not preventing a disconnect
Message-ID: <CAGwL=seb3SCMm3tcdCnusgHh3xGaoYzU25fiP0vzJV1eoZkz8g@mail.gmail.com>

Dear all,

I"m using a combination of mopidy, icecast2 and Home-Assistant on a
raspberry pi to stream Google music to a Chromecast Audio.

The streaming works and I can listen to music. If a new song is being
started, I keep connected. However, upon changing the song or pausing the
stream, the chromecast gets disconnected. I assumed that this should be
resolved by adding a fallback stream, but, unfortunatly, it doesn't. I
checked by adding a not-so-silent fallback file, and it appears that I'm
disconnected before I can hear the fallback song.

I've tryed it with streaming as ogg instead of mp3 (and thus also using a
silent ogg file), but it gives me exactly the same result. I have no idea
what I'm doing wrong, and have no idea how to continue. I tried really a
lot of stuff, but I seem te be stuck here for already quite some time. By
emailing this board, I was hoping if anybody in the community could help me
with this?


Home Assistant was configured using this explanation:

https://community.home-assistant.io/t/need-help-
> chromecast-audio-media-center-plex-kodi/12361/11
>

This is how my icecast.xml file looks like:

https://pastebin.com/se9s88kY

This is a log of me starting the mpd service, connecting with
home-assistant (and hearing music), followed by changing a track:


[2017-08-16  14:40:20] INFO connection/_handle_source_request Source
> logging in at mountpoint "/mopidy.mp3"

[2017-08-16  14:40:20] INFO source/source_startup sources count is now 1

[2017-08-16  14:40:20] INFO source/source_apply_mount Applying mount
> information for "/mopidy.mp3"

[2017-08-16  14:40:20] INFO source/source_startup source /mopidy.mp3 is
> ready to start

[2017-08-16  14:40:20] INFO source/source_set_override for /mopidy.mp3

[2017-08-16  14:40:20] INFO source/source_init Source /mopidy.mp3
> initialised

[2017-08-16  14:40:20] INFO source/source_read listener count on
> /mopidy.mp3 now 0

[2017-08-16  14:40:20] INFO admin/command_metadata Metadata song on
> /mopidy.mp3 set to "Unknown - Unknown"

[2017-08-16  14:40:20] INFO mpeg/check_for_mp3 MPEG 1 Layer 3 detected
> (44100, 2) on /mopidy.mp3

[2017-08-16  14:40:37] INFO source/source_add_listener max on /mopidy.mp3
> is -1 (cur 0)

[2017-08-16  14:40:37] INFO source/source_read listener count on
> /mopidy.mp3 now 1

[2017-08-16  14:40:45] INFO source/source_read End of Stream /mopidy.mp3

[2017-08-16  14:40:45] INFO source/source_shutdown Source "/mopidy.mp3"
> exiting

[2017-08-16  14:40:45] INFO source/source_set_fallback fallback set on
> /mopidy.mp3 to /silence.mp3(0) with 1 listeners

[2017-08-16  14:40:45] INFO source/source_client_read no more listeners on
> /mopidy.mp3

[2017-08-16  14:40:45] INFO source/_free_source freeing source "/mopidy.mp3"

[2017-08-16  14:40:46] INFO connection/_handle_source_request Source
> logging in at mountpoint "/mopidy.mp3"

[2017-08-16  14:40:46] INFO source/source_startup sources count is now 1

[2017-08-16  14:40:46] INFO source/source_apply_mount Applying mount
> information for "/mopidy.mp3"

[2017-08-16  14:40:46] INFO source/source_startup source /mopidy.mp3 is
> ready to start

[2017-08-16  14:40:46] INFO source/source_set_override for /mopidy.mp3

[2017-08-16  14:40:46] INFO source/source_init Source /mopidy.mp3
> initialised

[2017-08-16  14:40:46] INFO source/source_read listener count on
> /mopidy.mp3 now 0

[2017-08-16  14:40:46] INFO admin/command_metadata Metadata song on
> /mopidy.mp3 set to "Unknown - Unknown"

[2017-08-16  14:40:46] INFO admin/command_metadata Metadata song on
> /mopidy.mp3 set to "Unknown - Unknown"

[2017-08-16  14:40:46] INFO admin/command_metadata Metadata song on
> /mopidy.mp3 set to "Unknown - Unknown"

[2017-08-16  14:40:47] INFO mpeg/check_for_mp3 MPEG 1 Layer 3 detected
> (44100, 2) on /mopidy.mp3




One thing I noticed, is that somewere in this mailing list somebody
suggested that one should always see the fallback mountpoint in
/admin/listmounts.xsl. I however never ever see this.


If more information is needed, don't hesitate to ask.


Thanks you A LOT in advance,
Erwin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20170828/bffa4a3e/attachment.htm>

From lion at lion.leolix.org  Mon Aug 28 08:06:48 2017
From: lion at lion.leolix.org (Philipp Schafft)
Date: Mon, 28 Aug 2017 08:06:48 +0000
Subject: [Icecast] Fallback stream not preventing a disconnect
In-Reply-To: <CAGwL=seb3SCMm3tcdCnusgHh3xGaoYzU25fiP0vzJV1eoZkz8g@mail.gmail.com>
References: <CAGwL=seb3SCMm3tcdCnusgHh3xGaoYzU25fiP0vzJV1eoZkz8g@mail.gmail.com>
Message-ID: <1503907608.2157.15.camel@lion.leolix.org>

Good morning,

On Mon, 2017-08-28 at 09:39 +0200, Erwin Pannecoucke wrote:
> Dear all,
> 
> I"m using a combination of mopidy, icecast2 and Home-Assistant on a
> raspberry pi to stream Google music to a Chromecast Audio.

What exact software are you using. Your log file is not generated by
official Icecast2.


> [2017-08-16  14:40:20] INFO mpeg/check_for_mp3 MPEG 1 Layer 3 detected
> > (44100, 2) on /mopidy.mp3

No official version of Icecast2 can generate this message.


With best regards,

-- 
Philipp.
 (Rah of PH2)


From erwin589 at gmail.com  Mon Aug 28 08:36:15 2017
From: erwin589 at gmail.com (Erwin Pannecoucke)
Date: Mon, 28 Aug 2017 10:36:15 +0200
Subject: [Icecast] Fallback stream not preventing a disconnect
In-Reply-To: <1503907608.2157.15.camel@lion.leolix.org>
References: <CAGwL=seb3SCMm3tcdCnusgHh3xGaoYzU25fiP0vzJV1eoZkz8g@mail.gmail.com>
 <1503907608.2157.15.camel@lion.leolix.org>
Message-ID: <CAGwL=seqNUaTuTwAi6zjkMM0q_tRr=_iN7EDRr1wjC-_bWu00A@mail.gmail.com>

Dear Philipp,

Thanks for this fast answer.

I'm using "Icecast 2.3.3-kh7-20130425090916", installed on a Raspberry Pi 3
using the cononical "sudo apt-get install".

The output was copied from the log file in /var/log/icecast2/error.log.


Kind regards,
Erwin

2017-08-28 10:06 GMT+02:00 Philipp Schafft <lion at lion.leolix.org>:

> Good morning,
>
> On Mon, 2017-08-28 at 09:39 +0200, Erwin Pannecoucke wrote:
> > Dear all,
> >
> > I"m using a combination of mopidy, icecast2 and Home-Assistant on a
> > raspberry pi to stream Google music to a Chromecast Audio.
>
> What exact software are you using. Your log file is not generated by
> official Icecast2.
>
>
> > [2017-08-16  14:40:20] INFO mpeg/check_for_mp3 MPEG 1 Layer 3 detected
> > > (44100, 2) on /mopidy.mp3
>
> No official version of Icecast2 can generate this message.
>
>
> With best regards,
>
> --
> Philipp.
>  (Rah of PH2)
> _______________________________________________
> 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/20170828/57c62f85/attachment.htm>

From lion at lion.leolix.org  Mon Aug 28 08:41:31 2017
From: lion at lion.leolix.org (Philipp Schafft)
Date: Mon, 28 Aug 2017 08:41:31 +0000
Subject: [Icecast] Fallback stream not preventing a disconnect
In-Reply-To: <CAGwL=seqNUaTuTwAi6zjkMM0q_tRr=_iN7EDRr1wjC-_bWu00A@mail.gmail.com>
References: <CAGwL=seb3SCMm3tcdCnusgHh3xGaoYzU25fiP0vzJV1eoZkz8g@mail.gmail.com>
 <1503907608.2157.15.camel@lion.leolix.org>
 <CAGwL=seqNUaTuTwAi6zjkMM0q_tRr=_iN7EDRr1wjC-_bWu00A@mail.gmail.com>
Message-ID: <1503909691.2157.17.camel@lion.leolix.org>

Good morning,


On Mon, 2017-08-28 at 10:36 +0200, Erwin Pannecoucke wrote:
> Dear Philipp,
> 
> Thanks for this fast answer.
> 
> I'm using "Icecast 2.3.3-kh7-20130425090916", installed on a Raspberry Pi 3
> using the cononical "sudo apt-get install".
> 
> The output was copied from the log file in /var/log/icecast2/error.log.

Ok. That is a software from a different vendor (a fork).

Have you tried with official Icecast2?

You can also wait and see if any user of that software is on this ML
that can help you.

With best regards,

> 2017-08-28 10:06 GMT+02:00 Philipp Schafft <lion at lion.leolix.org>:
> > On Mon, 2017-08-28 at 09:39 +0200, Erwin Pannecoucke wrote:
> > > I"m using a combination of mopidy, icecast2 and Home-Assistant on a
> > > raspberry pi to stream Google music to a Chromecast Audio.
> >
> > What exact software are you using. Your log file is not generated by
> > official Icecast2.
> >
> >
> > > [2017-08-16  14:40:20] INFO mpeg/check_for_mp3 MPEG 1 Layer 3 detected
> > > > (44100, 2) on /mopidy.mp3
> >
> > No official version of Icecast2 can generate this message.

-- 
Philipp.
 (Rah of PH2)


From andy.speagle at wichita.edu  Mon Aug 28 13:46:58 2017
From: andy.speagle at wichita.edu (Speagle, Andy)
Date: Mon, 28 Aug 2017 13:46:58 +0000
Subject: [Icecast] SSL Cert Woes
Message-ID: <e005224e3984463fa5b2525e5d7e8567@mbxsvc-303.ad.wichita.edu>

> El vie, 25-08-2017 a las 16:49 +0000, Speagle, Andy escribi?:
> > Hi Folks,
> >
> > I?m having a problem getting a the SSL cert file formatted just like
> > icecast wants? I?m running 2.4.2 ? and it doesn?t seem to want to use
> > my combined key + cert chain no matter in what order I put it.
> > Presently, I have it in this format.. with spaces between each
> > key/cert?
> >
> > KEY
> >
> > CERTCHAIN-1
> >
> > CERTCHAIN-2
> >
> > CERTCHAIN-3
> >
> > MYCERT
> >
> > And? well? not sure what else to do here.? I have the file owned by
> > icecast:icecast ? and ? it should be readable in its present location?
> > so, not sure what else would be wrong.
> >
> Firtsly, what operative system are you running ?. On Debian GNU/Linux user
> icecast2 and group icecast, then icecast2:icecast.

I'm on RHEL 7, so the user/group is icecast:icecast ... 

> Secondly, check the Icecast2's error.log looking about SSL or TLS capability.
> On Debian GNU/Linux /var/log/icecast2/error.log.

From the log, I get a simple: 

WARN connection/get_ssl_certificate Invalid cert file <my cert filepath>
INFO connection/get_ssl_certificate No SSL capability on any configured ports

So... not sure what else I can do here... using simple openssl verify commands I can see that the cert chain is valid... 

Thanks!


From artuch at speedy.com.ar  Mon Aug 28 17:56:31 2017
From: artuch at speedy.com.ar (=?ISO-8859-1?Q?Jos=E9?= Luis Artuch)
Date: Mon, 28 Aug 2017 14:56:31 -0300
Subject: [Icecast] SSL Cert Woes
In-Reply-To: <e005224e3984463fa5b2525e5d7e8567@mbxsvc-303.ad.wichita.edu>
References: <e005224e3984463fa5b2525e5d7e8567@mbxsvc-303.ad.wichita.edu>
Message-ID: <1503942991.1803.2.camel@speedy.com.ar>

"Speagle, Andy" <andy.speagle at wichita.edu>Hi Andy,
El lun, 28-08-2017 a las 13:46 +0000, Speagle, Andy escribi?:
> > El vie, 25-08-2017 a las 16:49 +0000, Speagle, Andy escribi?:
> > > Hi Folks,
> > > 
> > > I?m having a problem getting a the SSL cert file formatted just
> > > like
> > > icecast wants? I?m running 2.4.2 ? and it doesn?t seem to want to
> > > use
> > > my combined key + cert chain no matter in what order I put it.
> > > Presently, I have it in this format.. with spaces between each
> > > key/cert?
> > > 
> > > KEY
> > > 
> > > CERTCHAIN-1
> > > 
> > > CERTCHAIN-2
> > > 
> > > CERTCHAIN-3
> > > 
> > > MYCERT
> > > 
> > > And? well? not sure what else to do here.? I have the file owned
> > > by
> > > icecast:icecast ? and ? it should be readable in its present
> > > location?
> > > so, not sure what else would be wrong.
> > > 
> > 
> > Firtsly, what operative system are you running ?. On Debian
> > GNU/Linux user
> > icecast2 and group icecast, then icecast2:icecast.
> 
> I'm on RHEL 7, so the user/group is icecast:icecast ...?
> 
> > Secondly, check the Icecast2's error.log looking about SSL or TLS
> > capability.
> > On Debian GNU/Linux /var/log/icecast2/error.log.
> 
> From the log, I get a simple:?
> 
> WARN connection/get_ssl_certificate Invalid cert file <my cert
> filepath>
> INFO connection/get_ssl_certificate No SSL capability on any
> configured ports
> 
Make sure you have set up Icecast correctly:

<listen-socket>
	<port>8443</port>
	<ssl>1</ssl>
</listen-socket>
...
<paths>
	...
	<ssl-certificate>/usr/share/icecast2/icecast.pem</ssl-
certificate>
</paths>

Also, there is the possibility that Icecast2 package does not support
encrypted connections via openssl.
In my case I saw something similar to this:
[2017-08-08??03:05:34] INFO connection/get_ssl_certificate No SSL
capability
Then, like solution I should have compiled Icecast with openssl support
enabled.

Regards.
Jos? Luis
> So... not sure what else I can do here... using simple openssl verify
> commands I can see that the cert chain is valid...?
> 
> Thanks!
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From andy.speagle at wichita.edu  Mon Aug 28 19:05:11 2017
From: andy.speagle at wichita.edu (Speagle, Andy)
Date: Mon, 28 Aug 2017 19:05:11 +0000
Subject: [Icecast] SSL Cert Woes
In-Reply-To: <1503942991.1803.2.camel@speedy.com.ar>
References: <e005224e3984463fa5b2525e5d7e8567@mbxsvc-303.ad.wichita.edu>
 <1503942991.1803.2.camel@speedy.com.ar>
Message-ID: <cac8a30fad5e4d1b8ebd0710fff16956@mbxsvc-303.ad.wichita.edu>

> > > > Hi Folks,
> > > >
> > > > I?m having a problem getting a the SSL cert file formatted just
> > > > like icecast wants? I?m running 2.4.2 ? and it doesn?t seem to
> > > > want to use my combined key + cert chain no matter in what order I
> > > > put it.
> > > > Presently, I have it in this format.. with spaces between each
> > > > key/cert?
> > > >
> > > > KEY
> > > >
> > > > CERTCHAIN-1
> > > >
> > > > CERTCHAIN-2
> > > >
> > > > CERTCHAIN-3
> > > >
> > > > MYCERT
> > > >
> > > > And? well? not sure what else to do here.? I have the file owned
> > > > by icecast:icecast ? and ? it should be readable in its present
> > > > location? so, not sure what else would be wrong.
> > > >
> > >
> > > Firtsly, what operative system are you running ?. On Debian
> > > GNU/Linux user
> > > icecast2 and group icecast, then icecast2:icecast.
> >
> > I'm on RHEL 7, so the user/group is icecast:icecast ...
> >
> > > Secondly, check the Icecast2's error.log looking about SSL or TLS
> > > capability.
> > > On Debian GNU/Linux /var/log/icecast2/error.log.
> >
> > From the log, I get a simple:
> >
> > WARN connection/get_ssl_certificate Invalid cert file <my cert
> > filepath>
> > INFO connection/get_ssl_certificate No SSL capability on any
> > configured ports
> >
> Make sure you have set up Icecast correctly:
> 
> <listen-socket>
> 	<port>8443</port>
> 	<ssl>1</ssl>
> </listen-socket>

Yeah... it's setup properly...

> <paths>
> 	...
> 	<ssl-certificate>/usr/share/icecast2/icecast.pem</ssl-
> certificate>
> </paths>

Yes... correct for me.

> Also, there is the possibility that Icecast2 package does not support
> encrypted connections via openssl.
> In my case I saw something similar to this:
> [2017-08-08??03:05:34] INFO connection/get_ssl_certificate No SSL capability
> Then, like solution I should have compiled Icecast with openssl support
> enabled.

Well... I believe it to be setup correctly... the RPM has a libssl requirement... and the fact that it tries to check the SSL cert file indicates that it has capability... 

From artuch at speedy.com.ar  Mon Aug 28 19:25:19 2017
From: artuch at speedy.com.ar (=?ISO-8859-1?Q?Jos=E9?= Luis Artuch)
Date: Mon, 28 Aug 2017 16:25:19 -0300
Subject: [Icecast] SSL Cert Woes
In-Reply-To: <cac8a30fad5e4d1b8ebd0710fff16956@mbxsvc-303.ad.wichita.edu>
References: <e005224e3984463fa5b2525e5d7e8567@mbxsvc-303.ad.wichita.edu>
 <1503942991.1803.2.camel@speedy.com.ar>
 <cac8a30fad5e4d1b8ebd0710fff16956@mbxsvc-303.ad.wichita.edu>
Message-ID: <1503948319.1487.2.camel@speedy.com.ar>

Hi Andy,
El lun, 28-08-2017 a las 19:05 +0000, Speagle, Andy escribi?:
> > > > > Hi Folks,
> > > > > 
> > > > > I?m having a problem getting a the SSL cert file formatted
> > > > > just
> > > > > like icecast wants? I?m running 2.4.2 ? and it doesn?t seem
> > > > > to
> > > > > want to use my combined key + cert chain no matter in what
> > > > > order I
> > > > > put it.
> > > > > Presently, I have it in this format.. with spaces between
> > > > > each
> > > > > key/cert?
> > > > > 
> > > > > KEY
> > > > > 
> > > > > CERTCHAIN-1
> > > > > 
> > > > > CERTCHAIN-2
> > > > > 
> > > > > CERTCHAIN-3
> > > > > 
> > > > > MYCERT
> > > > > 
> > > > > And? well? not sure what else to do here.? I have the file
> > > > > owned
> > > > > by icecast:icecast ? and ? it should be readable in its
> > > > > present
> > > > > location? so, not sure what else would be wrong.
> > > > > 
> > > > 
> > > > Firtsly, what operative system are you running ?. On Debian
> > > > GNU/Linux user
> > > > icecast2 and group icecast, then icecast2:icecast.
> > > 
> > > I'm on RHEL 7, so the user/group is icecast:icecast ...
> > > 
> > > > Secondly, check the Icecast2's error.log looking about SSL or
> > > > TLS
> > > > capability.
> > > > On Debian GNU/Linux /var/log/icecast2/error.log.
> > > 
> > > From the log, I get a simple:
> > > 
> > > WARN connection/get_ssl_certificate Invalid cert file <my cert
> > > filepath>
> > > INFO connection/get_ssl_certificate No SSL capability on any
> > > configured ports
> > > 
> > 
> > Make sure you have set up Icecast correctly:
> > 
> > <listen-socket>
> > 	<port>8443</port>
> > 	<ssl>1</ssl>
> > </listen-socket>
> 
> Yeah... it's setup properly...
> 
> > <paths>
> > 	...
> > 	<ssl-certificate>/usr/share/icecast2/icecast.pem</ssl-
> > certificate>
> > </paths>
> 
> Yes... correct for me.
> 
> > Also, there is the possibility that Icecast2 package does not
> > support
> > encrypted connections via openssl.
> > In my case I saw something similar to this:
> > [2017-08-08??03:05:34] INFO connection/get_ssl_certificate No SSL
> > capability
> > Then, like solution I should have compiled Icecast with openssl
> > support
> > enabled.
> 
> Well... I believe it to be setup correctly... the RPM has a libssl
> requirement... and the fact that it tries to check the SSL cert file
> indicates that it has capability...?
I agree.
I generated the certificate with:
openssl req -x509 -nodes -days 1095 -newkey rsa:2048 -keyout
/usr/share/icecast2/icecast.pem -out /usr/share/icecast2/icecast.pem
Then you need only change owner and group, nothing more.



From andy.speagle at wichita.edu  Mon Aug 28 20:23:04 2017
From: andy.speagle at wichita.edu (Speagle, Andy)
Date: Mon, 28 Aug 2017 20:23:04 +0000
Subject: [Icecast] SSL Cert Woes
In-Reply-To: <1503948319.1487.2.camel@speedy.com.ar>
References: <e005224e3984463fa5b2525e5d7e8567@mbxsvc-303.ad.wichita.edu>
 <1503942991.1803.2.camel@speedy.com.ar>
 <cac8a30fad5e4d1b8ebd0710fff16956@mbxsvc-303.ad.wichita.edu>
 <1503948319.1487.2.camel@speedy.com.ar>
Message-ID: <41b9937880544d6bb45ea38c6afcaa2b@mbxsvc-303.ad.wichita.edu>

> > > > > > Hi Folks,
> > > > > >
> > > > > > I?m having a problem getting a the SSL cert file formatted
> > > > > > just like icecast wants? I?m running 2.4.2 ? and it doesn?t
> > > > > > seem to want to use my combined key + cert chain no matter in
> > > > > > what order I put it.
> > > > > > Presently, I have it in this format.. with spaces between each
> > > > > > key/cert?
> > > > > >
> > > > > > KEY
> > > > > >
> > > > > > CERTCHAIN-1
> > > > > >
> > > > > > CERTCHAIN-2
> > > > > >
> > > > > > CERTCHAIN-3
> > > > > >
> > > > > > MYCERT
> > > > > >
> > > > > > And? well? not sure what else to do here.? I have the file
> > > > > > owned by icecast:icecast ? and ? it should be readable in its
> > > > > > present location? so, not sure what else would be wrong.
> > > > > >
> > > > >
> > > > > Firtsly, what operative system are you running ?. On Debian
> > > > > GNU/Linux user
> > > > > icecast2 and group icecast, then icecast2:icecast.
> > > >
> > > > I'm on RHEL 7, so the user/group is icecast:icecast ...
> > > >
> > > > > Secondly, check the Icecast2's error.log looking about SSL or
> > > > > TLS capability.
> > > > > On Debian GNU/Linux /var/log/icecast2/error.log.
> > > >
> > > > From the log, I get a simple:
> > > >
> > > > WARN connection/get_ssl_certificate Invalid cert file <my cert
> > > > filepath>
> > > > INFO connection/get_ssl_certificate No SSL capability on any
> > > > configured ports
> > > >
> > >
> > > Make sure you have set up Icecast correctly:
> > >
> > > <listen-socket>
> > > 	<port>8443</port>
> > > 	<ssl>1</ssl>
> > > </listen-socket>
> >
> > Yeah... it's setup properly...
> >
> > > <paths>
> > > 	...
> > > 	<ssl-certificate>/usr/share/icecast2/icecast.pem</ssl-
> > > certificate>
> > > </paths>
> >
> > Yes... correct for me.
> >
> > > Also, there is the possibility that Icecast2 package does not
> > > support encrypted connections via openssl.
> > > In my case I saw something similar to this:
> > > [2017-08-08??03:05:34] INFO connection/get_ssl_certificate No SSL
> > > capability Then, like solution I should have compiled Icecast with
> > > openssl support enabled.
> >
> > Well... I believe it to be setup correctly... the RPM has a libssl
> > requirement... and the fact that it tries to check the SSL cert file
> > indicates that it has capability...
> I agree.
> I generated the certificate with:
> openssl req -x509 -nodes -days 1095 -newkey rsa:2048 -keyout
> /usr/share/icecast2/icecast.pem -out /usr/share/icecast2/icecast.pem Then
> you need only change owner and group, nothing more.

Well... I was able to get it to work with a self-signed cert... so, something must be up with my Starfield signed cert... looks like they're configuring certs using "Subject Alternative Name" entries by default... could that be causing Icecast to barf on the cert?

Also... I setup another <listen-socket> entry for SSL... but Icecast doesn't seem to want to listen on that port when the service comes up.  Any idea why that might be?


From jordan at coolmic.net  Mon Aug 28 21:08:34 2017
From: jordan at coolmic.net (Jordan Erickson)
Date: Mon, 28 Aug 2017 14:08:34 -0700
Subject: [Icecast] SSL Cert Woes
In-Reply-To: <41b9937880544d6bb45ea38c6afcaa2b@mbxsvc-303.ad.wichita.edu>
References: <e005224e3984463fa5b2525e5d7e8567@mbxsvc-303.ad.wichita.edu>
 <1503942991.1803.2.camel@speedy.com.ar>
 <cac8a30fad5e4d1b8ebd0710fff16956@mbxsvc-303.ad.wichita.edu>
 <1503948319.1487.2.camel@speedy.com.ar>
 <41b9937880544d6bb45ea38c6afcaa2b@mbxsvc-303.ad.wichita.edu>
Message-ID: <4278fbc0-819a-5e5b-14b7-721870113da8@coolmic.net>

On 08/28/2017 01:23 PM, Speagle, Andy wrote:
*bigsnip*
> Also... I setup another <listen-socket> entry for SSL... but Icecast doesn't seem to want to listen on that port when the service comes up.  Any idea why that might be?

What port are you using? If < 1024 (such as 443) you must first run as a
privileged user (like root) and then <changeowner> as described here:

http://icecast.org/docs/icecast-2.4.1/config-file.html#security

If that is not the case, please give log output.


Cheers,
Jordan


From artuch at speedy.com.ar  Mon Aug 28 21:13:41 2017
From: artuch at speedy.com.ar (=?ISO-8859-1?Q?Jos=E9?= Luis Artuch)
Date: Mon, 28 Aug 2017 18:13:41 -0300
Subject: [Icecast] SSL Cert Woes
In-Reply-To: <41b9937880544d6bb45ea38c6afcaa2b@mbxsvc-303.ad.wichita.edu>
References: <e005224e3984463fa5b2525e5d7e8567@mbxsvc-303.ad.wichita.edu>
 <1503942991.1803.2.camel@speedy.com.ar>
 <cac8a30fad5e4d1b8ebd0710fff16956@mbxsvc-303.ad.wichita.edu>
 <1503948319.1487.2.camel@speedy.com.ar>
 <41b9937880544d6bb45ea38c6afcaa2b@mbxsvc-303.ad.wichita.edu>
Message-ID: <1503954821.1487.5.camel@speedy.com.ar>

El lun, 28-08-2017 a las 20:23 +0000, Speagle, Andy escribi?:
> > > > > > > Hi Folks,
> > > > > > > 
> > > > > > > I?m having a problem getting a the SSL cert file
> > > > > > > formatted
> > > > > > > just like icecast wants? I?m running 2.4.2 ? and it
> > > > > > > doesn?t
> > > > > > > seem to want to use my combined key + cert chain no
> > > > > > > matter in
> > > > > > > what order I put it.
> > > > > > > Presently, I have it in this format.. with spaces between
> > > > > > > each
> > > > > > > key/cert?
> > > > > > > 
> > > > > > > KEY
> > > > > > > 
> > > > > > > CERTCHAIN-1
> > > > > > > 
> > > > > > > CERTCHAIN-2
> > > > > > > 
> > > > > > > CERTCHAIN-3
> > > > > > > 
> > > > > > > MYCERT
> > > > > > > 
> > > > > > > And? well? not sure what else to do here.? I have the
> > > > > > > file
> > > > > > > owned by icecast:icecast ? and ? it should be readable in
> > > > > > > its
> > > > > > > present location? so, not sure what else would be wrong.
> > > > > > > 
> > > > > > 
> > > > > > Firtsly, what operative system are you running ?. On Debian
> > > > > > GNU/Linux user
> > > > > > icecast2 and group icecast, then icecast2:icecast.
> > > > > 
> > > > > I'm on RHEL 7, so the user/group is icecast:icecast ...
> > > > > 
> > > > > > Secondly, check the Icecast2's error.log looking about SSL
> > > > > > or
> > > > > > TLS capability.
> > > > > > On Debian GNU/Linux /var/log/icecast2/error.log.
> > > > > 
> > > > > From the log, I get a simple:
> > > > > 
> > > > > WARN connection/get_ssl_certificate Invalid cert file <my
> > > > > cert
> > > > > filepath>
> > > > > INFO connection/get_ssl_certificate No SSL capability on any
> > > > > configured ports
> > > > > 
> > > > 
> > > > Make sure you have set up Icecast correctly:
> > > > 
> > > > <listen-socket>
> > > > 	<port>8443</port>
> > > > 	<ssl>1</ssl>
> > > > </listen-socket>
> > > 
> > > Yeah... it's setup properly...
> > > 
> > > > <paths>
> > > > 	...
> > > > 	<ssl-certificate>/usr/share/icecast2/icecast.pem</ssl-
> > > > certificate>
> > > > </paths>
> > > 
> > > Yes... correct for me.
> > > 
> > > > Also, there is the possibility that Icecast2 package does not
> > > > support encrypted connections via openssl.
> > > > In my case I saw something similar to this:
> > > > [2017-08-08??03:05:34] INFO connection/get_ssl_certificate No
> > > > SSL
> > > > capability Then, like solution I should have compiled Icecast
> > > > with
> > > > openssl support enabled.
> > > 
> > > Well... I believe it to be setup correctly... the RPM has a
> > > libssl
> > > requirement... and the fact that it tries to check the SSL cert
> > > file
> > > indicates that it has capability...
> > 
> > I agree.
> > I generated the certificate with:
> > openssl req -x509 -nodes -days 1095 -newkey rsa:2048 -keyout
> > /usr/share/icecast2/icecast.pem -out
> > /usr/share/icecast2/icecast.pem Then
> > you need only change owner and group, nothing more.
> 
> Well... I was able to get it to work with a self-signed cert... so,
> something must be up with my Starfield signed cert... looks like
> they're configuring certs using "Subject Alternative Name" entries by
> default... could that be causing Icecast to barf on the cert?
> 
Looks like something about the configuration of the certificate, but I
do not specifically what ... I have only done tests with self-signed
certificates.
The format should be:
-----BEGIN PRIVATE KEY-----
blablabla
-----END PRIVATE KEY-----
-----BEGIN CERTIFICATE-----
blablabla
-----END CERTIFICATE-----
> Also... I setup another <listen-socket> entry for SSL... but Icecast
> doesn't seem to want to listen on that port when the service comes
> up.??Any idea why that might be?
> 
Do you mean with different port than 8443, by exemple 8765 ?. If so,
what is the output of:
netstat -tulpn | grep ':8765'



From andy.speagle at wichita.edu  Mon Aug 28 21:37:43 2017
From: andy.speagle at wichita.edu (Speagle, Andy)
Date: Mon, 28 Aug 2017 21:37:43 +0000
Subject: [Icecast] SSL Cert Woes
In-Reply-To: <1503954821.1487.5.camel@speedy.com.ar>
References: <e005224e3984463fa5b2525e5d7e8567@mbxsvc-303.ad.wichita.edu>
 <1503942991.1803.2.camel@speedy.com.ar>
 <cac8a30fad5e4d1b8ebd0710fff16956@mbxsvc-303.ad.wichita.edu>
 <1503948319.1487.2.camel@speedy.com.ar>
 <41b9937880544d6bb45ea38c6afcaa2b@mbxsvc-303.ad.wichita.edu>
 <1503954821.1487.5.camel@speedy.com.ar>
Message-ID: <4aa24d784fea47e090565fa4eb7cc7d0@mbxsvc-303.ad.wichita.edu>

> > > > > > > > Hi Folks,
> > > > > > > >
> > > > > > > > I?m having a problem getting a the SSL cert file formatted
> > > > > > > > just like icecast wants? I?m running 2.4.2 ? and it
> > > > > > > > doesn?t seem to want to use my combined key + cert chain
> > > > > > > > no matter in what order I put it.
> > > > > > > > Presently, I have it in this format.. with spaces between
> > > > > > > > each key/cert?
> > > > > > > >
> > > > > > > > KEY
> > > > > > > >
> > > > > > > > CERTCHAIN-1
> > > > > > > >
> > > > > > > > CERTCHAIN-2
> > > > > > > >
> > > > > > > > CERTCHAIN-3
> > > > > > > >
> > > > > > > > MYCERT
> > > > > > > >
> > > > > > > > And? well? not sure what else to do here.? I have the file
> > > > > > > > owned by icecast:icecast ? and ? it should be readable in
> > > > > > > > its present location? so, not sure what else would be
> > > > > > > > wrong.
> > > > > > > >
> > > > > > >
> > > > > > > Firtsly, what operative system are you running ?. On Debian
> > > > > > > GNU/Linux user
> > > > > > > icecast2 and group icecast, then icecast2:icecast.
> > > > > >
> > > > > > I'm on RHEL 7, so the user/group is icecast:icecast ...
> > > > > >
> > > > > > > Secondly, check the Icecast2's error.log looking about SSL
> > > > > > > or TLS capability.
> > > > > > > On Debian GNU/Linux /var/log/icecast2/error.log.
> > > > > >
> > > > > > From the log, I get a simple:
> > > > > >
> > > > > > WARN connection/get_ssl_certificate Invalid cert file <my cert
> > > > > > filepath>
> > > > > > INFO connection/get_ssl_certificate No SSL capability on any
> > > > > > configured ports
> > > > > >
> > > > >
> > > > > Make sure you have set up Icecast correctly:
> > > > >
> > > > > <listen-socket>
> > > > > 	<port>8443</port>
> > > > > 	<ssl>1</ssl>
> > > > > </listen-socket>
> > > >
> > > > Yeah... it's setup properly...
> > > >
> > > > > <paths>
> > > > > 	...
> > > > > 	<ssl-certificate>/usr/share/icecast2/icecast.pem</ssl-
> > > > > certificate>
> > > > > </paths>
> > > >
> > > > Yes... correct for me.
> > > >
> > > > > Also, there is the possibility that Icecast2 package does not
> > > > > support encrypted connections via openssl.
> > > > > In my case I saw something similar to this:
> > > > > [2017-08-08??03:05:34] INFO connection/get_ssl_certificate No
> > > > > SSL capability Then, like solution I should have compiled
> > > > > Icecast with openssl support enabled.
> > > >
> > > > Well... I believe it to be setup correctly... the RPM has a libssl
> > > > requirement... and the fact that it tries to check the SSL cert
> > > > file indicates that it has capability...
> > >
> > > I agree.
> > > I generated the certificate with:
> > > openssl req -x509 -nodes -days 1095 -newkey rsa:2048 -keyout
> > > /usr/share/icecast2/icecast.pem -out /usr/share/icecast2/icecast.pem
> > > Then you need only change owner and group, nothing more.
> >
> > Well... I was able to get it to work with a self-signed cert... so,
> > something must be up with my Starfield signed cert... looks like
> > they're configuring certs using "Subject Alternative Name" entries by
> > default... could that be causing Icecast to barf on the cert?
> >
> Looks like something about the configuration of the certificate, but I do not
> specifically what ... I have only done tests with self-signed certificates.
> The format should be:
> -----BEGIN PRIVATE KEY-----
> blablabla
> -----END PRIVATE KEY-----
> -----BEGIN CERTIFICATE-----
> blablabla
> -----END CERTIFICATE-----
> > Also... I setup another <listen-socket> entry for SSL... but Icecast
> > doesn't seem to want to listen on that port when the service comes up.
> > Any idea why that might be?
> >
> Do you mean with different port than 8443, by exemple 8765 ?. If so, what is
> the output of:
> netstat -tulpn | grep ':8765'

Yeah... I?m just trying 8443 ... and netstat shows nada for 8443 ... very strange.


From artuch at speedy.com.ar  Mon Aug 28 21:52:22 2017
From: artuch at speedy.com.ar (=?ISO-8859-1?Q?Jos=E9?= Luis Artuch)
Date: Mon, 28 Aug 2017 18:52:22 -0300
Subject: [Icecast] SSL Cert Woes
In-Reply-To: <4aa24d784fea47e090565fa4eb7cc7d0@mbxsvc-303.ad.wichita.edu>
References: <e005224e3984463fa5b2525e5d7e8567@mbxsvc-303.ad.wichita.edu>
 <1503942991.1803.2.camel@speedy.com.ar>
 <cac8a30fad5e4d1b8ebd0710fff16956@mbxsvc-303.ad.wichita.edu>
 <1503948319.1487.2.camel@speedy.com.ar>
 <41b9937880544d6bb45ea38c6afcaa2b@mbxsvc-303.ad.wichita.edu>
 <1503954821.1487.5.camel@speedy.com.ar>
 <4aa24d784fea47e090565fa4eb7cc7d0@mbxsvc-303.ad.wichita.edu>
Message-ID: <1503957142.1487.6.camel@speedy.com.ar>

El lun, 28-08-2017 a las 21:37 +0000, Speagle, Andy escribi?:
> > > > > > > > > Hi Folks,
> > > > > > > > > 
> > > > > > > > > I?m having a problem getting a the SSL cert file
> > > > > > > > > formatted
> > > > > > > > > just like icecast wants? I?m running 2.4.2 ? and it
> > > > > > > > > doesn?t seem to want to use my combined key + cert
> > > > > > > > > chain
> > > > > > > > > no matter in what order I put it.
> > > > > > > > > Presently, I have it in this format.. with spaces
> > > > > > > > > between
> > > > > > > > > each key/cert?
> > > > > > > > > 
> > > > > > > > > KEY
> > > > > > > > > 
> > > > > > > > > CERTCHAIN-1
> > > > > > > > > 
> > > > > > > > > CERTCHAIN-2
> > > > > > > > > 
> > > > > > > > > CERTCHAIN-3
> > > > > > > > > 
> > > > > > > > > MYCERT
> > > > > > > > > 
> > > > > > > > > And? well? not sure what else to do here.? I have the
> > > > > > > > > file
> > > > > > > > > owned by icecast:icecast ? and ? it should be
> > > > > > > > > readable in
> > > > > > > > > its present location? so, not sure what else would be
> > > > > > > > > wrong.
> > > > > > > > > 
> > > > > > > > 
> > > > > > > > Firtsly, what operative system are you running ?. On
> > > > > > > > Debian
> > > > > > > > GNU/Linux user
> > > > > > > > icecast2 and group icecast, then icecast2:icecast.
> > > > > > > 
> > > > > > > I'm on RHEL 7, so the user/group is icecast:icecast ...
> > > > > > > 
> > > > > > > > Secondly, check the Icecast2's error.log looking about
> > > > > > > > SSL
> > > > > > > > or TLS capability.
> > > > > > > > On Debian GNU/Linux /var/log/icecast2/error.log.
> > > > > > > 
> > > > > > > From the log, I get a simple:
> > > > > > > 
> > > > > > > WARN connection/get_ssl_certificate Invalid cert file <my
> > > > > > > cert
> > > > > > > filepath>
> > > > > > > INFO connection/get_ssl_certificate No SSL capability on
> > > > > > > any
> > > > > > > configured ports
> > > > > > > 
> > > > > > 
> > > > > > Make sure you have set up Icecast correctly:
> > > > > > 
> > > > > > <listen-socket>
> > > > > > 	<port>8443</port>
> > > > > > 	<ssl>1</ssl>
> > > > > > </listen-socket>
> > > > > 
> > > > > Yeah... it's setup properly...
> > > > > 
> > > > > > <paths>
> > > > > > 	...
> > > > > > 	<ssl-certificate>/usr/share/icecast2/icecast.pem</ssl-
> > > > > > certificate>
> > > > > > </paths>
> > > > > 
> > > > > Yes... correct for me.
> > > > > 
> > > > > > Also, there is the possibility that Icecast2 package does
> > > > > > not
> > > > > > support encrypted connections via openssl.
> > > > > > In my case I saw something similar to this:
> > > > > > [2017-08-08??03:05:34] INFO connection/get_ssl_certificate
> > > > > > No
> > > > > > SSL capability Then, like solution I should have compiled
> > > > > > Icecast with openssl support enabled.
> > > > > 
> > > > > Well... I believe it to be setup correctly... the RPM has a
> > > > > libssl
> > > > > requirement... and the fact that it tries to check the SSL
> > > > > cert
> > > > > file indicates that it has capability...
> > > > 
> > > > I agree.
> > > > I generated the certificate with:
> > > > openssl req -x509 -nodes -days 1095 -newkey rsa:2048 -keyout
> > > > /usr/share/icecast2/icecast.pem -out
> > > > /usr/share/icecast2/icecast.pem
> > > > Then you need only change owner and group, nothing more.
> > > 
> > > Well... I was able to get it to work with a self-signed cert...
> > > so,
> > > something must be up with my Starfield signed cert... looks like
> > > they're configuring certs using "Subject Alternative Name"
> > > entries by
> > > default... could that be causing Icecast to barf on the cert?
> > > 
> > 
> > Looks like something about the configuration of the certificate,
> > but I do not
> > specifically what ... I have only done tests with self-signed
> > certificates.
> > The format should be:
> > -----BEGIN PRIVATE KEY-----
> > blablabla
> > -----END PRIVATE KEY-----
> > -----BEGIN CERTIFICATE-----
> > blablabla
> > -----END CERTIFICATE-----
> > > Also... I setup another <listen-socket> entry for SSL... but
> > > Icecast
> > > doesn't seem to want to listen on that port when the service
> > > comes up.
> > > Any idea why that might be?
> > > 
> > 
> > Do you mean with different port than 8443, by exemple 8765 ?. If
> > so, what is
> > the output of:
> > netstat -tulpn | grep ':8765'
> 
> Yeah... I?m just trying 8443 ... and netstat shows nada for 8443 ...
> very strange.
> 
After restart the Icecast2 server ? ...



From andy.speagle at wichita.edu  Mon Aug 28 21:56:54 2017
From: andy.speagle at wichita.edu (Speagle, Andy)
Date: Mon, 28 Aug 2017 21:56:54 +0000
Subject: [Icecast] SSL Cert Woes
In-Reply-To: <1503957142.1487.6.camel@speedy.com.ar>
References: <e005224e3984463fa5b2525e5d7e8567@mbxsvc-303.ad.wichita.edu>
 <1503942991.1803.2.camel@speedy.com.ar>
 <cac8a30fad5e4d1b8ebd0710fff16956@mbxsvc-303.ad.wichita.edu>
 <1503948319.1487.2.camel@speedy.com.ar>
 <41b9937880544d6bb45ea38c6afcaa2b@mbxsvc-303.ad.wichita.edu>
 <1503954821.1487.5.camel@speedy.com.ar>
 <4aa24d784fea47e090565fa4eb7cc7d0@mbxsvc-303.ad.wichita.edu>
 <1503957142.1487.6.camel@speedy.com.ar>
Message-ID: <ad35a698d3594af1bdf5de6832f8a4d5@mbxsvc-303.ad.wichita.edu>

> > > > > > > > > > Hi Folks,
> > > > > > > > > >
> > > > > > > > > > I?m having a problem getting a the SSL cert file
> > > > > > > > > > formatted just like icecast wants? I?m running 2.4.2 ?
> > > > > > > > > > and it doesn?t seem to want to use my combined key +
> > > > > > > > > > cert chain no matter in what order I put it.
> > > > > > > > > > Presently, I have it in this format.. with spaces
> > > > > > > > > > between each key/cert?
> > > > > > > > > >
> > > > > > > > > > KEY
> > > > > > > > > >
> > > > > > > > > > CERTCHAIN-1
> > > > > > > > > >
> > > > > > > > > > CERTCHAIN-2
> > > > > > > > > >
> > > > > > > > > > CERTCHAIN-3
> > > > > > > > > >
> > > > > > > > > > MYCERT
> > > > > > > > > >
> > > > > > > > > > And? well? not sure what else to do here.? I have the
> > > > > > > > > > file owned by icecast:icecast ? and ? it should be
> > > > > > > > > > readable in its present location? so, not sure what
> > > > > > > > > > else would be wrong.
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > Firtsly, what operative system are you running ?. On
> > > > > > > > > Debian GNU/Linux user
> > > > > > > > > icecast2 and group icecast, then icecast2:icecast.
> > > > > > > >
> > > > > > > > I'm on RHEL 7, so the user/group is icecast:icecast ...
> > > > > > > >
> > > > > > > > > Secondly, check the Icecast2's error.log looking about
> > > > > > > > > SSL or TLS capability.
> > > > > > > > > On Debian GNU/Linux /var/log/icecast2/error.log.
> > > > > > > >
> > > > > > > > From the log, I get a simple:
> > > > > > > >
> > > > > > > > WARN connection/get_ssl_certificate Invalid cert file <my
> > > > > > > > cert
> > > > > > > > filepath>
> > > > > > > > INFO connection/get_ssl_certificate No SSL capability on
> > > > > > > > any configured ports
> > > > > > > >
> > > > > > >
> > > > > > > Make sure you have set up Icecast correctly:
> > > > > > >
> > > > > > > <listen-socket>
> > > > > > > 	<port>8443</port>
> > > > > > > 	<ssl>1</ssl>
> > > > > > > </listen-socket>
> > > > > >
> > > > > > Yeah... it's setup properly...
> > > > > >
> > > > > > > <paths>
> > > > > > > 	...
> > > > > > > 	<ssl-certificate>/usr/share/icecast2/icecast.pem</ssl-
> > > > > > > certificate>
> > > > > > > </paths>
> > > > > >
> > > > > > Yes... correct for me.
> > > > > >
> > > > > > > Also, there is the possibility that Icecast2 package does
> > > > > > > not
> > > > > > > support encrypted connections via openssl.
> > > > > > > In my case I saw something similar to this:
> > > > > > > [2017-08-08??03:05:34] INFO connection/get_ssl_certificate
> > > > > > > No
> > > > > > > SSL capability Then, like solution I should have compiled
> > > > > > > Icecast with openssl support enabled.
> > > > > >
> > > > > > Well... I believe it to be setup correctly... the RPM has a
> > > > > > libssl
> > > > > > requirement... and the fact that it tries to check the SSL
> > > > > > cert
> > > > > > file indicates that it has capability...
> > > > >
> > > > > I agree.
> > > > > I generated the certificate with:
> > > > > openssl req -x509 -nodes -days 1095 -newkey rsa:2048 -keyout
> > > > > /usr/share/icecast2/icecast.pem -out
> > > > > /usr/share/icecast2/icecast.pem
> > > > > Then you need only change owner and group, nothing more.
> > > >
> > > > Well... I was able to get it to work with a self-signed cert...
> > > > so,
> > > > something must be up with my Starfield signed cert... looks like
> > > > they're configuring certs using "Subject Alternative Name"
> > > > entries by
> > > > default... could that be causing Icecast to barf on the cert?
> > > >
> > >
> > > Looks like something about the configuration of the certificate,
> > > but I do not
> > > specifically what ... I have only done tests with self-signed
> > > certificates.
> > > The format should be:
> > > -----BEGIN PRIVATE KEY-----
> > > blablabla
> > > -----END PRIVATE KEY-----
> > > -----BEGIN CERTIFICATE-----
> > > blablabla
> > > -----END CERTIFICATE-----
> > > > Also... I setup another <listen-socket> entry for SSL... but
> > > > Icecast
> > > > doesn't seem to want to listen on that port when the service
> > > > comes up.
> > > > Any idea why that might be?
> > > >
> > >
> > > Do you mean with different port than 8443, by exemple 8765 ?. If
> > > so, what is
> > > the output of:
> > > netstat -tulpn | grep ':8765'
> >
> > Yeah... I?m just trying 8443 ... and netstat shows nada for 8443 ...
> > very strange.
> >
> After restart the Icecast2 server ? ...

Yeah... after the restart... the port doesn't appear.  Does icecast2 play well with selinux?


From artuch at speedy.com.ar  Mon Aug 28 22:19:15 2017
From: artuch at speedy.com.ar (=?ISO-8859-1?Q?Jos=E9?= Luis Artuch)
Date: Mon, 28 Aug 2017 19:19:15 -0300
Subject: [Icecast] SSL Cert Woes
In-Reply-To: <ad35a698d3594af1bdf5de6832f8a4d5@mbxsvc-303.ad.wichita.edu>
References: <e005224e3984463fa5b2525e5d7e8567@mbxsvc-303.ad.wichita.edu>
 <1503942991.1803.2.camel@speedy.com.ar>
 <cac8a30fad5e4d1b8ebd0710fff16956@mbxsvc-303.ad.wichita.edu>
 <1503948319.1487.2.camel@speedy.com.ar>
 <41b9937880544d6bb45ea38c6afcaa2b@mbxsvc-303.ad.wichita.edu>
 <1503954821.1487.5.camel@speedy.com.ar>
 <4aa24d784fea47e090565fa4eb7cc7d0@mbxsvc-303.ad.wichita.edu>
 <1503957142.1487.6.camel@speedy.com.ar>
 <ad35a698d3594af1bdf5de6832f8a4d5@mbxsvc-303.ad.wichita.edu>
Message-ID: <1503958755.1487.8.camel@speedy.com.ar>

El lun, 28-08-2017 a las 21:56 +0000, Speagle, Andy escribi?:
> > > > > > > > > > > Hi Folks,
> > > > > > > > > > > 
> > > > > > > > > > > I?m having a problem getting a the SSL cert file
> > > > > > > > > > > formatted just like icecast wants? I?m running
> > > > > > > > > > > 2.4.2 ?
> > > > > > > > > > > and it doesn?t seem to want to use my combined
> > > > > > > > > > > key +
> > > > > > > > > > > cert chain no matter in what order I put it.
> > > > > > > > > > > Presently, I have it in this format.. with spaces
> > > > > > > > > > > between each key/cert?
> > > > > > > > > > > 
> > > > > > > > > > > KEY
> > > > > > > > > > > 
> > > > > > > > > > > CERTCHAIN-1
> > > > > > > > > > > 
> > > > > > > > > > > CERTCHAIN-2
> > > > > > > > > > > 
> > > > > > > > > > > CERTCHAIN-3
> > > > > > > > > > > 
> > > > > > > > > > > MYCERT
> > > > > > > > > > > 
> > > > > > > > > > > And? well? not sure what else to do here.? I have
> > > > > > > > > > > the
> > > > > > > > > > > file owned by icecast:icecast ? and ? it should
> > > > > > > > > > > be
> > > > > > > > > > > readable in its present location? so, not sure
> > > > > > > > > > > what
> > > > > > > > > > > else would be wrong.
> > > > > > > > > > > 
> > > > > > > > > > 
> > > > > > > > > > Firtsly, what operative system are you running ?.
> > > > > > > > > > On
> > > > > > > > > > Debian GNU/Linux user
> > > > > > > > > > icecast2 and group icecast, then icecast2:icecast.
> > > > > > > > > 
> > > > > > > > > I'm on RHEL 7, so the user/group is icecast:icecast
> > > > > > > > > ...
> > > > > > > > > 
> > > > > > > > > > Secondly, check the Icecast2's error.log looking
> > > > > > > > > > about
> > > > > > > > > > SSL or TLS capability.
> > > > > > > > > > On Debian GNU/Linux /var/log/icecast2/error.log.
> > > > > > > > > 
> > > > > > > > > From the log, I get a simple:
> > > > > > > > > 
> > > > > > > > > WARN connection/get_ssl_certificate Invalid cert file
> > > > > > > > > <my
> > > > > > > > > cert
> > > > > > > > > filepath>
> > > > > > > > > INFO connection/get_ssl_certificate No SSL capability
> > > > > > > > > on
> > > > > > > > > any configured ports
> > > > > > > > > 
> > > > > > > > 
> > > > > > > > Make sure you have set up Icecast correctly:
> > > > > > > > 
> > > > > > > > <listen-socket>
> > > > > > > > 	<port>8443</port>
> > > > > > > > 	<ssl>1</ssl>
> > > > > > > > </listen-socket>
> > > > > > > 
> > > > > > > Yeah... it's setup properly...
> > > > > > > 
> > > > > > > > <paths>
> > > > > > > > 	...
> > > > > > > > 	<ssl-
> > > > > > > > certificate>/usr/share/icecast2/icecast.pem</ssl-
> > > > > > > > certificate>
> > > > > > > > </paths>
> > > > > > > 
> > > > > > > Yes... correct for me.
> > > > > > > 
> > > > > > > > Also, there is the possibility that Icecast2 package
> > > > > > > > does
> > > > > > > > not
> > > > > > > > support encrypted connections via openssl.
> > > > > > > > In my case I saw something similar to this:
> > > > > > > > [2017-08-08??03:05:34] INFO
> > > > > > > > connection/get_ssl_certificate
> > > > > > > > No
> > > > > > > > SSL capability Then, like solution I should have
> > > > > > > > compiled
> > > > > > > > Icecast with openssl support enabled.
> > > > > > > 
> > > > > > > Well... I believe it to be setup correctly... the RPM has
> > > > > > > a
> > > > > > > libssl
> > > > > > > requirement... and the fact that it tries to check the
> > > > > > > SSL
> > > > > > > cert
> > > > > > > file indicates that it has capability...
> > > > > > 
> > > > > > I agree.
> > > > > > I generated the certificate with:
> > > > > > openssl req -x509 -nodes -days 1095 -newkey rsa:2048
> > > > > > -keyout
> > > > > > /usr/share/icecast2/icecast.pem -out
> > > > > > /usr/share/icecast2/icecast.pem
> > > > > > Then you need only change owner and group, nothing more.
> > > > > 
> > > > > Well... I was able to get it to work with a self-signed
> > > > > cert...
> > > > > so,
> > > > > something must be up with my Starfield signed cert... looks
> > > > > like
> > > > > they're configuring certs using "Subject Alternative Name"
> > > > > entries by
> > > > > default... could that be causing Icecast to barf on the cert?
> > > > > 
> > > > 
> > > > Looks like something about the configuration of the
> > > > certificate,
> > > > but I do not
> > > > specifically what ... I have only done tests with self-signed
> > > > certificates.
> > > > The format should be:
> > > > -----BEGIN PRIVATE KEY-----
> > > > blablabla
> > > > -----END PRIVATE KEY-----
> > > > -----BEGIN CERTIFICATE-----
> > > > blablabla
> > > > -----END CERTIFICATE-----
> > > > > Also... I setup another <listen-socket> entry for SSL... but
> > > > > Icecast
> > > > > doesn't seem to want to listen on that port when the service
> > > > > comes up.
> > > > > Any idea why that might be?
> > > > > 
> > > > 
> > > > Do you mean with different port than 8443, by exemple 8765 ?.
> > > > If
> > > > so, what is
> > > > the output of:
> > > > netstat -tulpn | grep ':8765'
> > > 
> > > Yeah... I?m just trying 8443 ... and netstat shows nada for 8443
> > > ...
> > > very strange.
> > > 
> > 
> > After restart the Icecast2 server ? ...
> 
> Yeah... after the restart... the port doesn't appear.??Does icecast2
> play well with selinux?
> 
Are you in the same LAN than the server ?.
What about the firewall ? ...
ufw allow proto tcp from any to xxx.xxx.xxx.xxx port 8443

I have not worked with SELinux, I do not know :(



From andy.speagle at wichita.edu  Tue Aug 29 03:30:33 2017
From: andy.speagle at wichita.edu (Speagle, Andy)
Date: Tue, 29 Aug 2017 03:30:33 +0000
Subject: [Icecast] SSL Cert Woes
In-Reply-To: <1503958755.1487.8.camel@speedy.com.ar>
References: <e005224e3984463fa5b2525e5d7e8567@mbxsvc-303.ad.wichita.edu>
 <1503942991.1803.2.camel@speedy.com.ar>
 <cac8a30fad5e4d1b8ebd0710fff16956@mbxsvc-303.ad.wichita.edu>
 <1503948319.1487.2.camel@speedy.com.ar>
 <41b9937880544d6bb45ea38c6afcaa2b@mbxsvc-303.ad.wichita.edu>
 <1503954821.1487.5.camel@speedy.com.ar>
 <4aa24d784fea47e090565fa4eb7cc7d0@mbxsvc-303.ad.wichita.edu>
 <1503957142.1487.6.camel@speedy.com.ar>
 <ad35a698d3594af1bdf5de6832f8a4d5@mbxsvc-303.ad.wichita.edu>
 <1503958755.1487.8.camel@speedy.com.ar>
Message-ID: <03cfeba760234cf88ec646cd99ac86d3@mbxsvc-303.ad.wichita.edu>

> > > > > > > > > > > > Hi Folks,
> > > > > > > > > > > >
> > > > > > > > > > > > I?m having a problem getting a the SSL cert file
> > > > > > > > > > > > formatted just like icecast wants? I?m running
> > > > > > > > > > > > 2.4.2 ?
> > > > > > > > > > > > and it doesn?t seem to want to use my combined key
> > > > > > > > > > > > + cert chain no matter in what order I put it.
> > > > > > > > > > > > Presently, I have it in this format.. with spaces
> > > > > > > > > > > > between each key/cert?
> > > > > > > > > > > >
> > > > > > > > > > > > KEY
> > > > > > > > > > > >
> > > > > > > > > > > > CERTCHAIN-1
> > > > > > > > > > > >
> > > > > > > > > > > > CERTCHAIN-2
> > > > > > > > > > > >
> > > > > > > > > > > > CERTCHAIN-3
> > > > > > > > > > > >
> > > > > > > > > > > > MYCERT
> > > > > > > > > > > >
> > > > > > > > > > > > And? well? not sure what else to do here.? I have
> > > > > > > > > > > > the file owned by icecast:icecast ? and ? it
> > > > > > > > > > > > should be readable in its present location? so,
> > > > > > > > > > > > not sure what else would be wrong.
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Firtsly, what operative system are you running ?.
> > > > > > > > > > > On
> > > > > > > > > > > Debian GNU/Linux user
> > > > > > > > > > > icecast2 and group icecast, then icecast2:icecast.
> > > > > > > > > >
> > > > > > > > > > I'm on RHEL 7, so the user/group is icecast:icecast
> > > > > > > > > > ...
> > > > > > > > > >
> > > > > > > > > > > Secondly, check the Icecast2's error.log looking
> > > > > > > > > > > about SSL or TLS capability.
> > > > > > > > > > > On Debian GNU/Linux /var/log/icecast2/error.log.
> > > > > > > > > >
> > > > > > > > > > From the log, I get a simple:
> > > > > > > > > >
> > > > > > > > > > WARN connection/get_ssl_certificate Invalid cert file
> > > > > > > > > > <my cert
> > > > > > > > > > filepath>
> > > > > > > > > > INFO connection/get_ssl_certificate No SSL capability
> > > > > > > > > > on any configured ports
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > Make sure you have set up Icecast correctly:
> > > > > > > > >
> > > > > > > > > <listen-socket>
> > > > > > > > > 	<port>8443</port>
> > > > > > > > > 	<ssl>1</ssl>
> > > > > > > > > </listen-socket>
> > > > > > > >
> > > > > > > > Yeah... it's setup properly...
> > > > > > > >
> > > > > > > > > <paths>
> > > > > > > > > 	...
> > > > > > > > > 	<ssl-
> > > > > > > > > certificate>/usr/share/icecast2/icecast.pem</ssl-
> > > > > > > > > certificate>
> > > > > > > > > </paths>
> > > > > > > >
> > > > > > > > Yes... correct for me.
> > > > > > > >
> > > > > > > > > Also, there is the possibility that Icecast2 package
> > > > > > > > > does
> > > > > > > > > not
> > > > > > > > > support encrypted connections via openssl.
> > > > > > > > > In my case I saw something similar to this:
> > > > > > > > > [2017-08-08??03:05:34] INFO
> > > > > > > > > connection/get_ssl_certificate
> > > > > > > > > No
> > > > > > > > > SSL capability Then, like solution I should have
> > > > > > > > > compiled
> > > > > > > > > Icecast with openssl support enabled.
> > > > > > > >
> > > > > > > > Well... I believe it to be setup correctly... the RPM has
> > > > > > > > a
> > > > > > > > libssl
> > > > > > > > requirement... and the fact that it tries to check the
> > > > > > > > SSL
> > > > > > > > cert
> > > > > > > > file indicates that it has capability...
> > > > > > >
> > > > > > > I agree.
> > > > > > > I generated the certificate with:
> > > > > > > openssl req -x509 -nodes -days 1095 -newkey rsa:2048
> > > > > > > -keyout
> > > > > > > /usr/share/icecast2/icecast.pem -out
> > > > > > > /usr/share/icecast2/icecast.pem
> > > > > > > Then you need only change owner and group, nothing more.
> > > > > >
> > > > > > Well... I was able to get it to work with a self-signed
> > > > > > cert...
> > > > > > so,
> > > > > > something must be up with my Starfield signed cert... looks
> > > > > > like
> > > > > > they're configuring certs using "Subject Alternative Name"
> > > > > > entries by
> > > > > > default... could that be causing Icecast to barf on the cert?
> > > > > >
> > > > >
> > > > > Looks like something about the configuration of the
> > > > > certificate,
> > > > > but I do not
> > > > > specifically what ... I have only done tests with self-signed
> > > > > certificates.
> > > > > The format should be:
> > > > > -----BEGIN PRIVATE KEY-----
> > > > > blablabla
> > > > > -----END PRIVATE KEY-----
> > > > > -----BEGIN CERTIFICATE-----
> > > > > blablabla
> > > > > -----END CERTIFICATE-----
> > > > > > Also... I setup another <listen-socket> entry for SSL... but
> > > > > > Icecast
> > > > > > doesn't seem to want to listen on that port when the service
> > > > > > comes up.
> > > > > > Any idea why that might be?
> > > > > >
> > > > >
> > > > > Do you mean with different port than 8443, by exemple 8765 ?.
> > > > > If
> > > > > so, what is
> > > > > the output of:
> > > > > netstat -tulpn | grep ':8765'
> > > >
> > > > Yeah... I?m just trying 8443 ... and netstat shows nada for 8443
> > > > ...
> > > > very strange.
> > > >
> > >
> > > After restart the Icecast2 server ? ...
> >
> > Yeah... after the restart... the port doesn't appear.??Does icecast2
> > play well with selinux?
> >
> Are you in the same LAN than the server ?.
> What about the firewall ? ...
> ufw allow proto tcp from any to xxx.xxx.xxx.xxx port 8443
> 
> I have not worked with SELinux, I do not know :(

I have found some info about SELinux that I'll work through... though, it's not a firewall problem... I already have that configured... I presently just can't get Icecast to open the port.  Thanks for the help on that.

I just wish I knew what was up with my SSL cert... I need a real world cert... not a self-signed one... and my cert provider is being difficult.

From erwin589 at gmail.com  Tue Aug 29 08:01:36 2017
From: erwin589 at gmail.com (Erwin Pannecoucke)
Date: Tue, 29 Aug 2017 10:01:36 +0200
Subject: [Icecast] Fallback stream not preventing a disconnect
In-Reply-To: <1503909691.2157.17.camel@lion.leolix.org>
References: <CAGwL=seb3SCMm3tcdCnusgHh3xGaoYzU25fiP0vzJV1eoZkz8g@mail.gmail.com>
 <1503907608.2157.15.camel@lion.leolix.org>
 <CAGwL=seqNUaTuTwAi6zjkMM0q_tRr=_iN7EDRr1wjC-_bWu00A@mail.gmail.com>
 <1503909691.2157.17.camel@lion.leolix.org>
Message-ID: <CAGwL=sdE32u04EJUqTyhMOM5H=3RjJRECvwQm7ukj6xR+LfdHQ@mail.gmail.com>

Dear Philipp,

I've compiled it from source on my raspberry pi, and replaced the binary
from the synaptic package manager with the compiled one. Everyting is
working fine now, it seems that there is indeed a "faulty" package in the
repository. I don't know who I should contact to get this fixed?

Anyway, it works, but while using ogg as output stream from mopidy, I get a
delay of 4 (!) minutes when changing tracks:, it takes me about 2 minutes
from the stream to stop (still playing track 1), then another 2 of silence
(probably buffering), and only than I hear my music again (song 2).
If I use mp3 as a stream output, the delay is 2x 10 seconds, thus more
feasable but still a bit long. Anything I can do about that?


Thanks for putting me in the right direction!

Kind regards,
Erwin

2017-08-28 10:41 GMT+02:00 Philipp Schafft <lion at lion.leolix.org>:

> Good morning,
>
>
> On Mon, 2017-08-28 at 10:36 +0200, Erwin Pannecoucke wrote:
> > Dear Philipp,
> >
> > Thanks for this fast answer.
> >
> > I'm using "Icecast 2.3.3-kh7-20130425090916", installed on a Raspberry
> Pi 3
> > using the cononical "sudo apt-get install".
> >
> > The output was copied from the log file in /var/log/icecast2/error.log.
>
> Ok. That is a software from a different vendor (a fork).
>
> Have you tried with official Icecast2?
>
> You can also wait and see if any user of that software is on this ML
> that can help you.
>
> With best regards,
>
> > 2017-08-28 10:06 GMT+02:00 Philipp Schafft <lion at lion.leolix.org>:
> > > On Mon, 2017-08-28 at 09:39 +0200, Erwin Pannecoucke wrote:
> > > > I"m using a combination of mopidy, icecast2 and Home-Assistant on a
> > > > raspberry pi to stream Google music to a Chromecast Audio.
> > >
> > > What exact software are you using. Your log file is not generated by
> > > official Icecast2.
> > >
> > >
> > > > [2017-08-16  14:40:20] INFO mpeg/check_for_mp3 MPEG 1 Layer 3
> detected
> > > > > (44100, 2) on /mopidy.mp3
> > >
> > > No official version of Icecast2 can generate this message.
>
> --
> Philipp.
>  (Rah of PH2)
> _______________________________________________
> 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/20170829/d43846fd/attachment.htm>

From mcbicecast at robuust.nl  Tue Aug 29 08:36:40 2017
From: mcbicecast at robuust.nl (Maarten Bezemer)
Date: Tue, 29 Aug 2017 10:36:40 +0200 (CEST)
Subject: [Icecast] Fallback stream not preventing a disconnect
In-Reply-To: <CAGwL=sdE32u04EJUqTyhMOM5H=3RjJRECvwQm7ukj6xR+LfdHQ@mail.gmail.com>
References: <CAGwL=seb3SCMm3tcdCnusgHh3xGaoYzU25fiP0vzJV1eoZkz8g@mail.gmail.com>
 <1503907608.2157.15.camel@lion.leolix.org>
 <CAGwL=seqNUaTuTwAi6zjkMM0q_tRr=_iN7EDRr1wjC-_bWu00A@mail.gmail.com>
 <1503909691.2157.17.camel@lion.leolix.org>
 <CAGwL=sdE32u04EJUqTyhMOM5H=3RjJRECvwQm7ukj6xR+LfdHQ@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.1708291026590.30078@wormhole.robuust.nl>

Hi Erwin,

Not sure if this might be related. Not sure if you are connecting the 
fallback to another stream or to just a file. If it is a file, then you 
can get buffering issues because most clients have buffers they can fill 
with minutes of audio. If you fall back to a file that is pushed towards 
the client at once, it can push a few minutes of audio in just seconds.

If you set up a locally pushed stream that takes into account the bitrate 
of the fallback file, falling back to that file would only give 1 second 
of data per second.

As for the 10-20sec delays: this is normal, because players buffer data 
and usually only start playing if they have at least 10-15 seconds in 
buffer. Streaming audio was never intended to be real-time. If you want 
that, you need to use UDP data transport and fault-tolerant codecs such as 
used in phone systems.

Best,
Maarten


On Tue, 29 Aug 2017, Erwin Pannecoucke wrote:

> Dear Philipp,
>
> I've compiled it from source on my raspberry pi, and replaced the binary
> from the synaptic package manager with the compiled one. Everyting is
> working fine now, it seems that there is indeed a "faulty" package in the
> repository. I don't know who I should contact to get this fixed?
>
> Anyway, it works, but while using ogg as output stream from mopidy, I get a
> delay of 4 (!) minutes when changing tracks:, it takes me about 2 minutes
> from the stream to stop (still playing track 1), then another 2 of silence
> (probably buffering), and only than I hear my music again (song 2).
> If I use mp3 as a stream output, the delay is 2x 10 seconds, thus more
> feasable but still a bit long. Anything I can do about that?
>
>
> Thanks for putting me in the right direction!
>
> Kind regards,
> Erwin
>
> 2017-08-28 10:41 GMT+02:00 Philipp Schafft <lion at lion.leolix.org>:
>
>> Good morning,
>>
>>
>> On Mon, 2017-08-28 at 10:36 +0200, Erwin Pannecoucke wrote:
>>> Dear Philipp,
>>>
>>> Thanks for this fast answer.
>>>
>>> I'm using "Icecast 2.3.3-kh7-20130425090916", installed on a Raspberry
>> Pi 3
>>> using the cononical "sudo apt-get install".
>>>
>>> The output was copied from the log file in /var/log/icecast2/error.log.
>>
>> Ok. That is a software from a different vendor (a fork).
>>
>> Have you tried with official Icecast2?
>>
>> You can also wait and see if any user of that software is on this ML
>> that can help you.
>>
>> With best regards,
>>
>>> 2017-08-28 10:06 GMT+02:00 Philipp Schafft <lion at lion.leolix.org>:
>>>> On Mon, 2017-08-28 at 09:39 +0200, Erwin Pannecoucke wrote:
>>>>> I"m using a combination of mopidy, icecast2 and Home-Assistant on a
>>>>> raspberry pi to stream Google music to a Chromecast Audio.
>>>>
>>>> What exact software are you using. Your log file is not generated by
>>>> official Icecast2.
>>>>
>>>>
>>>>> [2017-08-16  14:40:20] INFO mpeg/check_for_mp3 MPEG 1 Layer 3
>> detected
>>>>>> (44100, 2) on /mopidy.mp3
>>>>
>>>> No official version of Icecast2 can generate this message.
>>
>> --
>> Philipp.
>>  (Rah of PH2)
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org
>> http://lists.xiph.org/mailman/listinfo/icecast
>>
>


From erwin589 at gmail.com  Wed Aug 30 06:47:44 2017
From: erwin589 at gmail.com (Erwin Pannecoucke)
Date: Wed, 30 Aug 2017 08:47:44 +0200
Subject: [Icecast] Fallback stream not preventing a disconnect
In-Reply-To: <Pine.LNX.4.64.1708291026590.30078@wormhole.robuust.nl>
References: <CAGwL=seb3SCMm3tcdCnusgHh3xGaoYzU25fiP0vzJV1eoZkz8g@mail.gmail.com>
 <1503907608.2157.15.camel@lion.leolix.org>
 <CAGwL=seqNUaTuTwAi6zjkMM0q_tRr=_iN7EDRr1wjC-_bWu00A@mail.gmail.com>
 <1503909691.2157.17.camel@lion.leolix.org>
 <CAGwL=sdE32u04EJUqTyhMOM5H=3RjJRECvwQm7ukj6xR+LfdHQ@mail.gmail.com>
 <Pine.LNX.4.64.1708291026590.30078@wormhole.robuust.nl>
Message-ID: <CAGwL=sd8xibi+=Gizh3ZrE7g5TdpkPCYigS7kHcXZGJAtEkpZw@mail.gmail.com>

Dear Maarten,

Thanks for this clear explanation. The fallback is indeed a local file, so
you are probably absolutely right.

10-20s delay is, luckely, something I can live with ;-)


Thank you all!
Erwin

2017-08-29 10:36 GMT+02:00 Maarten Bezemer <mcbicecast at robuust.nl>:

> Hi Erwin,
>
> Not sure if this might be related. Not sure if you are connecting the
> fallback to another stream or to just a file. If it is a file, then you can
> get buffering issues because most clients have buffers they can fill with
> minutes of audio. If you fall back to a file that is pushed towards the
> client at once, it can push a few minutes of audio in just seconds.
>
> If you set up a locally pushed stream that takes into account the bitrate
> of the fallback file, falling back to that file would only give 1 second of
> data per second.
>
> As for the 10-20sec delays: this is normal, because players buffer data
> and usually only start playing if they have at least 10-15 seconds in
> buffer. Streaming audio was never intended to be real-time. If you want
> that, you need to use UDP data transport and fault-tolerant codecs such as
> used in phone systems.
>
> Best,
> Maarten
>
>
>
> On Tue, 29 Aug 2017, Erwin Pannecoucke wrote:
>
> Dear Philipp,
>>
>> I've compiled it from source on my raspberry pi, and replaced the binary
>> from the synaptic package manager with the compiled one. Everyting is
>> working fine now, it seems that there is indeed a "faulty" package in the
>> repository. I don't know who I should contact to get this fixed?
>>
>> Anyway, it works, but while using ogg as output stream from mopidy, I get
>> a
>> delay of 4 (!) minutes when changing tracks:, it takes me about 2 minutes
>> from the stream to stop (still playing track 1), then another 2 of silence
>> (probably buffering), and only than I hear my music again (song 2).
>> If I use mp3 as a stream output, the delay is 2x 10 seconds, thus more
>> feasable but still a bit long. Anything I can do about that?
>>
>>
>> Thanks for putting me in the right direction!
>>
>> Kind regards,
>> Erwin
>>
>> 2017-08-28 10:41 GMT+02:00 Philipp Schafft <lion at lion.leolix.org>:
>>
>> Good morning,
>>>
>>>
>>> On Mon, 2017-08-28 at 10:36 +0200, Erwin Pannecoucke wrote:
>>>
>>>> Dear Philipp,
>>>>
>>>> Thanks for this fast answer.
>>>>
>>>> I'm using "Icecast 2.3.3-kh7-20130425090916", installed on a Raspberry
>>>>
>>> Pi 3
>>>
>>>> using the cononical "sudo apt-get install".
>>>>
>>>> The output was copied from the log file in /var/log/icecast2/error.log.
>>>>
>>>
>>> Ok. That is a software from a different vendor (a fork).
>>>
>>> Have you tried with official Icecast2?
>>>
>>> You can also wait and see if any user of that software is on this ML
>>> that can help you.
>>>
>>> With best regards,
>>>
>>> 2017-08-28 10:06 GMT+02:00 Philipp Schafft <lion at lion.leolix.org>:
>>>>
>>>>> On Mon, 2017-08-28 at 09:39 +0200, Erwin Pannecoucke wrote:
>>>>>
>>>>>> I"m using a combination of mopidy, icecast2 and Home-Assistant on a
>>>>>> raspberry pi to stream Google music to a Chromecast Audio.
>>>>>>
>>>>>
>>>>> What exact software are you using. Your log file is not generated by
>>>>> official Icecast2.
>>>>>
>>>>>
>>>>> [2017-08-16  14:40:20] INFO mpeg/check_for_mp3 MPEG 1 Layer 3
>>>>>>
>>>>> detected
>>>
>>>> (44100, 2) on /mopidy.mp3
>>>>>>>
>>>>>>
>>>>> No official version of Icecast2 can generate this message.
>>>>>
>>>>
>>> --
>>> Philipp.
>>>  (Rah of PH2)
>>> _______________________________________________
>>> 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/20170830/9b89533e/attachment.htm>

From artuch at speedy.com.ar  Wed Aug 30 21:30:45 2017
From: artuch at speedy.com.ar (=?ISO-8859-1?Q?Jos=E9?= Luis Artuch)
Date: Wed, 30 Aug 2017 18:30:45 -0300
Subject: [Icecast] How many relays
In-Reply-To: <1500659727.4083.0.camel@gmail.com>
References: <ojul1i$lu4$1@blaine.gmane.org>
 <1499685764.1836.3.camel@de.loewenfelsen.net>
 <1500655290.1748.5.camel@speedy.com.ar> <1500657006.2948.3.camel@gmail.com>
 <1500658061.2948.5.camel@speedy.com.ar> <1500659727.4083.0.camel@gmail.com>
Message-ID: <1504128645.12492.2.camel@speedy.com.ar>

Hello !
How many relays can I make with a single Icecast server ?, I can only
run 2 relays at most:

????<relay>
????????<server>111.222.111.222</server>
????????<port>8010</port>
????????<mount>/example1.ogg</mount>
????????<local-mount>/different1.ogg</local-mount>
????????<on-demand>0</on-demand>

????????<relay-shoutcast-metadata>0</relay-shoutcast-metadata>
????</relay>

????<relay>
????????<server>222.111.222.111</server>
????????<port>8020</port>
????????<mount>/example2.ogg</mount>
????????<local-mount>/different2.ogg</local-mount>
????????<on-demand>0</on-demand>

????????<relay-shoutcast-metadata>0</relay-shoutcast-metadata>
????</relay>

Thanks.
Jos? Luis