From phschafft at de.loewenfelsen.net Tue Mar 1 20:04:37 2022 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Tue, 01 Mar 2022 20:04:37 +0000 Subject: [Icecast] Upcoming presentation: Icecast URL authentication Message-ID: <56940b32ca6461e58b127b96c3fc17dc0bfcaf12.camel@de.loewenfelsen.net> Good evening, I would like to invite everyone on this list to our company's presentation on Icecast's URL authentication. The presentation will be this Friday (2022-03-04) at 15:00 UTC on Jitsi. A open discussion will follow it. Details: https://www.linkedin.com/events/icecasturlauthentication6901825140309786624/about/ To apply for one of the limited virtual seats please just reply off- list before Thursday 20:00 UTC. With best regards, PS: This presentation is part of a series of presentations on Icecast and related topics. We publish them on https://www.linkedin.com/company/loewenfelsen/ -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From fredg at paravelsystems.com Wed Mar 2 15:11:01 2022 From: fredg at paravelsystems.com (Fred Gleason) Date: Wed, 2 Mar 2022 10:11:01 -0500 Subject: [Icecast] Upcoming presentation: Icecast URL authentication In-Reply-To: <56940b32ca6461e58b127b96c3fc17dc0bfcaf12.camel@de.loewenfelsen.net> References: <56940b32ca6461e58b127b96c3fc17dc0bfcaf12.camel@de.loewenfelsen.net> Message-ID: The link: https://www.linkedin.com/events/icecasturlauthentication6901825140309786624/about/ is throwing a 404 for me. Cheers! |---------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |---------------------------------------------------------------------| | A room without books is like a body without a soul. | | | | -- Cicero | |---------------------------------------------------------------------| On Tue, Mar 1, 2022 at 3:04 PM Philipp Schafft < phschafft at de.loewenfelsen.net> wrote: > Good evening, > > I would like to invite everyone on this list to our company's > presentation on Icecast's URL authentication. > > > The presentation will be this Friday (2022-03-04) at 15:00 UTC on > Jitsi. A open discussion will follow it. > > Details: > > https://www.linkedin.com/events/icecasturlauthentication6901825140309786624/about/ > > To apply for one of the limited virtual seats please just reply off- > list before Thursday 20:00 UTC. > > > With best regards, > > PS: This presentation is part of a series of presentations on Icecast > and related topics. We publish them on > https://www.linkedin.com/company/loewenfelsen/ > > -- > Philipp Schafft (CEO/Gesch?ftsf?hrer) > Telephon: +49.3535 490 17 92 > Website: https://www.loewenfelsen.net/ > Follow us: https://www.linkedin.com/company/loewenfelsen/ > > L?wenfelsen UG (haftungsbeschr?nkt) Registration number: > Bickinger Stra?e 21 HRB 12308 CB > 04916 Herzberg (Elster) VATIN/USt-ID: > Germany DE305133015 > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: From phschafft at de.loewenfelsen.net Wed Mar 2 16:03:13 2022 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Wed, 02 Mar 2022 16:03:13 +0000 Subject: [Icecast] Upcoming presentation: Icecast URL authentication In-Reply-To: References: <56940b32ca6461e58b127b96c3fc17dc0bfcaf12.camel@de.loewenfelsen.net> Message-ID: <10e87cc4e490a064dec01d42fd18e85ff3cb3928.camel@de.loewenfelsen.net> Good evening, first a little announcement: All places are taken. But if you are still interested I'm happy to put you on the list in case someone needs to cancel. Also happy to hear (off-list) about what topics you're interested in for future presentations. On Wed, 2022-03-02 at 10:11 -0500, Fred Gleason wrote: > The link: > https://www.linkedin.com/events/icecasturlauthentication6901825140309786624/about/ > is throwing a 404 for me. This is strange. I just checked and it works for me. However I think you need to be logged into LinkedIn to see it. With best regards, > On Tue, Mar 1, 2022 at 3:04 PM Philipp Schafft < > phschafft at de.loewenfelsen.net> wrote: > > Good evening, > > > > I would like to invite everyone on this list to our company's > > presentation on Icecast's URL authentication. > > > > > > The presentation will be this Friday (2022-03-04) at 15:00 UTC on > > Jitsi. A open discussion will follow it. > > > > Details: > > https://www.linkedin.com/events/icecasturlauthentication6901825140309786624/about/ > > > > To apply for one of the limited virtual seats please just reply > > off- > > list before Thursday 20:00 UTC. > > > > > > With best regards, > > > > PS: This presentation is part of a series of presentations on > > Icecast > > and related topics. We publish them on > > https://www.linkedin.com/company/loewenfelsen/ -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From phschafft at de.loewenfelsen.net Thu Mar 3 08:22:53 2022 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Thu, 03 Mar 2022 08:22:53 +0000 Subject: [Icecast] Release of libigloo, version 0.9.1 Message-ID: <494716fea4f9964380744286a8b17b2766242516.camel@de.loewenfelsen.net> Good morning, the Icecast Project is very pleased to have released the next version of libigloo, version 0.9.1. libigloo is a generic C framework which provides us with a common space for helpers and support routines for other Icecast Project's software. However it can also be used outside of Icecast context. The new version 0.9.1 comes with a lot of updates: * Several fixes. * New string pool feature that provides a optimised storage for C strings. * TAP test frame work which can easily used by other projects. * Portable low level time API. * SHA-3 digest and HMAC support. * Pseudo random number generator. * Helper for working with UUIDs. If you are a downstream maintainer we would like to kindly ask considering updating packages. You can find our news entry at: https://icecast.org/news/libigloo-release-0_9_1/ Downloads can be found at: https://icecast.org/download/#bindings With best regards, -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From tombones at 440music.com Thu Mar 3 14:03:21 2022 From: tombones at 440music.com (Tommy TBones Cramer) Date: Thu, 3 Mar 2022 08:03:21 -0600 Subject: [Icecast] Release of libigloo, version 0.9.1 In-Reply-To: <494716fea4f9964380744286a8b17b2766242516.camel@de.loewenfelsen.net> References: <494716fea4f9964380744286a8b17b2766242516.camel@de.loewenfelsen.net> Message-ID: <17e25b7c-e5b8-2d7d-c532-04d92101395e@440music.com> I've been following this messages for a while just starting to reply. I'm having issues with googleusercontent com connecting for days rebroadcasting my streams without permission. Ubuntu 18.05 CentovaCast Control Panel UFW rules haven't stopped googleuser from connecting, the change the server and connect again. If they were attempting to log-in fail2ban would stop them I'm also looking to block all IPs originating in Russia Please excuse me if I made an error Tommy TBones Cramer Owner 440Music Entertainment Co www.440music.com 773 491 9937 599 365 0104 Zoom t440Music Skype On 3/3/22 02:22, Philipp Schafft wrote: > Good morning, > > the Icecast Project is very pleased to have released the next version > of libigloo, version 0.9.1. > > > libigloo is a generic C framework which provides us with a common space > for helpers and support routines for other Icecast Project's software. > However it can also be used outside of Icecast context. > > The new version 0.9.1 comes with a lot of updates: > > * Several fixes. > * New string pool feature that provides a optimised storage for C > strings. > * TAP test frame work which can easily used by other projects. > * Portable low level time API. > * SHA-3 digest and HMAC support. > * Pseudo random number generator. > * Helper for working with UUIDs. > > If you are a downstream maintainer we would like to kindly ask > considering updating packages. > > You can find our news entry at: > https://icecast.org/news/libigloo-release-0_9_1/ > > Downloads can be found at: > https://icecast.org/download/#bindings > > > With best regards, > > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast -- Tommy TBones Cramer Owner 440Music Entertainment Co www.440music.com 773 491 9937 599 365 0104 Zoom t440Music Skype From epirat07 at gmail.com Thu Mar 3 14:12:32 2022 From: epirat07 at gmail.com (Marvin Scholz) Date: Thu, 03 Mar 2022 15:12:32 +0100 Subject: [Icecast] Release of libigloo, version 0.9.1 In-Reply-To: <17e25b7c-e5b8-2d7d-c532-04d92101395e@440music.com> References: <494716fea4f9964380744286a8b17b2766242516.camel@de.loewenfelsen.net> <17e25b7c-e5b8-2d7d-c532-04d92101395e@440music.com> Message-ID: On 3 Mar 2022, at 15:03, Tommy TBones Cramer wrote: > I've been following this messages for a while just starting to reply. > I'm having issues with googleusercontent com connecting for days > rebroadcasting my streams without permission. > Ubuntu 18.05 > CentovaCast Control Panel > UFW rules haven't stopped googleuser from connecting, the change the > server and connect again. > If they were attempting to log-in fail2ban would stop them > I'm also looking to block all IPs originating in Russia > > Please excuse me if I made an error > Do not hijack an existing topic. Do not reply to something completely unrelated to what you are asking. Instead compose a new email to the list mail address: icecast at xiph.org > Tommy TBones Cramer > Owner > 440Music Entertainment Co > www.440music.com > 773 491 9937 > 599 365 0104 Zoom > t440Music Skype > > > On 3/3/22 02:22, Philipp Schafft wrote: >> Good morning, >> >> the Icecast Project is very pleased to have released the next version >> of libigloo, version 0.9.1. >> >> >> libigloo is a generic C framework which provides us with a common >> space >> for helpers and support routines for other Icecast Project's >> software. >> However it can also be used outside of Icecast context. >> >> The new version 0.9.1 comes with a lot of updates: >> >> * Several fixes. >> * New string pool feature that provides a optimised storage for C >> strings. >> * TAP test frame work which can easily used by other projects. >> * Portable low level time API. >> * SHA-3 digest and HMAC support. >> * Pseudo random number generator. >> * Helper for working with UUIDs. >> >> If you are a downstream maintainer we would like to kindly ask >> considering updating packages. >> >> You can find our news entry at: >> https://icecast.org/news/libigloo-release-0_9_1/ >> >> Downloads can be found at: >> https://icecast.org/download/#bindings >> >> >> With best regards, >> >> >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast > > -- > Tommy TBones Cramer > Owner > 440Music Entertainment Co > www.440music.com > 773 491 9937 > 599 365 0104 Zoom > t440Music Skype > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast From chiapas at aktivix.org Fri Mar 4 15:11:51 2022 From: chiapas at aktivix.org (Chip) Date: Fri, 4 Mar 2022 15:11:51 +0000 Subject: [Icecast] Upcoming presentation: Icecast URL authentication In-Reply-To: References: <56940b32ca6461e58b127b96c3fc17dc0bfcaf12.camel@de.loewenfelsen.net> Message-ID: Anyone have a link to the Jitsi session? I can't see it though I've registered for the event. Thanks Chip On Wed, 2 Mar 2022 at 15:11, Fred Gleason wrote: > The link: > > https://www.linkedin.com/events/icecasturlauthentication6901825140309786624/about/ > is throwing a 404 for me. > > Cheers! > > |---------------------------------------------------------------------| > | Frederick F. Gleason, Jr. | Chief Developer | > | | Paravel Systems | > |---------------------------------------------------------------------| > | A room without books is like a body without a soul. | > | | > | -- Cicero | > |---------------------------------------------------------------------| > > On Tue, Mar 1, 2022 at 3:04 PM Philipp Schafft < > phschafft at de.loewenfelsen.net> wrote: > >> Good evening, >> >> I would like to invite everyone on this list to our company's >> presentation on Icecast's URL authentication. >> >> >> The presentation will be this Friday (2022-03-04) at 15:00 UTC on >> Jitsi. A open discussion will follow it. >> >> Details: >> >> https://www.linkedin.com/events/icecasturlauthentication6901825140309786624/about/ >> >> To apply for one of the limited virtual seats please just reply off- >> list before Thursday 20:00 UTC. >> >> >> With best regards, >> >> PS: This presentation is part of a series of presentations on Icecast >> and related topics. We publish them on >> https://www.linkedin.com/company/loewenfelsen/ >> >> -- >> Philipp Schafft (CEO/Gesch?ftsf?hrer) >> Telephon: +49.3535 490 17 92 >> Website: https://www.loewenfelsen.net/ >> Follow us: https://www.linkedin.com/company/loewenfelsen/ >> >> L?wenfelsen UG (haftungsbeschr?nkt) Registration number: >> Bickinger Stra?e 21 HRB 12308 CB >> 04916 Herzberg (Elster) VATIN/USt-ID: >> Germany DE305133015 >> _______________________________________________ >> 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: From yahav.shasha at gmail.com Fri Mar 4 15:19:31 2022 From: yahav.shasha at gmail.com (Yahav Shasha) Date: Fri, 4 Mar 2022 17:19:31 +0200 Subject: [Icecast] Upcoming presentation: Icecast URL authentication In-Reply-To: References: <56940b32ca6461e58b127b96c3fc17dc0bfcaf12.camel@de.loewenfelsen.net> Message-ID: Would love to get a link as well ?????? ??? ??, 4 ???? 2022, 17:12, ??? Chip ?: > Anyone have a link to the Jitsi session? > > I can't see it though I've registered for the event. > > Thanks > > Chip > > On Wed, 2 Mar 2022 at 15:11, Fred Gleason > wrote: > >> The link: >> >> https://www.linkedin.com/events/icecasturlauthentication6901825140309786624/about/ >> is throwing a 404 for me. >> >> Cheers! >> >> |---------------------------------------------------------------------| >> | Frederick F. Gleason, Jr. | Chief Developer | >> | | Paravel Systems | >> |---------------------------------------------------------------------| >> | A room without books is like a body without a soul. | >> | | >> | -- Cicero | >> |---------------------------------------------------------------------| >> >> On Tue, Mar 1, 2022 at 3:04 PM Philipp Schafft < >> phschafft at de.loewenfelsen.net> wrote: >> >>> Good evening, >>> >>> I would like to invite everyone on this list to our company's >>> presentation on Icecast's URL authentication. >>> >>> >>> The presentation will be this Friday (2022-03-04) at 15:00 UTC on >>> Jitsi. A open discussion will follow it. >>> >>> Details: >>> >>> https://www.linkedin.com/events/icecasturlauthentication6901825140309786624/about/ >>> >>> To apply for one of the limited virtual seats please just reply off- >>> list before Thursday 20:00 UTC. >>> >>> >>> With best regards, >>> >>> PS: This presentation is part of a series of presentations on Icecast >>> and related topics. We publish them on >>> https://www.linkedin.com/company/loewenfelsen/ >>> >>> -- >>> Philipp Schafft (CEO/Gesch?ftsf?hrer) >>> Telephon: +49.3535 490 17 92 >>> Website: https://www.loewenfelsen.net/ >>> Follow us: https://www.linkedin.com/company/loewenfelsen/ >>> >>> L?wenfelsen UG (haftungsbeschr?nkt) Registration number: >>> Bickinger Stra?e 21 HRB 12308 CB >>> 04916 Herzberg (Elster) VATIN/USt-ID: >>> Germany DE305133015 >>> _______________________________________________ >>> Icecast mailing list >>> Icecast at xiph.org >>> http://lists.xiph.org/mailman/listinfo/icecast >>> >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast >> > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: From phschafft at de.loewenfelsen.net Thu Mar 10 10:23:04 2022 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Thu, 10 Mar 2022 10:23:04 +0000 Subject: [Icecast] Upcoming presentation: Icecast URL authentication In-Reply-To: References: <56940b32ca6461e58b127b96c3fc17dc0bfcaf12.camel@de.loewenfelsen.net> Message-ID: Good morning, On Fri, 2022-03-04 at 17:19 +0200, Yahav Shasha wrote: > Would love to get a link as well > > ?????? ??? ??, 4 ???? 2022, 17:12, ??? Chip ?: > > Anyone have a link to the Jitsi session? > > > > I can't see it though I've registered for the event. I'm sorry that it wasn't to be. Shortly after I posted the link on the list we were already out of virtual seats. We limit the amount of attendee to have the room for everyone to participate in the discussion following every presentation?. We generally announce first on our LinkedIn page: https://www.linkedin.com/company/loewenfelsen/ If there are still seats left, we may announce over here as well. Who get's a seat: It is mostly "First come, first served". However we prioritise a little bit: Coworkers first, if some asked for a topic we try to get them in, ... That said about the background, here are the good news: We plan to run this series of presentations for at least all of this year. There will be roughly one every two weeks (skipping holidays etc.). If anyone has a request for a topic, we're happy to hear about it (off- list). Also if we'll repeat those presentations that resulted in most interest. (And then we'll prioritise those who did not made it yet :). I hope this adds a bit of transparency on why and how. With best regards, ? This is also why we do not publish recordings and why we operate "cams off". -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From fredg at paravelsystems.com Thu Mar 10 17:12:33 2022 From: fredg at paravelsystems.com (Fred Gleason) Date: Thu, 10 Mar 2022 12:12:33 -0500 Subject: [Icecast] Upcoming presentation: Icecast URL authentication In-Reply-To: References: <56940b32ca6461e58b127b96c3fc17dc0bfcaf12.camel@de.loewenfelsen.net> Message-ID: On Mar 10, 2022, at 05:23, Philipp Schafft wrote: > I'm sorry that it wasn't to be. > > Shortly after I posted the link on the list we were already out of > virtual seats. We limit the amount of attendee to have the room for > everyone to participate in the discussion following every > presentation?. > > We generally announce first on our LinkedIn page: > https://www.linkedin.com/company/loewenfelsen/ Thanks for this info Philipp! However, in looking at that page, I?m not finding an announcement for last week?s talk in the ?Updates? list. Am I looking in the wrong place? Cheers! |---------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |---------------------------------------------------------------------| | A room without books is like a body without a soul. | | | | -- Cicero | |---------------------------------------------------------------------| -------------- next part -------------- An HTML attachment was scrubbed... URL: From db76 at riseup.net Thu Mar 10 21:57:01 2022 From: db76 at riseup.net (Damian) Date: Fri, 11 Mar 2022 07:57:01 +1000 Subject: [Icecast] Icecast2 and SSL certificate renewal Message-ID: <254B0CD9-F8CD-491A-B7E6-DA7809C498B5@riseup.net> Hi I have a question about current best-practice for renewing SSL certificates for Icecast. I am looking into automating the renewal process for my SSL certificate using Let?s Encrypt. However, it?s my understanding that the Icecast server would need to be restarted each time the automatic process takes place (every 3 months) which I think would be disruptive to running a continuous streaming service. All the listeners would be kicked off the streams. I?d like to know if anyone knows of a better solution or if this is just an unavoidable problem in terms of running streams via HTTPS. Thanks for any help Damian From cdgraff at gmail.com Thu Mar 10 23:53:53 2022 From: cdgraff at gmail.com (Alejandro Ferrari) Date: Thu, 10 Mar 2022 20:53:53 -0300 Subject: [Icecast] Icecast2 and SSL certificate renewal In-Reply-To: <254B0CD9-F8CD-491A-B7E6-DA7809C498B5@riseup.net> References: <254B0CD9-F8CD-491A-B7E6-DA7809C498B5@riseup.net> Message-ID: Hi Damian, Kill -HUP $PID That will reload the config without stop the streams. El jue, 10 mar 2022 a la(s) 18:57, Damian (db76 at riseup.net) escribi?: > Hi > > I have a question about current best-practice for renewing SSL > certificates for Icecast. > I am looking into automating the renewal process for my SSL certificate > using Let?s Encrypt. > However, it?s my understanding that the Icecast server would need to be > restarted each time the automatic process takes place (every 3 months) > which I think would be disruptive to running a continuous streaming > service. > All the listeners would be kicked off the streams. > > I?d like to know if anyone knows of a better solution or if this is just > an unavoidable problem in terms of running streams via HTTPS. > > Thanks for any help > > Damian > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: From db76 at riseup.net Fri Mar 11 00:00:19 2022 From: db76 at riseup.net (Damian) Date: Fri, 11 Mar 2022 10:00:19 +1000 Subject: [Icecast] Icecast2 and SSL certificate renewal In-Reply-To: References: <254B0CD9-F8CD-491A-B7E6-DA7809C498B5@riseup.net> Message-ID: <60C890DE-2A81-4899-A885-626074F74BEA@riseup.net> Nice! Thanks Alejandro. That will be very useful if I choose to go with an automated process. > On 11 Mar 2022, at 9:53 am, Alejandro Ferrari wrote: > > Hi Damian, > > Kill -HUP $PID > > That will reload the config without stop the streams. > > El jue, 10 mar 2022 a la(s) 18:57, Damian (db76 at riseup.net ) escribi?: > Hi > > I have a question about current best-practice for renewing SSL certificates for Icecast. > I am looking into automating the renewal process for my SSL certificate using Let?s Encrypt. > However, it?s my understanding that the Icecast server would need to be restarted each time the automatic process takes place (every 3 months) which I think would be disruptive to running a continuous streaming service. > All the listeners would be kicked off the streams. > > I?d like to know if anyone knows of a better solution or if this is just an unavoidable problem in terms of running streams via HTTPS. > > Thanks for any help > > Damian > > _______________________________________________ > 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: From ross at stationplaylist.com Fri Mar 11 01:05:27 2022 From: ross at stationplaylist.com (Ross Levis) Date: Fri, 11 Mar 2022 14:05:27 +1300 Subject: [Icecast] Icecast2 and SSL certificate renewal In-Reply-To: References: <254B0CD9-F8CD-491A-B7E6-DA7809C498B5@riseup.net> Message-ID: <00cb01d834e4$1a3c31d0$4eb49570$@com> Is there any method to do that on Windows? From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Alejandro Ferrari Sent: Friday, 11 March 2022 12:54 pm To: Icecast streaming server user discussions Subject: Re: [Icecast] Icecast2 and SSL certificate renewal Hi Damian, Kill -HUP $PID That will reload the config without stop the streams. El jue, 10 mar 2022 a la(s) 18:57, Damian (db76 at riseup.net) escribi?: Hi I have a question about current best-practice for renewing SSL certificates for Icecast. I am looking into automating the renewal process for my SSL certificate using Let?s Encrypt. However, it?s my understanding that the Icecast server would need to be restarted each time the automatic process takes place (every 3 months) which I think would be disruptive to running a continuous streaming service. All the listeners would be kicked off the streams. I?d like to know if anyone knows of a better solution or if this is just an unavoidable problem in terms of running streams via HTTPS. Thanks for any help Damian _______________________________________________ Icecast mailing list Icecast at xiph.org http://lists.xiph.org/mailman/listinfo/icecast -------------- next part -------------- An HTML attachment was scrubbed... URL: From phschafft at de.loewenfelsen.net Fri Mar 11 08:55:19 2022 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Fri, 11 Mar 2022 08:55:19 +0000 Subject: [Icecast] Icecast2 and SSL certificate renewal In-Reply-To: <00cb01d834e4$1a3c31d0$4eb49570$@com> References: <254B0CD9-F8CD-491A-B7E6-DA7809C498B5@riseup.net> <00cb01d834e4$1a3c31d0$4eb49570$@com> Message-ID: <89ec76e2585356764c05fcff5eafdd597db8a428.camel@de.loewenfelsen.net> Good Morning, On Fri, 2022-03-11 at 14:05 +1300, Ross Levis wrote: > Is there any method to do that on Windows? There is a reload link on the admin web interface on 2.5.x. It points to /admin/reloadconfig.xsl; if you want to do it programmatically you can just call /admin/reloadconfig with admin credentials. Reloading via API is not yet supported by 2.4.4. With best regards, > From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of > Alejandro Ferrari > Sent: Friday, 11 March 2022 12:54 pm > To: Icecast streaming server user discussions > Subject: Re: [Icecast] Icecast2 and SSL certificate renewal > > Hi Damian, > > Kill -HUP $PID > > That will reload the config without stop the streams. > > El jue, 10 mar 2022 a la(s) 18:57, Damian (db76 at riseup.net) escribi?: > > Hi > > > > I have a question about current best-practice for renewing SSL > > certificates for Icecast. > > I am looking into automating the renewal process for my SSL > > certificate using Let?s Encrypt. > > However, it?s my understanding that the Icecast server would need > > to be restarted each time the automatic process takes place (every > > 3 months) which I think would be disruptive to running a continuous > > streaming service. > > All the listeners would be kicked off the streams. > > > > I?d like to know if anyone knows of a better solution or if this is > > just an unavoidable problem in terms of running streams via HTTPS. > > > > Thanks for any help > > > > Damian -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From phschafft at de.loewenfelsen.net Fri Mar 11 10:31:29 2022 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Fri, 11 Mar 2022 10:31:29 +0000 Subject: [Icecast] Upcoming presentation: Icecast URL authentication In-Reply-To: References: <56940b32ca6461e58b127b96c3fc17dc0bfcaf12.camel@de.loewenfelsen.net> Message-ID: Good morning, On Thu, 2022-03-10 at 12:12 -0500, Fred Gleason wrote: > On Mar 10, 2022, at 05:23, Philipp Schafft < > phschafft at de.loewenfelsen.net> wrote: > > > I'm sorry that it wasn't to be. > > > > Shortly after I posted the link on the list we were already out of > > virtual seats. We limit the amount of attendee to have the room for > > everyone to participate in the discussion following every > > presentation?. > > > > We generally announce first on our LinkedIn page: > > https://www.linkedin.com/company/loewenfelsen/ > > Thanks for this info Philipp! > > However, in looking at that page, I?m not finding an announcement for > last week?s talk in the ?Updates? list. Am I looking in the wrong > place? It took me a little moment as well to find it. LinkedIn is not the most easy to search. Direct link to the posting: https://www.linkedin.com/posts/loewenfelsen_icecast-authentication-statistics-activity-6901825142356611072-QyxM/ However future events are also listed directly on the front page and on the "Events" tab. In the "Events" tab you also find past presentations. Hope that helps. :) With best regards, -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From db76 at riseup.net Sat Mar 12 07:57:34 2022 From: db76 at riseup.net (Damian) Date: Sat, 12 Mar 2022 17:57:34 +1000 Subject: [Icecast] Icecast2 and SSL certificate renewal In-Reply-To: <89ec76e2585356764c05fcff5eafdd597db8a428.camel@de.loewenfelsen.net> References: <254B0CD9-F8CD-491A-B7E6-DA7809C498B5@riseup.net> <00cb01d834e4$1a3c31d0$4eb49570$@com> <89ec76e2585356764c05fcff5eafdd597db8a428.camel@de.loewenfelsen.net> Message-ID: <487A18D3-581B-43BF-B293-064592AAFD57@riseup.net> Hi Philipp, Thanks for your reply. For now I will continue with 2.4.4 and just do things manually, with an eye to using a more automated process when I move over to version 2.5. I realise that it is generally not recommended, but can you tell me whether you think version 2.5 is generally stable enough to use for production at this stage? Also, is it recommended that we also follow the LinkedIn page at https://www.linkedin.com/company/loewenfelsen/ for important info about Icecast development? Damian > On 11 Mar 2022, at 6:55 pm, Philipp Schafft wrote: > > Good Morning, > > On Fri, 2022-03-11 at 14:05 +1300, Ross Levis wrote: >> Is there any method to do that on Windows? > > There is a reload link on the admin web interface on 2.5.x. > > It points to /admin/reloadconfig.xsl; if you want to do it > programmatically you can just call /admin/reloadconfig with admin > credentials. > > Reloading via API is not yet supported by 2.4.4. > > > With best regards, > >> From: Icecast [mailto:icecast-bounces at xiph.org ] On Behalf Of >> Alejandro Ferrari >> Sent: Friday, 11 March 2022 12:54 pm >> To: Icecast streaming server user discussions >> Subject: Re: [Icecast] Icecast2 and SSL certificate renewal >> >> Hi Damian, >> >> Kill -HUP $PID >> >> That will reload the config without stop the streams. >> >> El jue, 10 mar 2022 a la(s) 18:57, Damian (db76 at riseup.net) escribi?: >>> Hi >>> >>> I have a question about current best-practice for renewing SSL >>> certificates for Icecast. >>> I am looking into automating the renewal process for my SSL >>> certificate using Let?s Encrypt. >>> However, it?s my understanding that the Icecast server would need >>> to be restarted each time the automatic process takes place (every >>> 3 months) which I think would be disruptive to running a continuous >>> streaming service. >>> All the listeners would be kicked off the streams. >>> >>> I?d like to know if anyone knows of a better solution or if this is >>> just an unavoidable problem in terms of running streams via HTTPS. >>> >>> Thanks for any help >>> >>> Damian > > > -- > Philipp Schafft (CEO/Gesch?ftsf?hrer) > Telephon: +49.3535 490 17 92 > Website: https://www.loewenfelsen.net/ > Follow us: https://www.linkedin.com/company/loewenfelsen/ > > L?wenfelsen UG (haftungsbeschr?nkt) Registration number: > Bickinger Stra?e 21 HRB 12308 CB > 04916 Herzberg (Elster) VATIN/USt-ID: > Germany DE305133015 > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast -------------- next part -------------- An HTML attachment was scrubbed... URL: From uktony at radiocompany.net Sat Mar 12 10:20:27 2022 From: uktony at radiocompany.net (Tony Harding) Date: Sat, 12 Mar 2022 18:20:27 +0800 Subject: [Icecast] Icecast2 and SSL certificate renewal In-Reply-To: <00cb01d834e4$1a3c31d0$4eb49570$@com> Message-ID: <20220312102749.69BE560B9F@smtp3.osuosl.org> Was the windows question answered? ? > icecast2 ?HUP ????? ? Tony ? _____ From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Ross Levis Sent: Friday, March 11, 2022 9:05 AM To: 'Icecast streaming server user discussions' Subject: Re: [Icecast] Icecast2 and SSL certificate renewal ? Is there any method to do that on Windows? ? From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Alejandro Ferrari Sent: Friday, 11 March 2022 12:54 pm To: Icecast streaming server user discussions Subject: Re: [Icecast] Icecast2 and SSL certificate renewal ? Hi Damian, ? ? Kill -HUP $PID ? That will reload the config without stop the streams. ? El jue, 10 mar 2022 a la(s) 18:57, Damian (db76 at riseup.net) escribi?: Hi I have a question about current best-practice for renewing SSL certificates for Icecast. I am looking into automating the renewal process for my SSL certificate using Let?s Encrypt. However, it?s my understanding that the Icecast server would need to be restarted each time the automatic process takes place (every 3 months) which I think would be disruptive to running a continuous streaming service. All the listeners would be kicked off the streams. I?d like to know if anyone knows of a better solution or if this is just an unavoidable problem in terms of running streams via HTTPS. Thanks for any help Damian _______________________________________________ Icecast mailing list Icecast at xiph.org http://lists.xiph.org/mailman/listinfo/icecast -------------- next part -------------- An HTML attachment was scrubbed... URL: From db76 at riseup.net Sat Mar 12 11:31:15 2022 From: db76 at riseup.net (Damian) Date: Sat, 12 Mar 2022 21:31:15 +1000 Subject: [Icecast] Icecast2 and SSL certificate renewal In-Reply-To: <20220312102749.69BE560B9F@smtp3.osuosl.org> References: <20220312102749.69BE560B9F@smtp3.osuosl.org> Message-ID: <616CB59B-50E5-4A08-AF9C-DD8AA47FFB44@riseup.net> Well, I?m not sure if you read Philipp?s earlier response, so I?ve cut and pasted it below, but to me it seems to suggest that reloading the config is not supported in version 2.4.4. You would need to upgrade to version 2.5. > Good Morning, > > On Fri, 2022-03-11 at 14:05 +1300, Ross Levis wrote: >> Is there any method to do that on Windows? > > There is a reload link on the admin web interface on 2.5.x. > > It points to /admin/reloadconfig.xsl; if you want to do it > programmatically you can just call /admin/reloadconfig with admin > credentials. > > Reloading via API is not yet supported by 2.4.4. > On 12 Mar 2022, at 8:20 pm, Tony Harding wrote: > > Was the windows question answered? > > > icecast2 ?HUP ????? > > Tony > > From: Icecast [mailto:icecast-bounces at xiph.org ] On Behalf Of Ross Levis > Sent: Friday, March 11, 2022 9:05 AM > To: 'Icecast streaming server user discussions' > Subject: Re: [Icecast] Icecast2 and SSL certificate renewal > > Is there any method to do that on Windows? > > From: Icecast [mailto:icecast-bounces at xiph.org ] On Behalf Of Alejandro Ferrari > Sent: Friday, 11 March 2022 12:54 pm > To: Icecast streaming server user discussions > Subject: Re: [Icecast] Icecast2 and SSL certificate renewal > > Hi Damian, > > Kill -HUP $PID > > That will reload the config without stop the streams. > > El jue, 10 mar 2022 a la(s) 18:57, Damian (db76 at riseup.net ) escribi?: >> Hi >> >> I have a question about current best-practice for renewing SSL certificates for Icecast. >> I am looking into automating the renewal process for my SSL certificate using Let?s Encrypt. >> However, it?s my understanding that the Icecast server would need to be restarted each time the automatic process takes place (every 3 months) which I think would be disruptive to running a continuous streaming service. >> All the listeners would be kicked off the streams. >> >> I?d like to know if anyone knows of a better solution or if this is just an unavoidable problem in terms of running streams via HTTPS. >> >> Thanks for any help >> >> Damian >> >> _______________________________________________ >> 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: From phschafft at de.loewenfelsen.net Sat Mar 12 11:34:06 2022 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Sat, 12 Mar 2022 11:34:06 +0000 Subject: [Icecast] Icecast2 and SSL certificate renewal In-Reply-To: <616CB59B-50E5-4A08-AF9C-DD8AA47FFB44@riseup.net> References: <20220312102749.69BE560B9F@smtp3.osuosl.org> <616CB59B-50E5-4A08-AF9C-DD8AA47FFB44@riseup.net> Message-ID: <811bbd3679f41785a90f0d555f459ed45eaae309.camel@de.loewenfelsen.net> Good morning, On Sat, 2022-03-12 at 21:31 +1000, Damian wrote: > Well, I?m not sure if you read Philipp?s earlier response, so I?ve > cut and pasted it below, but to me it seems to suggest that reloading > the config is not supported in version 2.4.4. You would need to > upgrade to version 2.5. Actually it is kind of supported. Just that on Windows there is no support for signals. So there is no way to tell the server to do so. 2.5.x adds the reload via web (API and admin UI) to resolve this shortcoming. Hope that explains the situation a little bit better. With best regards, > > Good Morning, > > > > On Fri, 2022-03-11 at 14:05 +1300, Ross Levis wrote: > > > Is there any method to do that on Windows? > > > > There is a reload link on the admin web interface on 2.5.x. > > > > It points to /admin/reloadconfig.xsl; if you want to do it > > programmatically you can just call /admin/reloadconfig with admin > > credentials. > > > > Reloading via API is not yet supported by 2.4.4. > > > > > > On 12 Mar 2022, at 8:20 pm, Tony Harding > > wrote: > > > > Was the windows question answered? > > > > > icecast2 ?HUP ????? > > > > Tony > > > > From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Ross > > Levis > > Sent: Friday, March 11, 2022 9:05 AM > > To: 'Icecast streaming server user discussions' > > Subject: Re: [Icecast] Icecast2 and SSL certificate renewal > > > > Is there any method to do that on Windows? > > > > From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf > > Of Alejandro Ferrari > > Sent: Friday, 11 March 2022 12:54 pm > > To: Icecast streaming server user discussions > > Subject: Re: [Icecast] Icecast2 and SSL certificate renewal > > > > Hi Damian, > > > > Kill -HUP $PID > > > > That will reload the config without stop the streams. > > > > El jue, 10 mar 2022 a la(s) 18:57, Damian (db76 at riseup.net) > > escribi?: > > > Hi > > > > > > I have a question about current best-practice for renewing SSL > > > certificates for Icecast. > > > I am looking into automating the renewal process for my SSL > > > certificate using Let?s Encrypt. > > > However, it?s my understanding that the Icecast server would need > > > to be restarted each time the automatic process takes place > > > (every 3 months) which I think would be disruptive to running a > > > continuous streaming service. > > > All the listeners would be kicked off the streams. > > > > > > I?d like to know if anyone knows of a better solution or if this > > > is just an unavoidable problem in terms of running streams via > > > HTTPS. -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From phschafft at de.loewenfelsen.net Mon Mar 14 10:59:18 2022 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Mon, 14 Mar 2022 10:59:18 +0000 Subject: [Icecast] Icecast 2.5 beta3 release Message-ID: Good morning, the Icecast Project is very pleased to have released the next beta of Icecast, version 2.5 beta3. As this is a beta usage in production should be with caution. Please see the full news entry linked below for details. New features (extract): * Overall * Improved relay configuration including multi-upstream support * Improved directory configuration including updated mechanism for listen URL submission * Updates to example configuration * Better warning about legacy operations * Improved client navigation including per-client history and improved handling of fallback overrides * Improved configuration validation warnings * Support for plain text streaming * New *experimental* JSON renderings * Web interface * Complete redesign * Support to move single listeners between sources * Logfile display on admin interface * New dashboard including overall health and maintenance information * Added new endpoint `/admin/publicstats` replacing `/status- json.xsl` which is now deprecated * Added stats key `display-title` to replace `title`, and `artist` * Warning about legacy sources on dashboard * Listing of listen sockets on admin interface * Advanced version display on admin interface * Protocol * Full `OPTIONS`, `POST`, and `DELETE` support * Addition of `no-store` to `Cache-Control:`-header. * Improved CORS support * Network * Support for new listen socket type `virtual` * Improved listen URL reporting * Per listen socket HTTP headers * Prefer IPv6 when IPv4-mapped is supported for listen sockets * Authentication * Per role matches: `match-web`, `nomatch-web`, `match-admin`, `nomatch-admin`, `match-method`, and `nomatch-method` * Per listen socket authentication * Client altering via authentication including redirection * Allow client altering on authentication fail and acl deny * New backend `enforce_auth` to improve performance with URL authentication Fixes and Cleanup (extract): * Several TLS related fixes * Several autotool related fixes and cleanup * Skip using poll() on Darwin * Detection of missing submodules in autogen.sh * Several locking related fixes * Several fixes for legacy metadata * Several memory leak fixes * Re-implemented `` and renamed to `` * Handle safe HTTP methods in unsafe context correctly * Improved logging messages * Not consider reuse of connections if they reached an error state Full news entry: https://icecast.org/news/icecast-release-2_5-beta3/ Download: http://downloads.xiph.org/releases/icecast/icecast-2.5-beta3.tar.gz SHA-2-256: e050e892803dcc10d88fc4403bf92e4c7699ea365804b4896625ff21815a096f SHA-3-512: e8af24dd1d593c5c3fa15d16c7b600ae5bcf9ee79678d79f952c44e28dad2430 78e9aa21837c6a229a0ba2bb3c6ca2147f2f4085966cfb32bd4cad52c5faffdb Experimental packages: https://build.opensuse.org/repositories/multimedia:xiph:beta Tickets and bug reports: https://gitlab.xiph.org/xiph/icecast-server/-/issues With best regards, -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From phschafft at de.loewenfelsen.net Tue Mar 15 09:50:27 2022 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Tue, 15 Mar 2022 09:50:27 +0000 Subject: [Icecast] Icecast2 and SSL certificate renewal In-Reply-To: <487A18D3-581B-43BF-B293-064592AAFD57@riseup.net> References: <254B0CD9-F8CD-491A-B7E6-DA7809C498B5@riseup.net> <00cb01d834e4$1a3c31d0$4eb49570$@com> <89ec76e2585356764c05fcff5eafdd597db8a428.camel@de.loewenfelsen.net> <487A18D3-581B-43BF-B293-064592AAFD57@riseup.net> Message-ID: <08ab21472b3e6d62179a07a775066c5f20a208c3.camel@de.loewenfelsen.net> Good morning, On Sat, 2022-03-12 at 17:57 +1000, Damian wrote: > Hi Philipp, > > Thanks for your reply. For now I will continue with 2.4.4 and just do > things manually, with an eye to using a more automated process when I > move over to version 2.5. > I realise that it is generally not recommended, but can you tell me > whether you think version 2.5 is generally stable enough to use for > production at this stage? now after our beta release I can finally answer you. ;) Generally speaking 2.5 is mostly stable. However it does not have the millions of hours of testing in tens of thousands of systems as 2.4. So I would recommend to have a look at it. It should work just fine for the majority of all users. > Also, is it recommended that we also follow the LinkedIn page at > https://www.linkedin.com/company/loewenfelsen/ for important info > about Icecast development? No and yes. Let me explain this a bit: Icecast is developed by the Icecast Team, as part of the Xiph.Org Foundation. Which for all important news uses the website and this mailing list. And this is how it will stay. However L?wenfelsen provides business support for the Foundation's software, most prominently Icecast. This is something the Foundation can hardly provide given it's community centric organisation. So at the page above you'll find *additional* stuff that L?wenfelsen provides. E.g. the presentations?. But this is additional content; there is nothing taken away from the Icecast Project, just more stuff added at another place with a slightly different target audience. Hope that clarifies things a bit. I'm sure it is a bit of confusing, also considering that I sometimes act in my role as (Icecast) developer at the Foundation, and sometimes as co-worker of L?wenfelsen. With best regards, > > On 11 Mar 2022, at 6:55 pm, Philipp Schafft < > > phschafft at de.loewenfelsen.net> wrote: > > > > Good Morning, > > > > On Fri, 2022-03-11 at 14:05 +1300, Ross Levis wrote: > > > Is there any method to do that on Windows? > > > > There is a reload link on the admin web interface on 2.5.x. > > > > It points to /admin/reloadconfig.xsl; if you want to do it > > programmatically you can just call /admin/reloadconfig with admin > > credentials. > > > > Reloading via API is not yet supported by 2.4.4. > > > > > > With best regards, > > > > > From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of > > > Alejandro Ferrari > > > Sent: Friday, 11 March 2022 12:54 pm > > > To: Icecast streaming server user discussions > > > Subject: Re: [Icecast] Icecast2 and SSL certificate renewal > > > > > > Hi Damian, > > > > > > Kill -HUP $PID > > > > > > That will reload the config without stop the streams. > > > > > > El jue, 10 mar 2022 a la(s) 18:57, Damian (db76 at riseup.net) > > > escribi?: > > > > Hi > > > > > > > > I have a question about current best-practice for renewing SSL > > > > certificates for Icecast. > > > > I am looking into automating the renewal process for my SSL > > > > certificate using Let?s Encrypt. > > > > However, it?s my understanding that the Icecast server would > > > > need > > > > to be restarted each time the automatic process takes place > > > > (every > > > > 3 months) which I think would be disruptive to running a > > > > continuous > > > > streaming service. > > > > All the listeners would be kicked off the streams. > > > > > > > > I?d like to know if anyone knows of a better solution or if > > > > this is > > > > just an unavoidable problem in terms of running streams via > > > > HTTPS. > > > > > > > > Thanks for any help > > > > ? Next one this Friday. -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From uktony at radiocompany.net Tue Mar 15 20:15:38 2022 From: uktony at radiocompany.net (Tony Harding) Date: Wed, 16 Mar 2022 04:15:38 +0800 Subject: [Icecast] libxml2 is required In-Reply-To: <08ab21472b3e6d62179a07a775066c5f20a208c3.camel@de.loewenfelsen.net> Message-ID: <20220315202300.B5A2E4025E@smtp4.osuosl.org> I have downloaded beta 3 and tried installing it on a spare Ubuntu VPS ? However is get the error in ./configure of: ? configure: error: . libxml2 is required. ? But if I then tell my server to install it, it says it is already there ? =================================================================== configure: error: . libxml2 is required. root at vs45:/icecast-2.4.99.3# apt install libxml2 Reading package lists... Done Building dependency tree Reading state information... Done libxml2 is already the newest version (2.9.10+dfsg-5ubuntu0.20.04.2). The following packages were automatically installed and are no longer required: linux-image-4.15.0-99-generic linux-modules-4.15.0-99-generic ssl-cert Use 'apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. =================================================================== ? How can I get configure to progress past this error? ? Ubuntu 20.04.4 icecast-2.4.99.3 ? Regards Tony ? ? -----Original Message----- From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Philipp Schafft Sent: Tuesday, March 15, 2022 5:50 PM To: Icecast streaming server user discussions Subject: Re: [Icecast] Icecast2 and SSL certificate renewal ? Good morning, ? On Sat, 2022-03-12 at 17:57 +1000, Damian wrote: > Hi Philipp, > > Thanks for your reply. For now I will continue with 2.4.4 and just do > things manually, with an eye to using a more automated process when I > move over to version 2.5. > I realise that it is generally not recommended, but can you tell me > whether you think version 2.5 is generally stable enough to use for > production at this stage? ? now after our beta release I can finally answer you. ;) ? Generally speaking 2.5 is mostly stable. However it does not have the millions of hours of testing in tens of thousands of systems as 2.4. So I would recommend to have a look at it. It should work just fine for the majority of all users. ? ? > Also, is it recommended that we also follow the LinkedIn page at > https://www.linkedin.com/company/loewenfelsen/ for important info > about Icecast development? ? No and yes. ? Let me explain this a bit: ? Icecast is developed by the Icecast Team, as part of the Xiph.Org Foundation. Which for all important news uses the website and this mailing list. And this is how it will stay. ? ? However L?wenfelsen provides business support for the Foundation's software, most prominently Icecast. This is something the Foundation can hardly provide given it's community centric organisation. ? So at the page above you'll find *additional* stuff that L?wenfelsen provides. E.g. the presentations?. But this is additional content; there is nothing taken away from the Icecast Project, just more stuff added at another place with a slightly different target audience. ? ? Hope that clarifies things a bit. I'm sure it is a bit of confusing, also considering that I sometimes act in my role as (Icecast) developer at the Foundation, and sometimes as co-worker of L?wenfelsen. ? ? With best regards, ? ? > > On 11 Mar 2022, at 6:55 pm, Philipp Schafft < > > phschafft at de.loewenfelsen.net> wrote: > > > > Good Morning, > > > > On Fri, 2022-03-11 at 14:05 +1300, Ross Levis wrote: > > > Is there any method to do that on Windows? > > > > There is a reload link on the admin web interface on 2.5.x. > > > > It points to /admin/reloadconfig.xsl; if you want to do it > > programmatically you can just call /admin/reloadconfig with admin > > credentials. > > > > Reloading via API is not yet supported by 2.4.4. > > > > > > With best regards, > > > > > From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of > > > Alejandro Ferrari > > > Sent: Friday, 11 March 2022 12:54 pm > > > To: Icecast streaming server user discussions > > > Subject: Re: [Icecast] Icecast2 and SSL certificate renewal > > > > > > Hi Damian, > > > > > > Kill -HUP $PID > > > > > > That will reload the config without stop the streams. > > > > > > El jue, 10 mar 2022 a la(s) 18:57, Damian (db76 at riseup.net) > > > escribi?: > > > > Hi > > > > > > > > I have a question about current best-practice for renewing SSL > > > > certificates for Icecast. > > > > I am looking into automating the renewal process for my SSL > > > > certificate using Let?s Encrypt. > > > > However, it?s my understanding that the Icecast server would > > > > need > > > > to be restarted each time the automatic process takes place > > > > (every > > > > 3 months) which I think would be disruptive to running a > > > > continuous > > > > streaming service. > > > > All the listeners would be kicked off the streams. > > > > > > > > I?d like to know if anyone knows of a better solution or if > > > > this is > > > > just an unavoidable problem in terms of running streams via > > > > HTTPS. > > > > > > > > Thanks for any help > > > > ? ? ? Next one this Friday. ? -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ ? L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sigfood at dinorama.fr Tue Mar 15 20:27:52 2022 From: sigfood at dinorama.fr (tTh) Date: Tue, 15 Mar 2022 21:27:52 +0100 Subject: [Icecast] libxml2 is required In-Reply-To: <20220315202300.B5A2E4025E@smtp4.osuosl.org> References: <20220315202300.B5A2E4025E@smtp4.osuosl.org> Message-ID: <088b5eda-113c-19c5-7be0-74ba781ed4aa@dinorama.fr> On 3/15/22 21:15, Tony Harding wrote: > I have downloaded beta 3 and tried installing it on a spare Ubuntu VPS > > ? > > However is get the error in ./configure of: > > ? > > configure: error: . libxml2 is required. > > ? > > But if I then tell my server to install it, it says it is already there > If you use Debian, search for the package named libxml2-dev. tTh -- +-------------------------------------------------------------------+ | sphinx of black quartz, judge my vow. | +-------------------------------------------------------------------+ From federico.miniussi at gmail.com Wed Mar 16 10:23:44 2022 From: federico.miniussi at gmail.com (Federico Miniussi) Date: Wed, 16 Mar 2022 11:23:44 +0100 Subject: [Icecast] Icecast 2.5 beta3 release In-Reply-To: References: Message-ID: Hello, is there any plan for a binary (windows systems) release for the beta 3 or shall I wait for the public release out of beta stage? Thank you Best regards Il giorno lun 14 mar 2022 alle ore 11:59 Philipp Schafft < phschafft at de.loewenfelsen.net> ha scritto: > Good morning, > > the Icecast Project is very pleased to have released the next beta > of Icecast, version 2.5 beta3. > > As this is a beta usage in production should be with caution. > > Please see the full news entry linked below for details. > > New features (extract): > > * Overall > * Improved relay configuration including multi-upstream support > * Improved directory configuration including updated mechanism for > listen URL submission > * Updates to example configuration > * Better warning about legacy operations > * Improved client navigation including per-client history and > improved handling of fallback overrides > * Improved configuration validation warnings > * Support for plain text streaming > * New *experimental* JSON renderings > * Web interface > * Complete redesign > * Support to move single listeners between sources > * Logfile display on admin interface > * New dashboard including overall health and maintenance > information > * Added new endpoint `/admin/publicstats` replacing `/status- > json.xsl` which is now deprecated > * Added stats key `display-title` to replace `title`, and `artist` > * Warning about legacy sources on dashboard > * Listing of listen sockets on admin interface > * Advanced version display on admin interface > * Protocol > * Full `OPTIONS`, `POST`, and `DELETE` support > * Addition of `no-store` to `Cache-Control:`-header. > * Improved CORS support > * Network > * Support for new listen socket type `virtual` > * Improved listen URL reporting > * Per listen socket HTTP headers > * Prefer IPv6 when IPv4-mapped is supported for listen sockets > * Authentication > * Per role matches: `match-web`, `nomatch-web`, `match-admin`, > `nomatch-admin`, `match-method`, and `nomatch-method` > * Per listen socket authentication > * Client altering via authentication including redirection > * Allow client altering on authentication fail and acl deny > * New backend `enforce_auth` to improve performance with URL > authentication > > Fixes and Cleanup (extract): > > * Several TLS related fixes > * Several autotool related fixes and cleanup > * Skip using poll() on Darwin > * Detection of missing submodules in autogen.sh > * Several locking related fixes > * Several fixes for legacy metadata > * Several memory leak fixes > * Re-implemented `` and renamed to `` > * Handle safe HTTP methods in unsafe context correctly > * Improved logging messages > * Not consider reuse of connections if they reached an error state > > Full news entry: > > https://icecast.org/news/icecast-release-2_5-beta3/ > > Download: > > http://downloads.xiph.org/releases/icecast/icecast-2.5-beta3.tar.gz > > SHA-2-256: > e050e892803dcc10d88fc4403bf92e4c7699ea365804b4896625ff21815a096f > SHA-3-512: > e8af24dd1d593c5c3fa15d16c7b600ae5bcf9ee79678d79f952c44e28dad2430 > 78e9aa21837c6a229a0ba2bb3c6ca2147f2f4085966cfb32bd4cad52c5faffdb > > Experimental packages: > https://build.opensuse.org/repositories/multimedia:xiph:beta > > Tickets and bug reports: > > https://gitlab.xiph.org/xiph/icecast-server/-/issues > > > With best regards, > > -- > Philipp Schafft (CEO/Gesch?ftsf?hrer) > Telephon: +49.3535 490 17 92 > Website: https://www.loewenfelsen.net/ > Follow us: https://www.linkedin.com/company/loewenfelsen/ > > L?wenfelsen UG (haftungsbeschr?nkt) Registration number: > Bickinger Stra?e 21 HRB 12308 CB > 04916 Herzberg (Elster) VATIN/USt-ID: > Germany DE305133015 > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chiapas at aktivix.org Wed Mar 16 10:55:19 2022 From: chiapas at aktivix.org (Chip) Date: Wed, 16 Mar 2022 10:55:19 +0000 Subject: [Icecast] Icecast support for HLS or MPEG-DASH Message-ID: Hi I do not know anything about the technical issues involved but would the Icecast developers ever consider support for streaming over HLS or MPEG-DASH ? Or is support for these protocols available now? HLS provides mechanisms for players to adapt to unreliable network conditions without causing playback stalling and I believe has some advantages in terms of low latency. Many thanks in advance Chip Scooter -------------- next part -------------- An HTML attachment was scrubbed... URL: From phschafft at de.loewenfelsen.net Wed Mar 16 12:57:35 2022 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Wed, 16 Mar 2022 12:57:35 +0000 Subject: [Icecast] Icecast 2.5 beta3 release In-Reply-To: References: Message-ID: Good afternoon, On Wed, 2022-03-16 at 11:23 +0100, Federico Miniussi wrote: > Hello, > is there any plan for a binary (windows systems) release for the beta > 3 or shall I wait for the public release out of beta stage? there actually are/will be as part of the packages: > Experimental packages: > https://build.opensuse.org/repositories/multimedia:xiph:beta I'm not fully sure about the status windows builds (not my personal domain). But I think there will be another post maybe next week about the packages. With best regards, > > Il giorno lun 14 mar 2022 alle ore 11:59 Philipp Schafft < > phschafft at de.loewenfelsen.net> ha scritto: > > Good morning, > > > > the Icecast Project is very pleased to have released the next beta > > of Icecast, version 2.5 beta3. > > > > As this is a beta usage in production should be with caution. > > > > Please see the full news entry linked below for details. > > > > New features (extract): > > > > * Overall > > * Improved relay configuration including multi-upstream support > > * Improved directory configuration including updated mechanism > > for > > listen URL submission > > * Updates to example configuration > > * Better warning about legacy operations > > * Improved client navigation including per-client history and > > improved handling of fallback overrides > > * Improved configuration validation warnings > > * Support for plain text streaming > > * New *experimental* JSON renderings > > * Web interface > > * Complete redesign > > * Support to move single listeners between sources > > * Logfile display on admin interface > > * New dashboard including overall health and maintenance > > information > > * Added new endpoint `/admin/publicstats` replacing `/status- > > json.xsl` which is now deprecated > > * Added stats key `display-title` to replace `title`, and > > `artist` > > * Warning about legacy sources on dashboard > > * Listing of listen sockets on admin interface > > * Advanced version display on admin interface > > * Protocol > > * Full `OPTIONS`, `POST`, and `DELETE` support > > * Addition of `no-store` to `Cache-Control:`-header. > > * Improved CORS support > > * Network > > * Support for new listen socket type `virtual` > > * Improved listen URL reporting > > * Per listen socket HTTP headers > > * Prefer IPv6 when IPv4-mapped is supported for listen sockets > > * Authentication > > * Per role matches: `match-web`, `nomatch-web`, `match-admin`, > > `nomatch-admin`, `match-method`, and `nomatch-method` > > * Per listen socket authentication > > * Client altering via authentication including redirection > > * Allow client altering on authentication fail and acl deny > > * New backend `enforce_auth` to improve performance with URL > > authentication > > > > Fixes and Cleanup (extract): > > > > * Several TLS related fixes > > * Several autotool related fixes and cleanup > > * Skip using poll() on Darwin > > * Detection of missing submodules in autogen.sh > > * Several locking related fixes > > * Several fixes for legacy metadata > > * Several memory leak fixes > > * Re-implemented `` and renamed to ` > access>` > > * Handle safe HTTP methods in unsafe context correctly > > * Improved logging messages > > * Not consider reuse of connections if they reached an error state > > > > Full news entry: > > > > https://icecast.org/news/icecast-release-2_5-beta3/ > > > > Download: > > > > > > http://downloads.xiph.org/releases/icecast/icecast-2.5-beta3.tar.gz > > > > SHA-2-256: > > e050e892803dcc10d88fc4403bf92e4c7699ea365804b4896625ff21815a096f > > SHA-3-512: > > e8af24dd1d593c5c3fa15d16c7b600ae5bcf9ee79678d79f952c44e28dad2430 > > 78e9aa21837c6a229a0ba2bb3c6ca2147f2f4085966cfb32bd4cad52c5faffdb > > > > Experimental packages: > > https://build.opensuse.org/repositories/multimedia:xiph:beta > > > > Tickets and bug reports: > > > > https://gitlab.xiph.org/xiph/icecast-server/-/issues -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From phschafft at de.loewenfelsen.net Wed Mar 16 13:05:18 2022 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Wed, 16 Mar 2022 13:05:18 +0000 Subject: [Icecast] Next presentation: Load balancing with Round-robin DNS Message-ID: <33666eff18f403bbf395f18527a1b7f800e3ef96.camel@de.loewenfelsen.net> Good afternoon, we have _two_ empty seats left for our next presentation this Friday at 15:00 UTC. If you are interested please write me off-list. We will then reply if you have been fast and lucky or not. Details: https://www.linkedin.com/events/loadbalancingwithround-robindns6907625550580719616/about/ With best regards, -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From fredg at paravelsystems.com Wed Mar 16 14:14:45 2022 From: fredg at paravelsystems.com (Fred Gleason) Date: Wed, 16 Mar 2022 10:14:45 -0400 Subject: [Icecast] Icecast support for HLS or MPEG-DASH In-Reply-To: References: Message-ID: <45CF571B-168A-49F6-AF7C-50731E58F82D@paravelsystems.com> On Mar 16, 2022, at 06:55, Chip wrote: > I do not know anything about the technical issues involved but would the Icecast developers ever consider support for streaming over HLS or MPEG-DASH ? Or is support for these protocols available now? > > HLS provides mechanisms for players to adapt to unreliable network conditions without causing playback stalling and I believe has some advantages in terms of low latency. The main advantage of HLS/DASH _vis-a-vis_ the ICY/ice protocols is that they are *much* more CDN-friendly. If you?re needing to reach an audience of millions, then HLS/DASH is what you need to be using (along with an appropriately scaled CDN). The way that HLS/DASH achieves that is by pushing design complexity from the ?server? to the encoder and player components. The ?server? part of an HLS/DASH setup is, relatively speaking, dead simple. In fact, one can build a perfectly usable HLS ?server? using stock Apache httpd. I cannot of course speak for the Icecast developers, but FWIW I?d be frankly shocked to see HLS/DASH support ever happen in Icecast. Cheers! |---------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |---------------------------------------------------------------------| | A room without books is like a body without a soul. | | | | -- Cicero | |---------------------------------------------------------------------| -------------- next part -------------- An HTML attachment was scrubbed... URL: From chiapas at aktivix.org Wed Mar 16 19:08:52 2022 From: chiapas at aktivix.org (Chip) Date: Wed, 16 Mar 2022 19:08:52 +0000 Subject: [Icecast] Icecast support for HLS or MPEG-DASH In-Reply-To: <45CF571B-168A-49F6-AF7C-50731E58F82D@paravelsystems.com> References: <45CF571B-168A-49F6-AF7C-50731E58F82D@paravelsystems.com> Message-ID: Thank you very much, Fred! Very useful, indeed. On Wed, 16 Mar 2022 at 14:15, Fred Gleason wrote: > > I cannot of course speak for the Icecast developers, but FWIW I?d be > frankly shocked to see HLS/DASH support ever happen in Icecast. > And may I ask why you would be so shocked if support for HLS/DASH ever came to Icecast? Is it because they are proprietary protocols? But Icecast has support for MP3 and AAC. Many thanks Chip Scooter -------------- next part -------------- An HTML attachment was scrubbed... URL: From fredg at paravelsystems.com Wed Mar 16 20:20:22 2022 From: fredg at paravelsystems.com (Fred Gleason) Date: Wed, 16 Mar 2022 16:20:22 -0400 Subject: [Icecast] Icecast support for HLS or MPEG-DASH In-Reply-To: References: <45CF571B-168A-49F6-AF7C-50731E58F82D@paravelsystems.com> Message-ID: <394D5293-311E-45FB-860E-47F4708C5071@paravelsystems.com> On Mar 16, 2022, at 15:08, Chip wrote: > And may I ask why you would be so shocked if support for HLS/DASH ever came to Icecast? Because they are two completely different animals. It would be like comparing a mountain lion to a dolphin. There?re both mammals, but otherwise designed for totally different environments. > Is it because they are proprietary protocols? But Icecast has support for MP3 and AAC. The audio codecs are the same, yes. The transports however are utterly different. ICY/ice delivers a single sequential bitstream to each player. That makes the encoder and player relatively simple and easy to implement, but means that you need a fairly complex ?stream splitter? (for lack of a better term) between them to create and manage a separate, unicast bitstream copy for each player. That?s the role that Icecast and its brethren fulfill. OTOH, HLS/DASH takes that bitstream and splits it into segments of a given length (10 secs/segment is typical) and then posts each segment to a web server. Players download those segments, reassemble them into the original bitstream and then render the content. Since all of this segmentation and reassembly takes place at the endpoints, it makes both the encoder and the player *much* more complex. The advantage though is that the server then can be an ordinary ?garden variety? web server, because all you?re doing from the server POV is posting and downloading files. Such files are straightforward to replicate through a CDN, using the same methods that are already well established for replicating web content, whereas for ICY/ice streams you need special server software ?e.g. the ?relay? functionality in Icecast. Cheers! |---------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |---------------------------------------------------------------------| | A room without books is like a body without a soul. | | | | -- Cicero | |---------------------------------------------------------------------| -------------- next part -------------- An HTML attachment was scrubbed... URL: From chiapas at aktivix.org Wed Mar 16 20:51:45 2022 From: chiapas at aktivix.org (Chip) Date: Wed, 16 Mar 2022 20:51:45 +0000 Subject: [Icecast] Icecast support for HLS or MPEG-DASH In-Reply-To: <394D5293-311E-45FB-860E-47F4708C5071@paravelsystems.com> References: <45CF571B-168A-49F6-AF7C-50731E58F82D@paravelsystems.com> <394D5293-311E-45FB-860E-47F4708C5071@paravelsystems.com> Message-ID: Thank you very much, Fred - that's very helpful. Chip Scooter On Wed, 16 Mar 2022 at 20:20, Fred Gleason wrote: > On Mar 16, 2022, at 15:08, Chip wrote: > > And may I ask why you would be so shocked if support for HLS/DASH ever > came to Icecast? > > > Because they are two completely different animals. It would be like > comparing a mountain lion to a dolphin. There?re both mammals, but > otherwise designed for totally different environments. > > > Is it because they are proprietary protocols? But Icecast has support for > MP3 and AAC. > > > The audio codecs are the same, yes. The transports however are utterly > different. > > ICY/ice delivers a single sequential bitstream to each player. That makes > the encoder and player relatively simple and easy to implement, but means > that you need a fairly complex ?stream splitter? (for lack of a better > term) between them to create and manage a separate, unicast bitstream copy > for each player. That?s the role that Icecast and its brethren fulfill. > > OTOH, HLS/DASH takes that bitstream and splits it into segments of a given > length (10 secs/segment is typical) and then posts each segment to a web > server. Players download those segments, reassemble them into the original > bitstream and then render the content. Since all of this segmentation and > reassembly takes place at the endpoints, it makes both the encoder and the > player *much* more complex. The advantage though is that the server then > can be an ordinary ?garden variety? web server, because all you?re doing > from the server POV is posting and downloading files. Such files are > straightforward to replicate through a CDN, using the same methods that are > already well established for replicating web content, whereas for ICY/ice > streams you need special server software ?e.g. the ?relay? functionality in > Icecast. > > Cheers! > > > |---------------------------------------------------------------------| > | Frederick F. Gleason, Jr. | Chief Developer | > | | Paravel Systems | > |---------------------------------------------------------------------| > | A room without books is like a body without a soul. | > | | > | -- Cicero | > |---------------------------------------------------------------------| > -------------- next part -------------- An HTML attachment was scrubbed... URL: From uktony at radiocompany.net Wed Mar 16 08:21:45 2022 From: uktony at radiocompany.net (Tony Harding) Date: Wed, 16 Mar 2022 16:21:45 +0800 Subject: [Icecast] FW: libxml2 is required Message-ID: <20220316082150.D4AEB60F03@smtp3.osuosl.org> ? ? ? Naaaaaaaaa That did not work ? LIBXML2-DEV is already there ? root at vs45:/# apt install libxml2-dev Reading package lists... Done Building dependency tree Reading state information... Done libxml2-dev is already the newest version (2.9.10+dfsg-5ubuntu0.20.04.2). libxml2-dev set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root at vs45:/# ? ? _____ From: Dave Pascoe [mailto:davekm3t at gmail.com] Sent: Wednesday, March 16, 2022 4:25 AM To: uktony at radiocompany.net Subject: Re: [Icecast] libxml2 is required ? apt install libxml2-dev ? On Mar 15, 2022, at 4:23 PM, Tony Harding wrote: ? I have downloaded beta 3 and tried installing it on a spare Ubuntu VPS ? However is get the error in ./configure of: ? ? ? ? ? ? configure: error: . libxml2 is required. ? But if I then tell my server to install it, it says it is already there ? ? =================================================================== configure: error: . libxml2 is required. root at vs45:/icecast-2.4.99.3# apt install libxml2 Reading package lists... Done Building dependency tree Reading state information... Done libxml2 is already the newest version (2.9.10+dfsg-5ubuntu0.20.04.2). The following packages were automatically installed and are no longer required: ? linux-image-4.15.0-99-generic linux-modules-4.15.0-99-generic ssl-cert Use 'apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. =================================================================== ? How can I get configure to progress past this error? ? Ubuntu 20.04.4 icecast-2.4.99.3 ? Regards Tony ? ? -----Original Message----- From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Philipp Schafft Sent: Tuesday, March 15, 2022 5:50 PM To: Icecast streaming server user discussions Subject: Re: [Icecast] Icecast2 and SSL certificate renewal ? Good morning, ? On Sat, 2022-03-12 at 17:57 +1000, Damian wrote: > Hi Philipp, > > Thanks for your reply. For now I will continue with 2.4.4 and just do > things manually, with an eye to using a more automated process when I > move over to version 2.5. > I realise that it is generally not recommended, but can you tell me > whether you think version 2.5 is generally stable enough to use for > production at this stage? ? now after our beta release I can finally answer you. ;) ? Generally speaking 2.5 is mostly stable. However it does not have the millions of hours of testing in tens of thousands of systems as 2.4. So I would recommend to have a look at it. It should work just fine for the majority of all users. ? ? > Also, is it recommended that we also follow the LinkedIn page at > https://www.linkedin.com/company/loewenfelsen/ for important info > about Icecast development? ? No and yes. ? Let me explain this a bit: ? Icecast is developed by the Icecast Team, as part of the Xiph.Org Foundation. Which for all important news uses the website and this mailing list. And this is how it will stay. ? ? However L?wenfelsen provides business support for the Foundation's software, most prominently Icecast. This is something the Foundation can hardly provide given it's community centric organisation. ? So at the page above you'll find *additional* stuff that L?wenfelsen provides. E.g. the presentations?. But this is additional content; there is nothing taken away from the Icecast Project, just more stuff added at another place with a slightly different target audience. ? ? Hope that clarifies things a bit. I'm sure it is a bit of confusing, also considering that I sometimes act in my role as (Icecast) developer at the Foundation, and sometimes as co-worker of L?wenfelsen. ? ? With best regards, ? ? > > On 11 Mar 2022, at 6:55 pm, Philipp Schafft < > > phschafft at de.loewenfelsen.net> wrote: > > > > Good Morning, > > > > On Fri, 2022-03-11 at 14:05 +1300, Ross Levis wrote: > > > Is there any method to do that on Windows? > > > > There is a reload link on the admin web interface on 2.5.x. > > > > It points to /admin/reloadconfig.xsl; if you want to do it > > programmatically you can just call /admin/reloadconfig with admin > > credentials. > > > > Reloading via API is not yet supported by 2.4.4. > > > > > > With best regards, > > > > > From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of > > > Alejandro Ferrari > > > Sent: Friday, 11 March 2022 12:54 pm > > > To: Icecast streaming server user discussions > > > Subject: Re: [Icecast] Icecast2 and SSL certificate renewal > > > > > > Hi Damian, > > > > > > Kill -HUP $PID > > > > > > That will reload the config without stop the streams. > > > > > > El jue, 10 mar 2022 a la(s) 18:57, Damian (db76 at riseup.net) > > > escribi?: > > > > Hi > > > > > > > > I have a question about current best-practice for renewing SSL > > > > certificates for Icecast. > > > > I am looking into automating the renewal process for my SSL > > > > certificate using Let?s Encrypt. > > > > However, it?s my understanding that the Icecast server would > > > > need > > > > to be restarted each time the automatic process takes place > > > > (every > > > > 3 months) which I think would be disruptive to running a > > > > continuous > > > > streaming service. > > > > All the listeners would be kicked off the streams. > > > > > > > > I?d like to know if anyone knows of a better solution or if > > > > this is > > > > just an unavoidable problem in terms of running streams via > > > > HTTPS. > > > > > > > > Thanks for any help > > > > ? ? ? Next one this Friday. ? -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: ? +49.3535 490 17 92 Website: ? ? https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ ? L?wenfelsen UG (haftungsbeschr?nkt) ? ? ? ? Registration number: Bickinger Stra?e 21 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? HRB 12308 CB 04916 Herzberg (Elster) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? VATIN/USt-ID: Germany ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? DE305133015 _______________________________________________ Icecast mailing list Icecast at xiph.org http://lists.xiph.org/mailman/listinfo/icecast -------------- next part -------------- An HTML attachment was scrubbed... URL: From epirat07 at gmail.com Sun Mar 20 20:59:15 2022 From: epirat07 at gmail.com (Marvin Scholz) Date: Sun, 20 Mar 2022 21:59:15 +0100 Subject: [Icecast] libxml2 is required In-Reply-To: <20220316082150.D4AEB60F03@smtp3.osuosl.org> References: <20220316082150.D4AEB60F03@smtp3.osuosl.org> Message-ID: Hi, please avoid including all the past emails in your replies, as it makes your emails huge and mailman blocks them. Please attach your config.log after you ran ./configure. configure uses pkg-config to look for the libxml2.pc file in the default pkgconfig search paths. On 16 Mar 2022, at 9:21, Tony Harding wrote: > ? > > ? > > ? > > Naaaaaaaaa > > That did not work > > ? > > LIBXML2-DEV is already there > > ? > > root at vs45:/# apt install libxml2-dev > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > libxml2-dev is already the newest version (2.9.10+dfsg-5ubuntu0.20.04.2). > > libxml2-dev set to manually installed. > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > root at vs45:/# > > ? > > ? > > _____ From rlbart53 at gmail.com Tue Mar 22 11:45:22 2022 From: rlbart53 at gmail.com (Richard Bartholomew) Date: Tue, 22 Mar 2022 11:45:22 -0000 Subject: [Icecast] SOCKET TIMEOUTTTT Message-ID: <00c201d83de2$50916a00$f1b43e00$@gmail.com> Hi, We're running V2.4.4 on Ubuntu 21.0. Last night, whilst one of our presenters was broadcasting their show, they were disconnected and unable to re-connect for around five minutes and kept getting the message that they were connected even though they weren't but our fallback autodj system was successfully playing during that period! I found the following message in the error log for the time in question and wonder if anyone can advise me, please, on what I need to do to prevent this in the future...as far as I'm aware, it's the first time it has happened! WARN source/get_next_buffer Disconnecting source due to socket timeout Thanks for any help with this. Richard Bartholomew -------------- next part -------------- An HTML attachment was scrubbed... URL: From phschafft at de.loewenfelsen.net Tue Mar 22 12:14:48 2022 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Tue, 22 Mar 2022 12:14:48 +0000 Subject: [Icecast] SOCKET TIMEOUTTTT In-Reply-To: <00c201d83de2$50916a00$f1b43e00$@gmail.com> References: <00c201d83de2$50916a00$f1b43e00$@gmail.com> Message-ID: Good afternoon, On Tue, 2022-03-22 at 11:45 +0000, Richard Bartholomew wrote: > Hi, > > We're running V2.4.4 on Ubuntu 21.0. > > Last night, whilst one of our presenters was broadcasting their show, > they were disconnected and unable to re-connect for around five > minutes and kept getting the message that they were connected even > though they weren't but our fallback autodj system was successfully > playing during that period! > > I found the following message in the error log for the time in > question and wonder if anyone can advise me, please, on what I need > to do to prevent this in the future...as far as I'm aware, it's the > first time it has happened! > > WARN source/get_next_buffer Disconnecting source due to socket > timeout > > Thanks for any help with this. generally speaking the above warning is reported if a source does stop sending data. Normally this indicates that there is one of a) something wrong with the source client, b) some network problem. Generally speaking if nobody altered the source client it is b). Which I would also feel like it likely is that because of it taking a few minutes to recover but not too long. If it does not happen again I would just consider it a random network hiccup. However if you feel like there really needs to be something done about it there are a few first things to look at. Order and importance of the items really depend on your parameters: * Network quality (e.g. wired, not wireless), maybe some line provider that offers a availability focused SLA * Training for all involved admins (e.g. to learn if an software update may have an impact or not), keeping all teams informed on maintenance, ... * Redundancy. Which may include a second source client but also a second line. Hope that helps. :) With best regards, -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: From railgun.michael at gmail.com Tue Mar 22 12:59:34 2022 From: railgun.michael at gmail.com (Railgun) Date: Tue, 22 Mar 2022 13:59:34 +0100 Subject: [Icecast] SOCKET TIMEOUTTTT In-Reply-To: References: <00c201d83de2$50916a00$f1b43e00$@gmail.com> Message-ID: If that happen I normaly switch to another Data Center (with a vpn or a backup icecast with slave/connection to main) to reroute the traffic of my broadcast from home This normaly Helps to avoid network botlneks id the outgoing traffic from home use another Patch then default. Philipp Schafft schrieb am Di., 22. M?rz 2022, 13:15: > Good afternoon, > > On Tue, 2022-03-22 at 11:45 +0000, Richard Bartholomew wrote: > > Hi, > > > > We're running V2.4.4 on Ubuntu 21.0. > > > > Last night, whilst one of our presenters was broadcasting their show, > > they were disconnected and unable to re-connect for around five > > minutes and kept getting the message that they were connected even > > though they weren't but our fallback autodj system was successfully > > playing during that period! > > > > I found the following message in the error log for the time in > > question and wonder if anyone can advise me, please, on what I need > > to do to prevent this in the future...as far as I'm aware, it's the > > first time it has happened! > > > > WARN source/get_next_buffer Disconnecting source due to socket > > timeout > > > > Thanks for any help with this. > > generally speaking the above warning is reported if a source does stop > sending data. Normally this indicates that there is one of a) something > wrong with the source client, b) some network problem. > > Generally speaking if nobody altered the source client it is b). Which > I would also feel like it likely is that because of it taking a few > minutes to recover but not too long. > > > If it does not happen again I would just consider it a random network > hiccup. > > > However if you feel like there really needs to be something done about > it there are a few first things to look at. Order and importance of the > items really depend on your parameters: > * Network quality (e.g. wired, not wireless), maybe some line provider > that offers a availability focused SLA > * Training for all involved admins (e.g. to learn if an software > update may have an impact or not), keeping all teams informed on > maintenance, ... > * Redundancy. Which may include a second source client but also a > second line. > > > Hope that helps. :) > > With best regards, > > -- > Philipp Schafft (CEO/Gesch?ftsf?hrer) > Telephon: +49.3535 490 17 92 > Website: https://www.loewenfelsen.net/ > Follow us: https://www.linkedin.com/company/loewenfelsen/ > > L?wenfelsen UG (haftungsbeschr?nkt) Registration number: > Bickinger Stra?e 21 HRB 12308 CB > 04916 Herzberg (Elster) VATIN/USt-ID: > Germany DE305133015 > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tombones at 440music.com Wed Mar 23 17:50:52 2022 From: tombones at 440music.com (Tommy TBones Cramer) Date: Wed, 23 Mar 2022 12:50:52 -0500 Subject: [Icecast] SOCKET TIMEOUTTTT In-Reply-To: References: <00c201d83de2$50916a00$f1b43e00$@gmail.com> Message-ID: <52df07c9-c3a6-263c-4e77-643dd08c9caa@440music.com> the issue is that when logged in there is a default time out usually set for 600 seconds/5 minutes before inactivity disconnects the user. check the config file for Time-Out or Inactivity setting I also agree that it sounds like a network hickup On 3/22/22 07:14, Philipp Schafft wrote: > Good afternoon, > > On Tue, 2022-03-22 at 11:45 +0000, Richard Bartholomew wrote: >> Hi, >> >> We're running V2.4.4 on Ubuntu 21.0. >> >> Last night, whilst one of our presenters was broadcasting their show, >> they were disconnected and unable to re-connect for around five >> minutes and kept getting the message that they were connected even >> though they weren't but our fallback autodj system was successfully >> playing during that period! >> >> I found the following message in the error log for the time in >> question and wonder if anyone can advise me, please, on what I need >> to do to prevent this in the future...as far as I'm aware, it's the >> first time it has happened! >> >> WARN source/get_next_buffer Disconnecting source due to socket >> timeout >> >> Thanks for any help with this. > generally speaking the above warning is reported if a source does stop > sending data. Normally this indicates that there is one of a) something > wrong with the source client, b) some network problem. > > Generally speaking if nobody altered the source client it is b). Which > I would also feel like it likely is that because of it taking a few > minutes to recover but not too long. > > > If it does not happen again I would just consider it a random network > hiccup. > > > However if you feel like there really needs to be something done about > it there are a few first things to look at. Order and importance of the > items really depend on your parameters: > * Network quality (e.g. wired, not wireless), maybe some line provider > that offers a availability focused SLA > * Training for all involved admins (e.g. to learn if an software > update may have an impact or not), keeping all teams informed on > maintenance, ... > * Redundancy. Which may include a second source client but also a > second line. > > > Hope that helps. :) > > With best regards, > > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast -- Tommy TBones Cramer Owner 440Music Entertainment Co www.440music.com 773 491 9937 599 365 0104 Zoom t440Music Skype From mph at emotrics.com Fri Mar 25 23:24:18 2022 From: mph at emotrics.com (Milton Huang) Date: Fri, 25 Mar 2022 16:24:18 -0700 Subject: [Icecast] log rotation Message-ID: I've been having some issues on a new server I set up with the names of my access.log and error.log files. I use the default names access.log error.log And the logs are created properly, but with names access.log.1 and error.log.1. access.log and error.log are present, but always zero length. This didn't happen with my last server (although that was with version 2.4.4 and I'm now using source compiled 2.4.99.2 adding in Commit 52634884 that Fixes EPIPEs on TLS clients). The only other change was I added a line: delaycompress to the logrotate.d/icecast file as I need to be able to read the last two files and didn't want error.log.1 to be compressed. Is this a bug, or am I missing something basic about log rotation? -milton -------------- next part -------------- An HTML attachment was scrubbed... URL: