<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
<div class="moz-text-html" lang="x-western">
<p>Hello,<br>
The icecast 2.4 is compatible with ssl, I use it here (windows
server too).<br>
Just set up your icecast to read your certificate (.pem).<br>
you will only have to use a different port than the current one
you use to hear. (8003)</p>
<p><br>
SEE AN EXAMPLE OF MY CONFIGURATION:<br>
<br>
<icecast><br>
<location> XXXXXXXXX </location><br>
<admin> XXXXX @ XXXXX </admin><br>
<hostname> 127.0.0.1 </hostname><br>
<br>
<limits><br>
<clients> 100 </clients><br>
<sources> 1 </sources><br>
<queue-size> 524288 </queue-size><br>
<client-timeout> 30 </client-timeout><br>
<header-timeout> 15 </header-timeout><br>
<source-timeout> 10 </source-timeout><br>
<burst-on-connect> 1 </burst-on-connect><br>
<burst-size> 65535 </burst-size><br>
</limits><br>
<br>
<authentication><br>
<source-password> XXXXXXXX
</source-password><br>
<relay-password> XXXXXXXXXX
</relay-password><br>
<admin-user> XXXXXXXXXXX </admin-user><br>
<admin-password> XXXXXXXXX </admin-password><br>
</authentication><br>
<br>
<listen-socket><br>
<port> 8002 </port><br>
<shoutcast-mount> / 8002 </shoutcast-mount><br>
</listen-socket><br>
<br>
<br>
<listen-socket><br>
<port> 8003 </port> <--------- THIS WILL
BE YOUR SSL PORT<br>
<ssl> 1 </ssl><br>
</listen-socket><br>
<br>
<br>
<http-headers><br>
<header name = "Access-Control-Allow-Origin" value =
"*" /><br>
</http-headers><br>
<br>
<br>
<fileserve> 1 </fileserve><br>
<br>
<paths><br>
<logdir> .. \ log </logdir><br>
<webroot> .. \ web </webroot><br>
<adminroot> .. \ admin </adminroot><br>
<ssl-certificate> .. \ ssl \ CERTIFICADO.PEM
</ssl-certificate><br>
<alias source = "/" destination = "/ status.xsl"
/><br>
</paths><br>
<br>
<logging><br>
<accesslog> - </accesslog><br>
<errorlog> error.log </errorlog><br>
<loglevel> 1 </loglevel> <! - 4 Debug, 3
Info, 2 Warn, 1 Error -><br>
<logsize> 10000 </logsize> <! - Max size
of a logfile -><br>
</logging><br>
</icecast><br>
<br>
<br>
HOPE THIS HELPS<br>
<br>
GOOD LUCK!!<br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">Em 28/04/2020 17:35, Federico
Miniussi escreveu:<br>
</div>
<blockquote type="cite"
cite="mid:CAKQM2z2s9i6DXEYmyh8F=_wPAjTjVAnQk6yhqatMh5AXvZWixw@mail.gmail.com">
<div class="moz-text-html" lang="x-unicode">
<div dir="ltr">Hello,
<div>Before writing here I really tried almost everything,
reading the archives here, the FAQ and dozens of more or
less well commented online guides and posts.<br>
<br>
My environment is a Windows server, with IIS as web server
(I know, blame and flame on me, but this was available on
my hands at the time). The server is hosting several
websites and an icecast 2.4.4 running an online radio.</div>
<div><br>
</div>
<div>The radio on icecast can be listen through its website
(on my server too) with an html5 player.</div>
<div><br>
</div>
<div>Of course since end of january I started to have
notifications from listeners that were unable to hear
anything due to Chrome browser update and unsecure content
(website is of course under SSL with its cert).</div>
<div><br>
</div>
<div>A patch has been forwarded by myself to the Chrome
listeners by instructing them how to allow the unsecure
content from the radio's website in the settings of
chrome, then I started to find the solution.</div>
<div><br>
</div>
<div>As you of course know, the windows package of icecast
2.4.4 has no SSL capability so I switched almost
immediately into the proxy forward solution. However no
way as I'm not able to bind the SSL certificate to the
icecast streaming port (8002 in my case).<br>
<br>
If you have any advice about a possible solution (even
temporary) with a windows and IIS environment, it would be
highly appreciated. Otherwise, if you know that it is
literally impossible, simply tell me "no way" so I simply
stop struggling.<br>
<br>
I have full access to the server so I can play with
settings, install other softwares and so on.<br>
<br>
Thanks a lot, all the best to you.</div>
<div>Federico from Italy</div>
<div><br>
<br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<div class="moz-text-plain" wrap="true" lang="x-unicode">
<pre class="moz-quote-pre" wrap="">_______________________________________________
Icecast mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Icecast@xiph.org">Icecast@xiph.org</a>
<a class="moz-txt-link-freetext" href="http://lists.xiph.org/mailman/listinfo/icecast">http://lists.xiph.org/mailman/listinfo/icecast</a>
</pre>
</div>
</blockquote>
</div>
<div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br /> <table style="border-top: 1px solid #D3D4DE;">
<tr>
<td style="width: 55px; padding-top: 18px;"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" target="_blank"><img src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif" alt="" width="46" height="29" style="width: 46px; height: 29px;" /></a></td>
<td style="width: 470px; padding-top: 17px; color: #41424e; font-size: 13px; font-family: Arial, Helvetica, sans-serif; line-height: 18px;">Livre de vírus. <a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" target="_blank" style="color: #4453ea;">www.avast.com</a>. </td>
</tr>
</table>
<a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"> </a></div></body>
</html>