From lfernandez at nrj.fr Thu Jul 2 08:17:47 2020
From: lfernandez at nrj.fr (Lisardo FERNANDEZ)
Date: Thu, 2 Jul 2020 08:17:47 +0000
Subject: [Icecast] Integration of VAST Plugin
Message-ID: <216984a2-5c63-49a8-53b6-f09a874a76cc@nrj.fr>
Hello,
icecast provides something like a plugin for vast ads system?
Or we have to custom parse the xml and create some playlist to add a
preroll mp3 to another stream live?
Thanks.
BR
From jayaubs89 at gmail.com Thu Jul 2 14:00:14 2020
From: jayaubs89 at gmail.com (Hottunez Radio)
Date: Thu, 2 Jul 2020 15:00:14 +0100
Subject: [Icecast] Integration of VAST Plugin
In-Reply-To: <216984a2-5c63-49a8-53b6-f09a874a76cc@nrj.fr>
References: <216984a2-5c63-49a8-53b6-f09a874a76cc@nrj.fr>
Message-ID: <CAJQJMxqB6Kaa351GjYupehCo7Q+1m0Xb9EBktSVtRi-n0RRM7g@mail.gmail.com>
hello Lisardo and Icecast i'm enquiring about this icecast streaming
now does it come with a control panel so we can add autodj to it or how
does it work
On Thu, Jul 2, 2020 at 9:32 AM Lisardo FERNANDEZ <lfernandez at nrj.fr> wrote:
> Hello,
>
> icecast provides something like a plugin for vast ads system?
>
> Or we have to custom parse the xml and create some playlist to add a
> preroll mp3 to another stream live?
>
> Thanks.
>
> BR
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200702/1f1c38d6/attachment.htm>
From pm at nowster.me.uk Thu Jul 2 16:26:29 2020
From: pm at nowster.me.uk (Paul Martin)
Date: Thu, 2 Jul 2020 17:26:29 +0100
Subject: [Icecast] Integration of VAST Plugin
In-Reply-To: <216984a2-5c63-49a8-53b6-f09a874a76cc@nrj.fr>
References: <216984a2-5c63-49a8-53b6-f09a874a76cc@nrj.fr>
Message-ID: <20200702162629.GB109269@thinkpad.nowster.org.uk>
On Thu, Jul 02, 2020 at 08:17:47AM +0000, Lisardo FERNANDEZ wrote:
> icecast provides something like a plugin for vast ads system?
You're best doing that in whatever tool is feeding the stream to
Icecast.
--
Paul Martin <pm at nowster.me.uk>
From yahav.shasha at gmail.com Thu Jul 2 16:49:42 2020
From: yahav.shasha at gmail.com (Yahav Shasha)
Date: Thu, 2 Jul 2020 19:49:42 +0300
Subject: [Icecast] Integration of VAST Plugin
In-Reply-To: <20200702162629.GB109269@thinkpad.nowster.org.uk>
References: <216984a2-5c63-49a8-53b6-f09a874a76cc@nrj.fr>
<20200702162629.GB109269@thinkpad.nowster.org.uk>
Message-ID: <CABuab=Q_Akio5diW1K1imdpfsc=pDW1AibyDqnWyWdFQRL0JBg@mail.gmail.com>
As far as I know, the most common practice is handling the ads insertment
at the client side. eg. at the player level.
I know that videojs got a vast plugin:
https://github.com/googleads/videojs-ima
as well as JWPlayer:
https://developer.jwplayer.com/jwplayer/docs/jw8-advertising
However this method has one drawback, Adblock addons will target most VAST
requests and disable the advertisements..
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200702/bb39e7aa/attachment.htm>
From lfernandez at nrj.fr Thu Jul 2 17:07:45 2020
From: lfernandez at nrj.fr (Lisardo FERNANDEZ)
Date: Thu, 2 Jul 2020 17:07:45 +0000
Subject: [Icecast] Integration of VAST Plugin
In-Reply-To: <CABuab=Q_Akio5diW1K1imdpfsc=pDW1AibyDqnWyWdFQRL0JBg@mail.gmail.com>
References: <216984a2-5c63-49a8-53b6-f09a874a76cc@nrj.fr>
<20200702162629.GB109269@thinkpad.nowster.org.uk>,
<CABuab=Q_Akio5diW1K1imdpfsc=pDW1AibyDqnWyWdFQRL0JBg@mail.gmail.com>
Message-ID: <DBAPR02MB6055C5A12EF582D2DD21F8E8AD6D0@DBAPR02MB6055.eurprd02.prod.outlook.com>
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200702/74c8164a/attachment.htm>
From pm at nowster.me.uk Thu Jul 2 17:08:59 2020
From: pm at nowster.me.uk (Paul Martin)
Date: Thu, 2 Jul 2020 18:08:59 +0100
Subject: [Icecast] SSL-Question
In-Reply-To: <20200630200512.GC24774@album.bayer.uni.cx>
References: <20200627161311.GB12200@thinkpad.nowster.org.uk>
<CABDatARfqHJio=6E_DzoJ=GcCXyYYnOLdWpBBKS1-QUZSAxDPg@mail.gmail.com>
<20200627223637.GA330071@thinkpad.nowster.org.uk>
<CABDatATB7xLksjDw7+ErSNTsM5wdpNMvsJcK0uyXCgg41zaMQg@mail.gmail.com>
<20200628180520.GA391553@thinkpad.nowster.org.uk>
<CABDatAR08fPGfMvcqfp6gw=bmH7pw-JskbG0VKLLSMAoQ2tK4Q@mail.gmail.com>
<CAOUVwuuLXT5MpgtNeq9bO-gvvJyWZaB09jYqB3QTJ-Lpizb8WQ@mail.gmail.com>
<CABDatASM5k9+ECFLsobAKGw=zYOMejHax_sbeu3Xi1TcQ0PfxA@mail.gmail.com>
<20200629092609.GB440325@thinkpad.nowster.org.uk>
<20200630200512.GC24774@album.bayer.uni.cx>
Message-ID: <20200702170859.GC109269@thinkpad.nowster.org.uk>
On Tue, Jun 30, 2020 at 10:05:12PM +0200, Petr Pisar wrote:
> > HTTPS only works with domain names, and the client checks the
> > certificate it sees against the site name it is connecting to.
> >
> An X.509 certicate can be issued for an IP address.
That won't work for public use with https, though.
--
Paul Martin <pm at nowster.me.uk>
From pm at nowster.me.uk Thu Jul 2 17:15:52 2020
From: pm at nowster.me.uk (Paul Martin)
Date: Thu, 2 Jul 2020 18:15:52 +0100
Subject: [Icecast] Integration of VAST Plugin
In-Reply-To: <DBAPR02MB6055C5A12EF582D2DD21F8E8AD6D0@DBAPR02MB6055.eurprd02.prod.outlook.com>
References: <216984a2-5c63-49a8-53b6-f09a874a76cc@nrj.fr>
<20200702162629.GB109269@thinkpad.nowster.org.uk>
<CABuab=Q_Akio5diW1K1imdpfsc=pDW1AibyDqnWyWdFQRL0JBg@mail.gmail.com>
<DBAPR02MB6055C5A12EF582D2DD21F8E8AD6D0@DBAPR02MB6055.eurprd02.prod.outlook.com>
Message-ID: <20200702171552.GD109269@thinkpad.nowster.org.uk>
Icecast has never been good at serving up static playlists, and
changing playlists requires reloading the server, potentially dropping
any connected clients. Either that or they won't see the changed
playlist anyway.
Get yourself a program which can feed a stream into Icecast and you
can control that program however you like.
--
Paul Martin <pm at nowster.me.uk>
From geoff at QuiteLikely.com Thu Jul 2 20:27:02 2020
From: geoff at QuiteLikely.com (Geoff Shang)
Date: Thu, 2 Jul 2020 23:27:02 +0300 (IDT)
Subject: [Icecast] Integration of VAST Plugin
In-Reply-To: <20200702162629.GB109269@thinkpad.nowster.org.uk>
References: <216984a2-5c63-49a8-53b6-f09a874a76cc@nrj.fr>
<20200702162629.GB109269@thinkpad.nowster.org.uk>
Message-ID: <alpine.DEB.2.11.2007022322510.38411@debian.work>
On Thu, 2 Jul 2020, Paul Martin wrote:
> You're best doing that in whatever tool is feeding the stream to
> Icecast.
the problem is that the poster wants the ad to play to the person who is
connecting, not to every listener. And presumably they want that ad to be
different based on some kind of characteristics of the connecting person
(i.e. it's not going to be the same for everyone).
I don't know anything about VAST, but maybe you could use the auth
mechanisms to do something.
Cheers,
Geoff.
From ajl379 at gmail.com Mon Jul 6 01:12:51 2020
From: ajl379 at gmail.com (Andy Ludowese)
Date: Sun, 5 Jul 2020 20:12:51 -0500
Subject: [Icecast] htpasswd authentication
Message-ID: <CAHhPv0P7-KY=Oce_Ui9gkA9bd0gwjV4hVJiNv+bkz8=b-ecMhQ@mail.gmail.com>
Hi,
I am configuring Icecast2 on a Windows 10 machine and have been struggling
with getting the htpasswd section configured correctly. I have a file path
where the user credentials should be saved in. My issue is when I open the
Web Admin page, the mount doesn't show the "Manage authentication"
hyperlink so I can add users. I will send in my config file if that will
help.
I am not sure if I forgot to include any other information.
Thanks for your help in advance,
Andy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200705/796545fc/attachment.htm>
From db76 at riseup.net Fri Jul 10 22:09:23 2020
From: db76 at riseup.net (Damian)
Date: Sat, 11 Jul 2020 08:09:23 +1000
Subject: [Icecast] Installing ice cast with SSL support
Message-ID: <5EA871D6-7058-4F2A-8FA2-A7DBC5C3B2BA@riseup.net>
Hi,
My question is specific to installing a version of Icecast2 with support for SSL. Of course I still need to configure the config file with the certificate later, but I?ve read that installing icecast from the xiph repositories at download.opensouse would get me a version with SSL support?doing ...
sudo sh -c "echo deb http://download.opensuse.org/repositories/multimedia:/xiph/Debian_10/ ./ >>/etc/apt/sources.list.d/icecast.list"
wget -qO - http://download.opensuse.org/repositories/multimedia:/xiph/Debian_10/Release.key | sudo apt-key add -
I?ve also read a different thread that says I need to build it myself like below
wget http://downloads.xiph.org/releases/icecast/icecast-2.4.4.tar.gz
tar xvf icecast-2.4.4.tar.gz
cd icecast-2.4.4
./configure --prefix=/usr/serverok/icecast --with-curl --with-openssl
If the first option is indeed possible I would prefer that. Can anyone confirm it is possible?
Damian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200711/b199ce98/attachment.htm>
From 2qopz9602 at sneakemail.com Sun Jul 12 18:25:20 2020
From: 2qopz9602 at sneakemail.com (axeon)
Date: Sun, 12 Jul 2020 18:25:20 +0000
Subject: [Icecast] Linux source-client that can push AAC to icecast2?
Message-ID: <23069-1594578320-876806@sneakemail.com>
Hi all, I set up ezstream to read a playlist.m3u file containing only MP3 encoded songs (to shuffle continuously) and push this to icecast2. This works, and I can also reencode to a lower bitrate.
I would like to know if there is a way to reencode these MP3s into AAC-LC 128kpbs and then push the stream to icecast2. I'm doing this on a VM with only terminal access and no audio hardware, so ezstream was perfect because it could just read MP3s and send it over, but it does not support AAC. I've looked at all the other source clients on the icecast website, but could not find anything that could work with AAC. I'm not good enough with Linux to recompile stuff (have run into errors on clean cloud Linux VMs), so was hoping there were packages unknown to be that could accomplish this. I think all the source songs are MP3, so just need to reencode to AAC.
And worst case I can reencode everything to AAC, but I still lack a source client that can send the song over to icecast2 without having to play it on the host and then capture the audio stream. Thank you.
From jeffares.robert at gmail.com Sun Jul 12 21:51:10 2020
From: jeffares.robert at gmail.com (Robert Jeffares)
Date: Mon, 13 Jul 2020 09:51:10 +1200
Subject: [Icecast] Linux source-client that can push AAC to icecast2?
In-Reply-To: <23069-1594578320-876806@sneakemail.com>
References: <23069-1594578320-876806@sneakemail.com>
Message-ID: <778b3042-699c-1c15-82dc-659035b8a271@gmail.com>
looks like a job for liquidsoap!
You can set up a playlist of any kind of audio.
It will encode AAC and AAC+ both have small footprints with better audio
delivery.
I assume you are using mp3 as source because of limited space.
The resampled sound will be no better then the mp3 source and in some
cases will not be so good.
regards
Robert
On 13/07/20 6:25 am, axeon wrote:
> Hi all, I set up ezstream to read a playlist.m3u file containing only MP3 encoded songs (to shuffle continuously) and push this to icecast2. This works, and I can also reencode to a lower bitrate.
>
> I would like to know if there is a way to reencode these MP3s into AAC-LC 128kpbs and then push the stream to icecast2. I'm doing this on a VM with only terminal access and no audio hardware, so ezstream was perfect because it could just read MP3s and send it over, but it does not support AAC. I've looked at all the other source clients on the icecast website, but could not find anything that could work with AAC. I'm not good enough with Linux to recompile stuff (have run into errors on clean cloud Linux VMs), so was hoping there were packages unknown to be that could accomplish this. I think all the source songs are MP3, so just need to reencode to AAC.
>
> And worst case I can reencode everything to AAC, but I still lack a source client that can send the song over to icecast2 without having to play it on the host and then capture the audio stream. Thank you.
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
--
Communication Consultants 2020 Limited
64 Warner Park Avenue
Laingholm
Auckland 0604
New Zealand
From 2qopz9602 at sneakemail.com Mon Jul 13 04:52:46 2020
From: 2qopz9602 at sneakemail.com (axeon)
Date: Sun, 12 Jul 2020 21:52:46 -0700
Subject: [Icecast] Linux source-client that can push AAC to icecast2?
In-Reply-To: <778b3042-699c-1c15-82dc-659035b8a271@gmail.com>
References: <23069-1594578320-876806@sneakemail.com>
<778b3042-699c-1c15-82dc-659035b8a271@gmail.com>
Message-ID: <10647-1594616002-732543@sneakemail.com>
Thanks, Robert! liquidsoap looks pretty slick. I'll play around and ask
them for help if I can't set it up properly.
All my songs are in MP3 so I was going to just leave it as is and transcode
to AAC live, out of laziness. Do you think that is a bad idea? Should I
convert them all to AAC ahead of time? I'm setting this up just for myself
to use. The reason I need AAC is because the device I am listening to the
stream with only seems to accept AAC as a stream format, and limited to
128kbps max.
On Sun, Jul 12, 2020 at 2:51 PM Robert Jeffares wrote:
> looks like a job for liquidsoap!
>
> You can set up a playlist of any kind of audio.
>
> It will encode AAC and AAC+ both have small footprints with better audio
> delivery.
>
> I assume you are using mp3 as source because of limited space.
>
> The resampled sound will be no better then the mp3 source and in some
> cases will not be so good.
>
> regards
>
> Robert
>
> On 13/07/20 6:25 am, axeon wrote:
> > Hi all, I set up ezstream to read a playlist.m3u file containing only
> MP3 encoded songs (to shuffle continuously) and push this to icecast2. This
> works, and I can also reencode to a lower bitrate.
> >
> > I would like to know if there is a way to reencode these MP3s into
> AAC-LC 128kpbs and then push the stream to icecast2. I'm doing this on a VM
> with only terminal access and no audio hardware, so ezstream was perfect
> because it could just read MP3s and send it over, but it does not support
> AAC. I've looked at all the other source clients on the icecast website,
> but could not find anything that could work with AAC. I'm not good enough
> with Linux to recompile stuff (have run into errors on clean cloud Linux
> VMs), so was hoping there were packages unknown to be that could accomplish
> this. I think all the source songs are MP3, so just need to reencode to AAC.
> >
> > And worst case I can reencode everything to AAC, but I still lack a
> source client that can send the song over to icecast2 without having to
> play it on the host and then capture the audio stream. Thank you.
> > _______________________________________________
> > Icecast mailing list
> > Icecast at xiph.org
> > http://lists.xiph.org/mailman/listinfo/icecast
>
> --
> Communication Consultants 2020 Limited
> 64 Warner Park Avenue
> Laingholm
> Auckland 0604
> New Zealand
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200712/dc17f5f0/attachment.htm>
From pm at nowster.me.uk Mon Jul 13 10:54:52 2020
From: pm at nowster.me.uk (Paul Martin)
Date: Mon, 13 Jul 2020 11:54:52 +0100
Subject: [Icecast] Installing ice cast with SSL support
In-Reply-To: <5EA871D6-7058-4F2A-8FA2-A7DBC5C3B2BA@riseup.net>
References: <5EA871D6-7058-4F2A-8FA2-A7DBC5C3B2BA@riseup.net>
Message-ID: <20200713105452.GD516668@thinkpad.nowster.org.uk>
On Sat, Jul 11, 2020 at 08:09:23AM +1000, Damian wrote:
> My question is specific to installing a version of Icecast2 with
> support for SSL. Of course I still need to configure the config file
> with the certificate later, but I?ve read that installing icecast
> from the xiph repositories at download.opensouse would get me a
> version with SSL support?doing ...
The version in Debian "testing" currently supports SSL. Support came
in with build 2.4.4-2 on 31 Oct 2019.
There's a backport for "buster" (stable) at
https://packages.debian.org/buster-backports/amd64/icecast2/download
https://packages.debian.org/buster-backports/icecast2
--
Paul Martin <pm at nowster.me.uk>
From db76 at riseup.net Mon Jul 13 20:25:45 2020
From: db76 at riseup.net (Damian)
Date: Tue, 14 Jul 2020 06:25:45 +1000
Subject: [Icecast] Installing ice cast with SSL support
In-Reply-To: <20200713105452.GD516668@thinkpad.nowster.org.uk>
References: <20200713105452.GD516668@thinkpad.nowster.org.uk>
Message-ID: <4E82CF04-640E-499A-9F47-302CF85FAD77@riseup.net>
Thanks for confirming that. So then is the information in the article below about SSL support being available in the stable versions offered by Xiph incorrect?
https://mediarealm.com.au/articles/icecast-https-ssl-setup-lets-encrypt/
> On 13 Jul 2020, at 20:55, Paul Martin <pm at nowster.me.uk> wrote:
>
> ?On Sat, Jul 11, 2020 at 08:09:23AM +1000, Damian wrote:
>> My question is specific to installing a version of Icecast2 with
>> support for SSL. Of course I still need to configure the config file
>> with the certificate later, but I?ve read that installing icecast
>> from the xiph repositories at download.opensouse would get me a
>> version with SSL support?doing ...
>
> The version in Debian "testing" currently supports SSL. Support came
> in with build 2.4.4-2 on 31 Oct 2019.
>
> There's a backport for "buster" (stable) at
>
> https://packages.debian.org/buster-backports/amd64/icecast2/download
> https://packages.debian.org/buster-backports/icecast2
>
> --
> Paul Martin <pm at nowster.me.uk>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200714/1caddae8/attachment.htm>
From geoff at QuiteLikely.com Mon Jul 13 21:23:24 2020
From: geoff at QuiteLikely.com (Geoff Shang)
Date: Tue, 14 Jul 2020 00:23:24 +0300 (IDT)
Subject: [Icecast] Linux source-client that can push AAC to icecast2?
In-Reply-To: <23069-1594578320-876806@sneakemail.com>
References: <23069-1594578320-876806@sneakemail.com>
Message-ID: <alpine.DEB.2.11.2007140018490.60727@debian.work>
On Sun, 12 Jul 2020, axeon wrote:
> Hi all, I set up ezstream to read a playlist.m3u file containing only
> MP3 encoded songs (to shuffle continuously) and push this to icecast2.
> This works, and I can also reencode to a lower bitrate.
> I would like to know if there is a way to reencode these MP3s into
> AAC-LC 128kpbs and then push the stream to icecast2. I'm doing this on a
> VM with only terminal access and no audio hardware, so ezstream was
> perfect because it could just read MP3s and send it over, but it does
> not support AAC.
The thing about ezstream is it can literally support anything if you have
the needed command line decoder and encoder.
I have no experience with streaming AAC, but presumably you could figure
out the appropriate faac command line and set it up as an encoder and have
ezstream stream it.
Cheers,
Geoff.
From 2qopz9602 at sneakemail.com Tue Jul 14 01:24:44 2020
From: 2qopz9602 at sneakemail.com (axeon)
Date: Mon, 13 Jul 2020 18:24:44 -0700
Subject: [Icecast] Linux source-client that can push AAC to icecast2?
In-Reply-To: <alpine.DEB.2.11.2007140018490.60727@debian.work>
References: <23069-1594578320-876806@sneakemail.com>
<alpine.DEB.2.11.2007140018490.60727@debian.work>
Message-ID: <5486-1594689922-268472@sneakemail.com>
On Mon, Jul 13, 2020 at 2:23 PM Geoff Shang wrote:
> On Sun, 12 Jul 2020, axeon wrote:
>
> > Hi all, I set up ezstream to read a playlist.m3u file containing only
> > MP3 encoded songs (to shuffle continuously) and push this to icecast2.
> > This works, and I can also reencode to a lower bitrate.
>
> > I would like to know if there is a way to reencode these MP3s into
> > AAC-LC 128kpbs and then push the stream to icecast2. I'm doing this on a
> > VM with only terminal access and no audio hardware, so ezstream was
> > perfect because it could just read MP3s and send it over, but it does
> > not support AAC.
>
> The thing about ezstream is it can literally support anything if you have
> the needed command line decoder and encoder.
>
> I have no experience with streaming AAC, but presumably you could figure
> out the appropriate faac command line and set it up as an encoder and have
> ezstream stream it.
>
> Cheers,
> Geoff.
>
I wrote my XML file here: https://pastebin.com/Ta54uZji
But, after running it gives the error:
ezstream[28007]: aacstream.xml[14]: stream (default): format: unsupported
stream format
ezstream[28007]: aacstream.xml[38]: encoder (aac-encoder): format:
unsupported stream format
I probably don't have the encoding command correct, but not sure what to do
about line 14 error.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200713/24f3b954/attachment.htm>
From pm at nowster.me.uk Tue Jul 14 15:49:26 2020
From: pm at nowster.me.uk (Paul Martin)
Date: Tue, 14 Jul 2020 16:49:26 +0100
Subject: [Icecast] Installing ice cast with SSL support
In-Reply-To: <4E82CF04-640E-499A-9F47-302CF85FAD77@riseup.net>
References: <20200713105452.GD516668@thinkpad.nowster.org.uk>
<4E82CF04-640E-499A-9F47-302CF85FAD77@riseup.net>
Message-ID: <20200714154926.GB571653@thinkpad.nowster.org.uk>
On Tue, Jul 14, 2020 at 06:25:45AM +1000, Damian wrote:
> Thanks for confirming that. So then is the information in the
> article below about SSL support being available in the stable
> versions offered by Xiph incorrect?
>
> https://mediarealm.com.au/articles/icecast-https-ssl-setup-lets-encrypt/
It's out of date now. You can get pre-built icecast2 packages from
Debian directly, which support SSL out of the box. (They're linked
against a different SSL library, not openssl, but they work just
fine.)
The version in Debian "stable" doesn't have SSL support, but the one
in testing or backports does (as mentioned in my previous message).
I can't tell you if Ubuntu has picked up the update yet.
--
Paul Martin <pm at nowster.me.uk>
From db76 at riseup.net Tue Jul 14 20:25:51 2020
From: db76 at riseup.net (Damian)
Date: Wed, 15 Jul 2020 06:25:51 +1000
Subject: [Icecast] Installing ice cast with SSL support
In-Reply-To: <20200714154926.GB571653@thinkpad.nowster.org.uk>
References: <20200714154926.GB571653@thinkpad.nowster.org.uk>
Message-ID: <96CFB008-89EE-4F02-A65F-A588ADCAABC8@riseup.net>
Great. Thanks for clarifying all that.
> On 15 Jul 2020, at 01:49, Paul Martin <pm at nowster.me.uk> wrote:
>
> ?On Tue, Jul 14, 2020 at 06:25:45AM +1000, Damian wrote:
>> Thanks for confirming that. So then is the information in the
>> article below about SSL support being available in the stable
>> versions offered by Xiph incorrect?
>>
>> https://mediarealm.com.au/articles/icecast-https-ssl-setup-lets-encrypt/
>
> It's out of date now. You can get pre-built icecast2 packages from
> Debian directly, which support SSL out of the box. (They're linked
> against a different SSL library, not openssl, but they work just
> fine.)
>
> The version in Debian "stable" doesn't have SSL support, but the one
> in testing or backports does (as mentioned in my previous message).
>
> I can't tell you if Ubuntu has picked up the update yet.
>
> --
> Paul Martin <pm at nowster.me.uk>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
From db76 at riseup.net Sat Jul 18 09:30:28 2020
From: db76 at riseup.net (Damian)
Date: Sat, 18 Jul 2020 19:30:28 +1000
Subject: [Icecast] Streaming SSL / HTTPS with m3u file
Message-ID: <BFAA6821-C000-4B98-A6DE-267A0B8EE2F4@riseup.net>
Hi,
I installed icecast2 on Debian 10 via backports for buster so that I could get ssl support.
I?ve successfully configured iceacst to stream via ssl within the browser. No problems there.
For instance I can successfully open a https link to the stream with a URL like https://domain-name.net:8433/mountname <https://domain-name.net:8433/mountname>
However, the same URL with .m3u at the end fails
The issue seems to be similar to this thread ... https://gitlab.xiph.org/xiph/icecast-server/-/issues/2323 <https://gitlab.xiph.org/xiph/icecast-server/-/issues/2323>
When trying to open m3u or xspf stream links via the icecast status.xsl page, it gives errors. Hovering over the m3u or xspf stream links shows a https URL, but when opening the file in a client, it tries to play a http stream and fails. The actual contents of the file shows a http link to the stream rather than a https link. Seems to be something internal to icecast.
The icecast.xsl config is set up for ssl as follows:
<hostname>IP address or domain HERE</hostname>
<!-- You may have multiple <listen-socket> elements-->
<listen-socket>
<port>8000</port>
<bind-address>127.0.0.1</bind-address>
<!-- <shoutcast-mount>/stream</shoutcast-mount> -->
</listen-socket>
<listen-socket>
<port>8443</port>
<ssl>1</ssl>
</listen-socket>
Can you confirm whether the issue in the thread above has been resolved? ? and is there something else I need to do in the config to avert this problem?
Cheers
Damian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200718/81446f71/attachment.htm>
From db76 at riseup.net Sun Jul 19 23:12:51 2020
From: db76 at riseup.net (Damian)
Date: Mon, 20 Jul 2020 09:12:51 +1000
Subject: [Icecast] Streaming SSL / HTTPS with m3u file
In-Reply-To: <BFAA6821-C000-4B98-A6DE-267A0B8EE2F4@riseup.net>
References: <BFAA6821-C000-4B98-A6DE-267A0B8EE2F4@riseup.net>
Message-ID: <AE827EA3-E9E4-4E9E-A564-4F67C2B90DB7@riseup.net>
I solved the issue by adding my own m3u files to /usr/share/icecast/web but I am not sure if this is icecast best-practice. This also raises a few other issues as well? http stream links don?t appear on the icecast stream directory and stream titles and track metadata does not display when opening m3u files created in this way. I assume that there are various reasons for this?mainly that https connections are not really meant to be opened via m3u files, but instead should be opened directly in the browser. Hoping to get some confirmation on these suspicions.
> On 18 Jul 2020, at 19:30, Damian <db76 at riseup.net> wrote:
>
> Hi,
>
> I installed icecast2 on Debian 10 via backports for buster so that I could get ssl support.
> I?ve successfully configured iceacst to stream via ssl within the browser. No problems there.
> For instance I can successfully open a https link to the stream with a URL like https://domain-name.net:8433/mountname <https://domain-name.net:8433/mountname>
>
> However, the same URL with .m3u at the end fails
>
> The issue seems to be similar to this thread ... https://gitlab.xiph.org/xiph/icecast-server/-/issues/2323 <https://gitlab.xiph.org/xiph/icecast-server/-/issues/2323>
>
> When trying to open m3u or xspf stream links via the icecast status.xsl page, it gives errors. Hovering over the m3u or xspf stream links shows a https URL, but when opening the file in a client, it tries to play a http stream and fails. The actual contents of the file shows a http link to the stream rather than a https link. Seems to be something internal to icecast.
>
> The icecast.xsl config is set up for ssl as follows:
>
> <hostname>IP address or domain HERE</hostname>
>
> <!-- You may have multiple <listen-socket> elements-->
> <listen-socket>
> <port>8000</port>
> <bind-address>127.0.0.1</bind-address>
> <!-- <shoutcast-mount>/stream</shoutcast-mount> -->
> </listen-socket>
>
> <listen-socket>
> <port>8443</port>
> <ssl>1</ssl>
> </listen-socket>
>
>
> Can you confirm whether the issue in the thread above has been resolved? ? and is there something else I need to do in the config to avert this problem?
>
> Cheers
>
> Damian
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200720/48345768/attachment.htm>
From epirat07 at gmail.com Mon Jul 20 10:36:19 2020
From: epirat07 at gmail.com (Marvin Scholz)
Date: Mon, 20 Jul 2020 12:36:19 +0200
Subject: [Icecast] Streaming SSL / HTTPS with m3u file
In-Reply-To: <AE827EA3-E9E4-4E9E-A564-4F67C2B90DB7@riseup.net>
References: <BFAA6821-C000-4B98-A6DE-267A0B8EE2F4@riseup.net>
<AE827EA3-E9E4-4E9E-A564-4F67C2B90DB7@riseup.net>
Message-ID: <069DEA15-D6E2-4D46-A113-6593CBFFA2D2@gmail.com>
On 20 Jul 2020, at 1:12, Damian wrote:
> I solved the issue by adding my own m3u files to
> /usr/share/icecast/web but I am not sure if this is icecast
> best-practice. This also raises a few other issues as well? http
> stream links don?t appear on the icecast stream directory and stream
> titles and track metadata does not display when opening m3u files
> created in this way.
Which player did you try this with?
> I assume that there are various reasons for this?mainly that https
> connections are not really meant to be opened via m3u files, but
> instead should be opened directly in the browser. Hoping to get some
> confirmation on these suspicions.
>
>
>
>> On 18 Jul 2020, at 19:30, Damian <db76 at riseup.net> wrote:
>>
>> Hi,
>>
>> I installed icecast2 on Debian 10 via backports for buster so that I
>> could get ssl support.
>> I?ve successfully configured iceacst to stream via ssl within the
>> browser. No problems there.
>> For instance I can successfully open a https link to the stream with
>> a URL like https://domain-name.net:8433/mountname
>> <https://domain-name.net:8433/mountname>
>>
>> However, the same URL with .m3u at the end fails
>>
>> The issue seems to be similar to this thread ...
>> https://gitlab.xiph.org/xiph/icecast-server/-/issues/2323
>> <https://gitlab.xiph.org/xiph/icecast-server/-/issues/2323>
>>
>> When trying to open m3u or xspf stream links via the icecast
>> status.xsl page, it gives errors. Hovering over the m3u or xspf
>> stream links shows a https URL, but when opening the file in a
>> client, it tries to play a http stream and fails. The actual contents
>> of the file shows a http link to the stream rather than a https link.
>> Seems to be something internal to icecast.
>>
>> The icecast.xsl config is set up for ssl as follows:
>>
>> <hostname>IP address or domain HERE</hostname>
>>
>> <!-- You may have multiple <listen-socket> elements-->
>> <listen-socket>
>> <port>8000</port>
>> <bind-address>127.0.0.1</bind-address>
>> <!-- <shoutcast-mount>/stream</shoutcast-mount> -->
>> </listen-socket>
>>
>> <listen-socket>
>> <port>8443</port>
>> <ssl>1</ssl>
>> </listen-socket>
>>
>>
>> Can you confirm whether the issue in the thread above has been
>> resolved? ? and is there something else I need to do in the config
>> to avert this problem?
>>
>> Cheers
>>
>> 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
From db76 at riseup.net Mon Jul 20 11:02:38 2020
From: db76 at riseup.net (Damian)
Date: Mon, 20 Jul 2020 21:02:38 +1000
Subject: [Icecast] Streaming SSL / HTTPS with m3u file
In-Reply-To: <069DEA15-D6E2-4D46-A113-6593CBFFA2D2@gmail.com>
References: <BFAA6821-C000-4B98-A6DE-267A0B8EE2F4@riseup.net>
<AE827EA3-E9E4-4E9E-A564-4F67C2B90DB7@riseup.net>
<069DEA15-D6E2-4D46-A113-6593CBFFA2D2@gmail.com>
Message-ID: <5FE28B92-9A77-4115-A4C5-061C332DA58C@riseup.net>
>
> On 20 Jul 2020, at 1:12, Damian wrote:
>
>> I solved the issue by adding my own m3u files to /usr/share/icecast/web but I am not sure if this is icecast best-practice. This also raises a few other issues as well? http stream links don?t appear on the icecast stream directory and stream titles and track metadata does not display when opening m3u files created in this way.
>
> Which player did you try this with?
>
I used VLC and Apple Music on Mac OS Catalina. I also tested it using VLC on Debian 10.
From epirat07 at gmail.com Mon Jul 20 11:33:14 2020
From: epirat07 at gmail.com (Marvin Scholz)
Date: Mon, 20 Jul 2020 13:33:14 +0200
Subject: [Icecast] Streaming SSL / HTTPS with m3u file
In-Reply-To: <5FE28B92-9A77-4115-A4C5-061C332DA58C@riseup.net>
References: <BFAA6821-C000-4B98-A6DE-267A0B8EE2F4@riseup.net>
<AE827EA3-E9E4-4E9E-A564-4F67C2B90DB7@riseup.net>
<069DEA15-D6E2-4D46-A113-6593CBFFA2D2@gmail.com>
<5FE28B92-9A77-4115-A4C5-061C332DA58C@riseup.net>
Message-ID: <BBB3486B-06D5-451C-A0BF-022B456A6656@gmail.com>
On 20 Jul 2020, at 13:02, Damian wrote:
>>
>> On 20 Jul 2020, at 1:12, Damian wrote:
>>
>>> I solved the issue by adding my own m3u files to
>>> /usr/share/icecast/web but I am not sure if this is icecast
>>> best-practice. This also raises a few other issues as well? http
>>> stream links don?t appear on the icecast stream directory and
>>> stream titles and track metadata does not display when opening m3u
>>> files created in this way.
>>
>> Which player did you try this with?
>>
>
>
> I used VLC and Apple Music on Mac OS Catalina. I also tested it using
> VLC on Debian 10.
>
For https streams, VLC will not be able to show ICY metadata (used for
example for MP3 or AAC streams)
due to a bug in VLC.
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
From db76 at riseup.net Mon Jul 20 11:38:24 2020
From: db76 at riseup.net (Damian)
Date: Mon, 20 Jul 2020 21:38:24 +1000
Subject: [Icecast] Streaming SSL / HTTPS with m3u file
In-Reply-To: <BBB3486B-06D5-451C-A0BF-022B456A6656@gmail.com>
References: <BFAA6821-C000-4B98-A6DE-267A0B8EE2F4@riseup.net>
<AE827EA3-E9E4-4E9E-A564-4F67C2B90DB7@riseup.net>
<069DEA15-D6E2-4D46-A113-6593CBFFA2D2@gmail.com>
<5FE28B92-9A77-4115-A4C5-061C332DA58C@riseup.net>
<BBB3486B-06D5-451C-A0BF-022B456A6656@gmail.com>
Message-ID: <AF1D4CA3-F670-4E40-9282-8195EB9D8B69@riseup.net>
>
> For https streams, VLC will not be able to show ICY metadata (used for example for MP3 or AAC streams)
> due to a bug in VLC.
>
Okay. Do you know why Apple Music wouldn?t play the https stream at all? Also, just going back to my previous question, are https streams not available on the Xiph stream directory?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200720/5236a807/attachment.htm>
From epirat07 at gmail.com Mon Jul 20 19:45:12 2020
From: epirat07 at gmail.com (Marvin Scholz)
Date: Mon, 20 Jul 2020 21:45:12 +0200
Subject: [Icecast] Streaming SSL / HTTPS with m3u file
In-Reply-To: <AF1D4CA3-F670-4E40-9282-8195EB9D8B69@riseup.net>
References: <BFAA6821-C000-4B98-A6DE-267A0B8EE2F4@riseup.net>
<AE827EA3-E9E4-4E9E-A564-4F67C2B90DB7@riseup.net>
<069DEA15-D6E2-4D46-A113-6593CBFFA2D2@gmail.com>
<5FE28B92-9A77-4115-A4C5-061C332DA58C@riseup.net>
<BBB3486B-06D5-451C-A0BF-022B456A6656@gmail.com>
<AF1D4CA3-F670-4E40-9282-8195EB9D8B69@riseup.net>
Message-ID: <C723D5CF-E7A7-404B-92AE-6EBA1A3AA42A@gmail.com>
On 20 Jul 2020, at 13:38, Damian wrote:
>>
>> For https streams, VLC will not be able to show ICY metadata (used
>> for example for MP3 or AAC streams)
>> due to a bug in VLC.
>>
>
>
> Okay. Do you know why Apple Music wouldn?t play the https stream at
> all? Also, just going back to my previous question, are https streams
> not available on the Xiph stream directory?
No, currently its not easily possible to list a https stream in the
directory.
It's a known issue that will be solved for Icecast 2.5
Regarding Apple Music, I did not test yet. Have you tried with the
direct stream URL not the m3u paylist?
From db76 at riseup.net Mon Jul 20 20:25:03 2020
From: db76 at riseup.net (Damian)
Date: Tue, 21 Jul 2020 06:25:03 +1000
Subject: [Icecast] Streaming SSL / HTTPS with m3u file
In-Reply-To: <C723D5CF-E7A7-404B-92AE-6EBA1A3AA42A@gmail.com>
References: <BFAA6821-C000-4B98-A6DE-267A0B8EE2F4@riseup.net>
<AE827EA3-E9E4-4E9E-A564-4F67C2B90DB7@riseup.net>
<069DEA15-D6E2-4D46-A113-6593CBFFA2D2@gmail.com>
<5FE28B92-9A77-4115-A4C5-061C332DA58C@riseup.net>
<BBB3486B-06D5-451C-A0BF-022B456A6656@gmail.com>
<AF1D4CA3-F670-4E40-9282-8195EB9D8B69@riseup.net>
<C723D5CF-E7A7-404B-92AE-6EBA1A3AA42A@gmail.com>
Message-ID: <6F3278D8-344F-4484-9E19-70DBD2AE670F@riseup.net>
Hi, yes direct stream URLs work ? I did test that, but I guess the issue is that most listeners want to click on a link rather than cut and paste a steam link into their players. It?s not an ideal way to attract traffic that passes through the radio website. It?s good to know that the issues I?ve asked about are not problems at my end though. Thanks for confirming these.
> On 21 Jul 2020, at 05:45, Marvin Scholz <epirat07 at gmail.com> wrote:
>
>
>
> On 20 Jul 2020, at 13:38, Damian wrote:
>
>>>
>>> For https streams, VLC will not be able to show ICY metadata (used for example for MP3 or AAC streams)
>>> due to a bug in VLC.
>>>
>>
>>
>> Okay. Do you know why Apple Music wouldn?t play the https stream at all? Also, just going back to my previous question, are https streams not available on the Xiph stream directory?
>
> No, currently its not easily possible to list a https stream in the directory.
> It's a known issue that will be solved for Icecast 2.5
>
> Regarding Apple Music, I did not test yet. Have you tried with the direct stream URL not the m3u paylist?
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
From pm at nowster.me.uk Fri Jul 24 09:11:05 2020
From: pm at nowster.me.uk (Paul Martin)
Date: Fri, 24 Jul 2020 10:11:05 +0100
Subject: [Icecast] Streaming SSL / HTTPS with m3u file
In-Reply-To: <6F3278D8-344F-4484-9E19-70DBD2AE670F@riseup.net>
References: <BFAA6821-C000-4B98-A6DE-267A0B8EE2F4@riseup.net>
<AE827EA3-E9E4-4E9E-A564-4F67C2B90DB7@riseup.net>
<069DEA15-D6E2-4D46-A113-6593CBFFA2D2@gmail.com>
<5FE28B92-9A77-4115-A4C5-061C332DA58C@riseup.net>
<BBB3486B-06D5-451C-A0BF-022B456A6656@gmail.com>
<AF1D4CA3-F670-4E40-9282-8195EB9D8B69@riseup.net>
<C723D5CF-E7A7-404B-92AE-6EBA1A3AA42A@gmail.com>
<6F3278D8-344F-4484-9E19-70DBD2AE670F@riseup.net>
Message-ID: <20200724091105.GA164457@thinkpad.nowster.org.uk>
On Tue, Jul 21, 2020 at 06:25:03AM +1000, Damian wrote:
> Hi, yes direct stream URLs work ? I did test that, but I guess the
> issue is that most listeners want to click on a link rather than cut
> and paste a steam link into their players. It?s not an ideal way to
> attract traffic that passes through the radio website. It?s good to
> know that the issues I?ve asked about are not problems at my end
> though. Thanks for confirming these.
The m3u file can be stored anywhere. It doesn't have to be served by
icecast. It could be served by your radio station's website.
All it needs is to contain is a single line like:
https://icecast.example.com:8443/stream.mp3
(And yes, the M3U links from the Icecast status page are to "http" not
"https" even if you're looking at the status page via https.)
--
Paul Martin <pm at nowster.me.uk>