Icecast - Feb 2020 - Chrome not allowing mixed content anymore

For example, in my case, we use several servers with Centovacast, with
several Icecast2 services. Version 2.5 of Icecast2, allows to respond to
http and https connections from the same port, but takes years in beta.
Centovacast does not update its panel, waiting for the final version of
Icecast 2.5 to be released.

Chrome has been warning for months that this would happen in February, but
no one has advanced anything to fix this.

Therefore, we have to enable manually service by service a new secondary
port that responds via https, and contact client by client to update their
Websites, when everyone could be massively enabled by the same port if the
new version of Icecast was already available.

Why is this improvement not already implemented in Icecast2? In Icecast KH
it has been available for months...


El sáb., 29 feb. 2020 a las 16:31, Albert Santoni (<
albert.santoni at oscillicious.com>) escribió:
> Hi all,
>
> Can you explain the use case here a bit more? I think I'm missing
> something in my understanding.
>
> If you enable TLS/HTTPS, you should enable it on a different port (eg.
> 443) and keep your existing HTTP port for Icecast so that your stations
> will continue to work in external players (Winamp, playlists, VLC, etc.).
> However, you should update all embedded links to your stream on your
> website(s) and point them to the new HTTPS port.
>
> Is the problem that your streams are embedded on many websites outside of
> your control?
>
> Thanks,
> Albert
>
>
>
>
> On Sat, Feb 29, 2020 at 10:11 AM Yahav Shasha <yahav.shasha at
gmail.com>
> wrote:
>
>> This is a real problem that needs to be addressed.
>> Anyone has figured a way to mitigate this?
>>
>> On Sat, Feb 29, 2020 at 4:29 PM Mikel Sanz | 20 Comunicación <
>> mikel at 20comunicacion.com> wrote:
>>
>>> Yes, I also think that 6 years of Beta is too much and now it's
too
>>> late...
>>>
>>> El sáb., 29 feb. 2020 14:25, Alexandru Matei <alexandru.ort at
gmail.com>
>>> escribió:
>>>
>>>> Hi.
>>>>
>>>> With its 80th version, Chrome stopped serving non-secure
resources on
>>>> https pages. This affected the icecast server I run also. I
enabled SSL,
>>>> the issue with Chrome not playing audio got fixed, but I
noticed a major
>>>> drop in the number of listeners. As far as I figured out, the
listeners
>>>> that have the http url in a playlist - listening in winamp, vlc
etc. -
>>>> could listen no more. Those using internet radio devices were
affected also.
>>>>
>>>> Does icecast support streaming both http and https on the same
port?
>>>> Is there such a feature in the version 4.5beta2?
>>>> Is there a release date planned for the new version of icecast?
>>>>
>>>> This will affect many listeners and the administrators of those
radios
>>>> servers. What would you do?
>>>>
>>>> Thank you.
>>>>
>>>> Alex G.
>>>> _______________________________________________
>>>> Icecast mailing list
>>>> Icecast at xiph.org
>>>> http://lists.xiph.org/mailman/listinfo/icecast
>>>>
>>> _______________________________________________
>>> 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
>>
>
>
> --
> Albert Santoni
> Founder, Lead Developer | Oscillicious
> Delicious Audio Tools and Plug-ins
> _______________________________________________
> 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/20200229/eb6c9f1b/attachment.html>

@Mikel
You could use Centova's port 80 proxy meanwhile couldn't you?
Also. Centova Cast doesn't have an SSL setting for the servers unless
you're manually overwriting the server config files.. or is it?


