similar to: SSL ports

I have ice cast up on my server, ssl is working as intended and I have both a standard feed and ssl port working. Only big issue I have is even though the SSL port is set for 443 it is also running on Port 80. Is there some reason port 80 is running alongside 80 and is there a way to run it without Port 80 being used?

Hi John, El vie, 22-09-2017 a las 16:50 +0000, Zernick, John escribió: > > 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

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 icecast.pem and un-remarked the path to get it to read the file in the Icecast

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

Hi This is for Linux but you might be able to find something useful in there for your situation: - https://serverok.in/centovacast-enable-ssl-on-icecast If you are using Letsencrypt then this, IMHO, is a good way to make the icecast.pem file: cat privkey.pem fullchain.pem > icecast.pem The above creates a useful SSL cert format which, for example, a range of devices are able to

I copy certificate.crt and private.key to one file and this file convert to .pem. This is in icecast error.log: [2020-06-11 13:37:30] INFO main/main.c Icecast 2.4.4 server started [2020-06-11 13:37:30] INFO yp/yp.c YP update thread started [2020-06-11 13:37:30] WARN connection/connection.c Invalid private key file ./cert/icecast.pem [2020-06-11 13:37:30] INFO connection/connection.c No SSL

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'

Install letsencrypt and request a certificate specifying the webroot of your Icecast server and the host.domain: certbot-auto certonly --webroot --webroot-path /usr/share/icecast2/web/ -d icecast.domain.name Now you should have a certificate for your server, it's only in the wrong format for Icecast, copy the key and the certificate to 1 file with the following cmd: cat

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>

El lun, 28-08-2017 a las 20:23 +0000, Speagle, Andy escribió: > > > > > > > Hi Folks, > > > > > > > > > > > > > > I’m having a problem getting a the SSL cert file > > > > > > > formatted > > > > > > > just like icecast wants… I’m running 2.4.2 … and it > > > > > > >

El lun, 28-08-2017 a las 21:37 +0000, Speagle, Andy escribió: > > > > > > > > > Hi Folks, > > > > > > > > > > > > > > > > > > I’m having a problem getting a the SSL cert file > > > > > > > > > formatted > > > > > > > > > just like icecast wants… I’m running 2.4.2

> > > > > > Hi Folks, > > > > > > > > > > > > I’m having a problem getting a the SSL cert file formatted > > > > > > just like icecast wants… I’m running 2.4.2 … and it doesn’t > > > > > > seem to want to use my combined key + cert chain no matter in > > > > > > what order I put it. >

El lun, 28-08-2017 a las 21:56 +0000, Speagle, Andy escribió: > > > > > > > > > > > Hi Folks, > > > > > > > > > > > > > > > > > > > > > > I’m having a problem getting a the SSL cert file > > > > > > > > > > > formatted just like icecast wants… I’m running > >

Hi Andy, El lun, 28-08-2017 a las 19:05 +0000, Speagle, Andy escribió: > > > > > Hi Folks, > > > > > > > > > > I’m having a problem getting a the SSL cert file formatted > > > > > just > > > > > like icecast wants… I’m running 2.4.2 … and it doesn’t seem > > > > > to > > > > > want to use my

"Speagle, Andy" <andy.speagle at wichita.edu>Hi Andy, El lun, 28-08-2017 a las 13:46 +0000, Speagle, Andy escribió: > > El vie, 25-08-2017 a las 16:49 +0000, Speagle, Andy escribió: > > > Hi Folks, > > > > > > I’m having a problem getting a the SSL cert file formatted just > > > like > > > icecast wants… I’m running 2.4.2 … and it

Hi, I'm using Icecast on Windows with a public TLS (SSL) mount with a Let's Encrypt cert. I had to configure two things in the icecast.xml: <listen-socket> <port>443</port> <bind-address>192.168.1.35</bind-address> <ssl>1</ssl> </listen-socket> (NOTE: I'm not sure if the above is needed for the public mount URL. Maybe an expert

I use Let's Encrypt for SSL with icecast. Here is my rudimentary script on GitHub... It does NOT require Apache or nginx. https://github.com/amavarick/letsencrypt_certbot_standalone_icecast On Jul 10, 2017, at 9:39 AM, ScanCaster <scancaster at scancaster.net<mailto:scancaster at scancaster.net>> wrote: On Mon, 10 Jul 2017 09:31:06 +0000, Philipp Schafft wrote: Good morning,

Hi, On 08/12/2018 02:04 AM, subscription at nextdial.com.br wrote: > Hello, >   > At a test VPS running Ubuntu 16.04 LTS I did this: > > 1. sudo apt-get update > 2. sudo add-apt-repository ppa:certbot/certbot > 3. sudo apt-get install certbot > You'll need an additional step at this point, see below. > 1. sudo apt-get install icecast2 > 2. sudo certbot

Hello everyone. Thanks a lot! I got it working. Frankly speaking I had already tested the setup proposed, but I made two mistakes, first i tried to setup the port 443 and it was stupid as this port is already used by web service https. Second mistake was the .pem file that probably was wrongly concatenated and was not recognized/loaded by icecast. However I confirm that in most places on

> > > > Hi Folks, > > > > > > > > I’m having a problem getting a the SSL cert file formatted just > > > > like icecast wants… I’m running 2.4.2 … and it doesn’t seem to > > > > want to use my combined key + cert chain no matter in what order I > > > > put it. > > > > Presently, I have it in this format.. with