<div dir="ltr">Thanks Thomas. I did see the stunnel option but I really had no need to put out that extra effort as my source lives on the same host as the icecast server. Just like you stated, since I'm pointing it at the localhost there really is no need to encrypt that stream. So I'm just running a secondary port that isn't publicly exposed as non-ssl.<div><br></div><div>Thanks again,</div><div>Nathan<br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 3, 2015 at 10:50 PM, "Thomas B. Rücker" <span dir="ltr"><<a href="mailto:thomas@ruecker.fi" target="_blank">thomas@ruecker.fi</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 04/04/2015 02:42 AM, Nathan Miller wrote:<br>
> Philipp,<br>
><br>
> Thank you for your quick response. I can't believe that I didn't<br>
> think of that...I guess I just assumed that it would use SSL. I'm<br>
> using Liquidsoap as my source client. Once you brought that up I<br>
> started researching whether there was a way to force Liquidsoap to use<br>
> SSL and from what I found it doesn't look like there is an<br>
> option...but please correct me if you or anyone else who reads this<br>
> knows differently.<br>
><br>
> After I had a good idea of what was happening I found this other<br>
> thread <a href="http://lists.xiph.org/pipermail/icecast/2015-January/013118.html" target="_blank">http://lists.xiph.org/pipermail/icecast/2015-January/013118.html</a> that<br>
> talks about exactly what I'm trying to do using Liquidsoap. I<br>
> followed it and I'm good now running on two ports...one SSL and one<br>
> not from connecting to Liquidsoap.<br>
><br>
> Thanks again for your hint :) and please let me know if you've seen<br>
> other ways to tackle this with Liquidsoap than what I setup.<br>
<br>
If you read the remainder of that thread you pointed to, you'll find<br>
some hints.<br>
The main thing being to "ssl enable" the source connections by using<br>
Stunnel on the originating machine. This random picture from "the<br>
interwebz" explains it pretty well:<br>
<a href="http://www.ximera.de/bilder/stunnel2.png" target="_blank">http://www.ximera.de/bilder/stunnel2.png</a><br>
In place of "Hamster" you'd have your source client.<br>
<br>
I expect the TLS support situation to improve with source clients, as we<br>
are soon going to release a TLS enabled version of libshout. The library<br>
many clients use to talk to Icecast servers.<br>
<br>
In case one has only local connections from source clients, then just<br>
binding a plain http port to ::1 or 127.0.0.1 is safe too.<br>
<br>
Cheers<br>
<br>
Thomas<br>
<br>
<br>
<br>
> On Fri, Apr 3, 2015 at 3:41 PM, Philipp Schafft <<a href="mailto:lion@lion.leolix.org">lion@lion.leolix.org</a><br>
> <mailto:<a href="mailto:lion@lion.leolix.org">lion@lion.leolix.org</a>>> wrote:<br>
><br>
> Good evening,<br>
><br>
> On Fri, 2015-04-03 at 14:02 -0700, Nathan Miller wrote:<br>
> > I'm running Icecast package 2.4.1 on Ubuntu 14.04<br>
> > from<br>
> ttp://<a href="http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04" target="_blank">download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04</a> <<a href="http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04" target="_blank">http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04</a>>.<br>
> ><br>
> ><br>
> > I've been running on this server for about 6 months now without any<br>
> > issue and all my streams run great. This icecast server is<br>
> running on<br>
> > the same host that my wordpress site is running on. This is all<br>
> on my<br>
> > own private server, not a hosting service.<br>
> ><br>
> ><br>
> > Recently I decided to switch everything to SSL and all went well<br>
> with<br>
> > the exception of the icecast server. The SSL portion of the icecast<br>
> > server is actually working just fine and the SSL certificate is<br>
> > loading on the admin page on all modern browsers without any<br>
> issue or<br>
> > error. I can see the full admin page and navigate it without issue.<br>
> > The problem is as soon as I add this line to the <paths> section, as<br>
> > required to load the PEM certificate, my mountpoint streams stopped<br>
> > loading:<br>
> ><br>
> ><br>
> ><br>
> <ssl-certificate>/usr/share/icecast2/ssl/mysslcertname.pem</ssl-certificate><br>
> ><br>
> ><br>
> ><br>
> > Then my icecast error log fills with this whenever anyone<br>
> attempts to<br>
> > hit any of the stream mountpoints that failed to load:<br>
> ><br>
> ><br>
> > [2015-04-02 18:17:59] INFO fserve/fserve_client_create checking for<br>
> > file /stream1 (/usr/share/icecast2/web/stream1)<br>
> > [2015-04-02 18:17:59] WARN fserve/fserve_client_create req for file<br>
> > "/usr/share/icecast2/web/stream1" No such file or directory<br>
> > [2015-04-03 01:52:43] INFO fserve/fserve_client_create checking for<br>
> > file /stream2 (/usr/share/icecast2/web/stream2)<br>
> > [2015-04-03 01:52:43] WARN fserve/fserve_client_create req for file<br>
> > "/usr/share/icecast2/web/stream2" No such file or directory<br>
><br>
> Those messages tell that there is no mount nor a file in web/. I<br>
> suspect<br>
> that the stream is not mounted (= the source is not connected).<br>
><br>
><br>
> > There is nothing in the error logs after I've added this line to the<br>
> > <paths> and restarted icecast so I'm not sure what is breaking<br>
> but I'm<br>
> > guessing from the errors whenever someone tries to hit the<br>
> mountpoint<br>
> > that the file that was supposed to be created never is. Not<br>
> sure why<br>
> > adding to the path would cause this issue, but as soon as I<br>
> remove it<br>
> > all returns to a working order with stream mountpoints loading and<br>
> > working perfectly...though now SSL is broken again :(<br>
><br>
> Which source client do you use? If you switch the port to TLS that is<br>
> used by the source client to connect you also need to set the source<br>
> client to TLS mode.<br>
><br>
><br>
> > Hopefully someone can provide some guidance here! Thanks!<br>
><br>
> Please come back with the answers. I'm sure this isn't impossible.<br>
><br>
> Have a good night!<br>
><br>
> --<br>
> Philipp.<br>
> (Rah of PH2)<br>
><br>
> _______________________________________________<br>
> Icecast mailing list<br>
> <a href="mailto:Icecast@xiph.org">Icecast@xiph.org</a> <mailto:<a href="mailto:Icecast@xiph.org">Icecast@xiph.org</a>><br>
> <a href="http://lists.xiph.org/mailman/listinfo/icecast" target="_blank">http://lists.xiph.org/mailman/listinfo/icecast</a><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Icecast mailing list<br>
> <a href="mailto:Icecast@xiph.org">Icecast@xiph.org</a><br>
> <a href="http://lists.xiph.org/mailman/listinfo/icecast" target="_blank">http://lists.xiph.org/mailman/listinfo/icecast</a><br>
<br>
<br>
_______________________________________________<br>
Icecast mailing list<br>
<a href="mailto:Icecast@xiph.org">Icecast@xiph.org</a><br>
<a href="http://lists.xiph.org/mailman/listinfo/icecast" target="_blank">http://lists.xiph.org/mailman/listinfo/icecast</a><br>
</blockquote></div><br></div></div></div>