<html><head></head><body> Sorry for the late update. I didn't realise the replies came and went off list regarding this.<br><br> I had another suggestion made to me it could still be bad pem files and to try converting them to pfx then back to pem files, which I did, and fortunately this fixed it.<br><br> The error message I was getting in the Icecast log was about no compatible ssl port. I assumed this was something more complex than a bad certificate since an error message to that effect would have been easier to figure out.<br><br> I took the certificate and private key .pem files, added them together but it didn't work until the conversion to pfx and back.<br><br> Thanks for the reply though.<br><br>Cheers,<br>Gavin.<br><br><br><br><br><br><br><br><br><br><div class="gmail_quote">On 9 March 2020 4:03:00 AM NZDT, Paul Martin <pm@nowster.me.uk> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On Sat, Mar 07, 2020 at 07:16:51AM +1300, Gavin Stephens wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">FYI Chrome just sits there saying establishing secure connection. I've just<br>installed Ice on another machine and copied over the icecast.pem file and<br>un-remarked the port and path areas for SSL on port 443 (not 8443). Same<br>result.<br></blockquote><br>I have:<br><br> <listen-socket><br> <port>8443</port><br> <bind-address>::</bind-address><br> <ssl>1</ssl><br> </listen-socket><br><br> <paths><br> <ssl-certificate>/etc/icecast2/icecast.pem</ssl-certificate><br> </paths><br><br>And it's definitely working with Chromium 80.0.3987.132.<br><br>Is there anything else listening on port 443/tcp on that server?<br></pre></blockquote></div><br>-- <br>Sent from Open Mail on Android.</body></html>