similar to: icecast and SSL

Thanks chip! Thats working. Thanks a lot Kind regards, Marv Op 10 dec. 2019 om 19:51 heeft Chip <chiapas at aktivix.org> het volgende geschreven: > >  > How about this: > https://serverok.in/centovacast-enable-ssl-on-icecast > You're welcome. Don't mention it :o) > > Chip Scooter > > On Mon, 9 Dec 2019 at 12:54, Marvin | OveralWiFi.nu <marvin at

@Mikel You could use Centova's port 80 proxy meanwhile couldn't you? Also. Centova Cast doesn't have an SSL setting for the servers unless you're manually overwriting the server config files.. or is it? On Sat, Feb 29, 2020 at 6:13 PM Mikel Sanz | 20 Comunicación < mikel at 20comunicacion.com> wrote: > For example, in my case, we use several servers with Centovacast,

Hello all, I’ve a problem to set up ssl on icecast server. I’ve tried 2/3 certificates and i compiled a new icecast server file with ssl but i still get the error:ssl, no ssl capability in error log icecast. I cant find the solution. I use centos 7 with centova cast panel Who can help me? Thanx in advance Marv

First I would recommend to run make uninstall from the location you ran make install before to clean up what it already installed in the wrong location. Then repeat the ./configure ... step but without the prefix: ./configure --with-curl --with-openssl then make and make install, which should install Icecast to /usr/local with the Icecast binary in /usr/local/bin and the configuration

Hi, the guide you followed is not really correct for the usecase you have unless you use CentovaCast, which I guess you do not? On 17 Oct 2020, at 13:19, Bananradion wrote: > Thanks for the fast reply, but that didn't help either. > > What is supposed to happened after "make install" > I see: > > Making install in examples > make[1]: Entering directory

On 17 Oct 2020, at 15:14, Bananradion wrote: > I tried that, but i'm not sure what´s supposed to happen after "make > install" is done? Nothing us supposed to happen afterwards. The log you posted looks like it successfully installed everything. > > Making install in examples > make[1]: Entering directory '/home/pi/icecast-2.4.4/examples' > make[2]:

No, I don't have centovacast.. i just want to use icecast with ices2. But icecast has to have ssl enabled. Den lör 17 okt. 2020 kl 13:55 skrev Marvin Scholz <epirat07 at gmail.com>: > Hi, > > the guide you followed is not really correct for the usecase you have > unless you use CentovaCast, which I guess you do not? > > On 17 Oct 2020, at 13:19, Bananradion wrote:

Where does the value for ssl-allowed-ciphers come from? On 10/17/2020 5:19 AM, Chip wrote: > Try this: > > * 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,

Thanks for the fast reply, but that didn't help either. What is supposed to happened after "make install" I see: Making install in examples make[1]: Entering directory '/usr/local/src/icecast-2.4.4/examples' make[2]: Entering directory '/usr/local/src/icecast-2.4.4/examples' make[2]: Nothing to be done for 'install-exec-am'. make[2]: Nothing to be done for

I tried that, but i'm not sure what´s supposed to happen after "make install" is done? Making install in examples make[1]: Entering directory '/home/pi/icecast-2.4.4/examples' make[2]: Entering directory '/home/pi/icecast-2.4.4/examples' make[2]: Nothing to be done for 'install-exec-am'. make[2]: Nothing to be done for 'install-data-am'. make[2]:

Can someone please compile the latest icecast version with ssl for raspbian/debian? Regards.. Daniel Den lör 17 okt. 2020 kl 16:44 skrev Steve Matzura <sm at noisynotes.com>: > Where does the value for ssl-allowed-ciphers come from? > > > On 10/17/2020 5:19 AM, Chip wrote: > > Try this: > > - https://serverok.in/centovacast-enable-ssl-on-icecast > > If

Hi These instructions are very useful, as previously shared: - https://serverok.in/centovacast-enable-ssl-on-icecast However, I think this step caused me problems using Letsencrypt (LE) and the icecast.pem file might have been in error: Paste your SSL in following order 1) Your private key 2) Your SSL cert 3) CA Bundle I don't think LE creates a 'CA Bundle'. Following some

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 would expect the public cert to be imported as a "server" not an "auth" The attached image shows that TBird wants an httpS url for a webserver, for the source. Ages ago, I think it prompted for "do you want to trust this new cert" and YES added it (assuming that is the public key) to the server list.? A bit confused by this. <see attached thunderbird

Our DC has been using a Verisign certificate. Over the past year, we've been using a Digicert Wildcard Plus certificate for almost all of our machines, and I wanted to switched over our DC mailserver. I used the following command to generate the CSR and key: openssl req -new -newkey rsa:1024 -nodes -out star_bard_edu.csr -keyout star_bard_edu.key -subj "/C=US/ST=NY/L=ourtown/O=Bard

<!doctype html> <html><head> <meta charset="UTF-8"> </head><body><div>I see. You need to import the cert into thundebird's trusted ca certs.</div><div><br></div><div>Aki</div><blockquote type="cite"><div>On 30/04/2020 21:36 <a

Dear community, My webradio is currently appearing in Icecast directory there http://dir.xiph.org/search?search=onstreet I didn't do it It surely was done directly by my streaming provider radionomy. In radionomy I have access to nothing but the stream link http://listen.radionomy.com/onstreet The thing is we are leaving radionomy for another stream provider. How to keep appearing in

Hi, I have ecommerce stores on my server who use the same instantssl certificate without any problems. These particular certificates were migrated over from one plesk system to my new server with centOS 3.4 and plesk 7.5.1 reloaded. When I generated a new csr for a new client on my centOS server and chose apache mod_ssl at instantssl for the csr I got the certificate, installed it (first new

Hello, After countless hours on, this I found the root cause of HTTPS settings on Debian Buster. All this came from ast_tls_cert script using 1024 bits-long keys where Debian's defaut was to require at least 2048-long keys ! Simply passing -b 2048 to ast_tls_cert solved it. 1. May I suggest mentioning explicitly this possibility in wiki page [1] ? 2. What would you say of adding an extra