similar to: SSL Question

On Sat, Mar 07, 2020 at 07:16:51AM +1300, Gavin Stephens wrote: > FYI Chrome just sits there saying establishing secure connection. I've just > installed Ice on another machine and copied over the icecast.pem file and > un-remarked the port and path areas for SSL on port 443 (not 8443).  Same > result. I have: <listen-socket> <port>8443</port>

On 7/03/2020 7:08 am, Gavin Stephens wrote: > So as I've just found out last week, Chrome no longer will open an > http audio stream from an https website. > > I've un-remarked and enabled ssl on port 443. I've configured the path > and I've used OpenSSL to generate a cert and key. I've then combined > the private key in to the cert and called it

Sorry for the late update. I didn't realise the replies came and went off list regarding this. 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. The error message I was getting in the Icecast log was about no compatible ssl port. I assumed this was something more complex

I need mobile web browser compatibility across most manufacturers. -Pete > On Jan 27, 2020, at 11:20 AM, user <5f787a at i2pmail.org> wrote: > > Why do you care about format?

Non SSL wor perfectly, but i need https://IP:8443 for another listeners. This I need, because chrome not play player in my web site (mixed content). Now is in my player in web site http://ip:8000, but website run in https V V pon., 29. jun. 2020 ob 09:15 je oseba Railgun <railgun.michael at gmail.com> napisala: > Try non SSL connection for localhost > > Ervin Bizjak

Dave Madsen Assistant Professor and Dept. Head, Mass Communication Morningside College 1501 Morningside Ave. Sioux City, IA 51106 Office: 712-274-5480 Cell: 712-490-3327 madsend at morningside.edu *From:* Icecast <icecast-bounces at xiph.org> *On Behalf Of *Gavin Stephens *Sent:* Sunday, March 8, 2020 10:25 AM *To:* Icecast streaming server user discussions <icecast at

<div dir="auto">For what it's worth, it's working in NZ/vodafone/android firefox for me<br></div><div style="line-height:1.5"><br><br>-------- Original message --------<br>From: Gavin Stephens <gavin@stephens.net.nz><br>Date: Mon, 15 Jun 2020, 15:59<br>To: icecast@xiph.org<br>Subject: Re: [Icecast]

Hello All, I had installed icecast2.2.4 with openSSL. I created a wordpress web site with SSL. If I stream with HTTPS under chrome , the player don’t work. If I stream without yes ! Could you please help me ? Thanks -------- Norbert Deleutre  <http://www.lmgc.univ-montp2.fr/perso/norbert-deleutre/> P 0467149655 UMR CNRS 5508  <http://www.lmgc.univ-montp2.fr/> A Campus

I have been trying to get icecast 2.4.2 to stream with ssl to https. But so far I have had no luck. I am running Ubuntu 16.04 and the regular stream is working properly over port 80. I want to stream securely over port 443. I need to use 443 because of network rules here. I can view the Icecast2 Status pages and listen to a stream, but once I add https:// I get 'Secure Connection Failed'

If you use Chrome, recent updates won't allow connections to an http server if the referring url is on an https server. I wonder how much additional CPU strain this causes when you have a few hundred plus listeners to encrypt everything. Anyway, this is the way it is now, unless you use the likes of .pls/.m3u files with the http server link for an external player. Cheers, Gavin. On

On 08/03/2020 16:24, Gavin Stephens wrote: > Sorry for the late update. I didn't realise the replies came and went > off list regarding this. > > 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. > > The error message I was getting in the Icecast

2.2.4? I didn't think SSL was implemented until version 2.4.3. What would be helpful, not to mention useful, is to explain specifically and exactly what goes into the key file. The choices are: your server's private key, your server's public key, your server's certifying authority (CA) key, maybe even the curl CA. I've also seen this in examples of the SSL stanza from

AFIK, pem is simply 1. private key 2. (most specific) certificate 3. intermediate certificates, if any in this order. at least such a pem work for my icecast 2.4 w/o problems --u Gavin Stephens: > > > > 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

And what should I do now? What suggestion? An IP-based certificate cannot be created or registered. V V ned., 28. jun. 2020 ob 20:05 je oseba Paul Martin <pm at nowster.me.uk> napisala: > On Sun, Jun 28, 2020 at 08:03:59AM +0200, Ervin Bizjak wrote: > > I not use domain for my icecast, but only localhost > http://localhost:8000 > > and https://localhost:8443. and

Hi Is anyone experiencing Icecast streams dropping out after about 8-12 seconds in Edge or IE? It's fine in Chrome or Firefox. It's also fine in the new Chromium based Edge. I have a number of listeners reporting it. It also happens on some of the streams in the http://dir.xiph.org/ Icecast directory (Alt Rock 97, Wakefield FM, KBSU, 80s 90s Hit Radio etc.). Here's one of my stream

Thomas B. Rücker: > After all, Icecast is just another web server. > > Please note the absence of 8000 and 8443. Neither are officially > specified for WWW type HTTP(S). They are commonly used as such, but 80 > and 443 are *much* better choices and should be preferred. makes sense, but if my webserver needs to serve http/s from the same IP, that would not work. Unless I want to

Hello! Sorry, but SSL in my windows where is installed icecast not work. Create certificate (.crt) and convert to .pem with openssl x509 -in mycert.crt -out mycert.pem -outform PEM certificate.pem copy to c:/icecast/cert/ Edit icecast.xml: <ssl-certificate>./cert/icecast.pem</ssl-certificate> <listen-socket> <port>8443</port> <ssl>1</ssl>

Hello, 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. 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. The radio

I set icecast.xmp: <listen-socket> <port>8000</port> </listen-socket> <listen-socket> <port>8443</port> <ssl>1</ssl> </listen-socket> 8000 work, 8443 not work. If set ssl to port 8000 not work nothing V V sob., 27. jun. 2020 ob 18:13 je oseba Paul Martin <pm at nowster.me.uk> napisala:

Thanks for the reply. And how do you have it then left it arranged? I have a windows system. Like I said I have a domain that is just parked and entered in the dns, but I don’t use it. This certificate also belongs to this domain. V V pon., 29. jun. 2020 ob 11:26 je oseba Paul Martin <pm at nowster.me.uk> napisala: > On Mon, Jun 29, 2020 at 09:20:37AM +0200, Ervin Bizjak wrote: >