On Sat, Feb 29, 2020 at 6:13 PM Mikel Sanz | 20 Comunicación <
mikel at 20comunicacion.com> wrote:
> For example, in my case, we use several servers with Centovacast, with
> several Icecast2 services. Version 2.5 of Icecast2, allows to respond to
> http and https connections from the same port, but takes years in beta.
> Centovacast does not update its panel, waiting for the final version of
> Icecast 2.5 to be released.
>
> Chrome has been warning for months that this would happen in February, but
> no one has advanced anything to fix this.
>
> Therefore, we have to enable manually service by service a new secondary
> port that responds via https, and contact client by client to update their
> Websites, when everyone could be massively enabled by the same port if the
> new version of Icecast was already available.
>
> Why is this improvement not already implemented in Icecast2? In Icecast KH
> it has been available for months...
>
>
> El sáb., 29 feb. 2020 a las 16:31, Albert Santoni (<
> albert.santoni at oscillicious.com>) escribió:
>
>> Hi all,
>>
>> Can you explain the use case here a bit more? I think I'm missing
>> something in my understanding.
>>
>> If you enable TLS/HTTPS, you should enable it on a different port (eg.
>> 443) and keep your existing HTTP port for Icecast so that your stations
>> will continue to work in external players (Winamp, playlists, VLC,
etc.).
>> However, you should update all embedded links to your stream on your
>> website(s) and point them to the new HTTPS port.
>>
>> Is the problem that your streams are embedded on many websites outside
of
>> your control?
>>
>> Thanks,
>> Albert
>>
>>
>>
>>
>> On Sat, Feb 29, 2020 at 10:11 AM Yahav Shasha <yahav.shasha at
gmail.com>
>> wrote:
>>
>>> This is a real problem that needs to be addressed.
>>> Anyone has figured a way to mitigate this?
>>>
>>> On Sat, Feb 29, 2020 at 4:29 PM Mikel Sanz | 20 Comunicación <
>>> mikel at 20comunicacion.com> wrote:
>>>
>>>> Yes, I also think that 6 years of Beta is too much and now
it's too
>>>> late...
>>>>
>>>> El sáb., 29 feb. 2020 14:25, Alexandru Matei <alexandru.ort
at gmail.com>
>>>> escribió:
>>>>
>>>>> Hi.
>>>>>
>>>>> With its 80th version, Chrome stopped serving non-secure
resources on
>>>>> https pages. This affected the icecast server I run also. I
enabled SSL,
>>>>> the issue with Chrome not playing audio got fixed, but I
noticed a major
>>>>> drop in the number of listeners. As far as I figured out,
the listeners
>>>>> that have the http url in a playlist - listening in winamp,
vlc etc. -
>>>>> could listen no more. Those using internet radio devices
were affected also.
>>>>>
>>>>> Does icecast support streaming both http and https on the
same port?
>>>>> Is there such a feature in the version 4.5beta2?
>>>>> Is there a release date planned for the new version of
icecast?
>>>>>
>>>>> This will affect many listeners and the administrators of
those radios
>>>>> servers. What would you do?
>>>>>
>>>>> Thank you.
>>>>>
>>>>> Alex G.
>>>>> _______________________________________________
>>>>> Icecast mailing list
>>>>> Icecast at xiph.org
>>>>> http://lists.xiph.org/mailman/listinfo/icecast
>>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>
>>
>> --
>> Albert Santoni
>> Founder, Lead Developer | Oscillicious
>> Delicious Audio Tools and Plug-ins
>> _______________________________________________
>> 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
>

-- 
Yahav Shasha,
Web Developer
+972-(0)549214421
http://www.linkedin.com/in/yahavs
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.xiph.org/pipermail/icecast/attachments/20200229/83398608/attachment.html>

Yes, but the proxy under port 80 consumes many resources. Besides, it makes
no sense to do it when Icecast2 supports it natively. All that remains is
for the final version 2.5 to be enabled to enable http and https through
the same port and only the certificate should be added to each account
(even if manually), only that would be needed ... Centovacast will update
the panel as soon as it is released the final version, but it all depends
on Icecast doing it ...


El sáb., 29 feb. 2020 a las 17:20, Yahav Shasha (<yahav.shasha at
gmail.com>)
escribió:
> @Mikel
> You could use Centova's port 80 proxy meanwhile couldn't you?
> Also. Centova Cast doesn't have an SSL setting for the servers unless
> you're manually overwriting the server config files.. or is it?
>
>
> On Sat, Feb 29, 2020 at 6:13 PM Mikel Sanz | 20 Comunicación <
> mikel at 20comunicacion.com> wrote:
>
>> For example, in my case, we use several servers with Centovacast, with
>> several Icecast2 services. Version 2.5 of Icecast2, allows to respond
to
>> http and https connections from the same port, but takes years in beta.
>> Centovacast does not update its panel, waiting for the final version of
>> Icecast 2.5 to be released.
>>
>> Chrome has been warning for months that this would happen in February,
>> but no one has advanced anything to fix this.
>>
>> Therefore, we have to enable manually service by service a new
secondary
>> port that responds via https, and contact client by client to update
their
>> Websites, when everyone could be massively enabled by the same port if
the
>> new version of Icecast was already available.
>>
>> Why is this improvement not already implemented in Icecast2? In Icecast
>> KH it has been available for months...
>>
>>
>> El sáb., 29 feb. 2020 a las 16:31, Albert Santoni (<
>> albert.santoni at oscillicious.com>) escribió:
>>
>>> Hi all,
>>>
>>> Can you explain the use case here a bit more? I think I'm
missing
>>> something in my understanding.
>>>
>>> If you enable TLS/HTTPS, you should enable it on a different port
(eg.
>>> 443) and keep your existing HTTP port for Icecast so that your
stations
>>> will continue to work in external players (Winamp, playlists, VLC,
etc.).
>>> However, you should update all embedded links to your stream on
your
>>> website(s) and point them to the new HTTPS port.
>>>
>>> Is the problem that your streams are embedded on many websites
outside
>>> of your control?
>>>
>>> Thanks,
>>> Albert
>>>
>>>
>>>
>>>
>>> On Sat, Feb 29, 2020 at 10:11 AM Yahav Shasha <yahav.shasha at
gmail.com>
>>> wrote:
>>>
>>>> This is a real problem that needs to be addressed.
>>>> Anyone has figured a way to mitigate this?
>>>>
>>>> On Sat, Feb 29, 2020 at 4:29 PM Mikel Sanz | 20 Comunicación
<
>>>> mikel at 20comunicacion.com> wrote:
>>>>
>>>>> Yes, I also think that 6 years of Beta is too much and now
it's too
>>>>> late...
>>>>>
>>>>> El sáb., 29 feb. 2020 14:25, Alexandru Matei
<alexandru.ort at gmail.com>
>>>>> escribió:
>>>>>
>>>>>> Hi.
>>>>>>
>>>>>> With its 80th version, Chrome stopped serving
non-secure resources on
>>>>>> https pages. This affected the icecast server I run
also. I enabled SSL,
>>>>>> the issue with Chrome not playing audio got fixed, but
I noticed a major
>>>>>> drop in the number of listeners. As far as I figured
out, the listeners
>>>>>> that have the http url in a playlist - listening in
winamp, vlc etc. -
>>>>>> could listen no more. Those using internet radio
devices were affected also.
>>>>>>
>>>>>> Does icecast support streaming both http and https on
the same port?
>>>>>> Is there such a feature in the version 4.5beta2?
>>>>>> Is there a release date planned for the new version of
icecast?
>>>>>>
>>>>>> This will affect many listeners and the administrators
of those
>>>>>> radios servers. What would you do?
>>>>>>
>>>>>> Thank you.
>>>>>>
>>>>>> Alex G.
>>>>>> _______________________________________________
>>>>>> Icecast mailing list
>>>>>> Icecast at xiph.org
>>>>>> http://lists.xiph.org/mailman/listinfo/icecast
>>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>
>>>
>>>
>>> --
>>> Albert Santoni
>>> Founder, Lead Developer | Oscillicious
>>> Delicious Audio Tools and Plug-ins
>>> _______________________________________________
>>> 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
>>
>
>
> --
> Yahav Shasha,
> Web Developer
> +972-(0)549214421
> http://www.linkedin.com/in/yahavs
> _______________________________________________
> 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/20200229/67b498f1/attachment.html>