[Icecast] SSL-Question

Ervin Bizjak ervin.bizjak at gmail.com
Thu Jun 11 12:17:23 UTC 2020


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 capability on
any configured ports

V V čet., 11. jun. 2020 ob 13:37 je oseba Chip <chiapas at aktivix.org>
napisala:

> 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 interpret.
>
> Hope that helps
>
> Chip Scooter
>
> On Thu, 11 Jun 2020 at 12:18, Ervin Bizjak <ervin.bizjak at gmail.com> wrote:
>
>> 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>
>> </listen-socket>
>>
>> I don't know what can I do wrong
>>
>> V V pet., 2. avg. 2019 ob 03:47 je oseba <
>> webmaster at berean-biblechurch.org> napisala:
>>
>>> On 2019-07-31 09:44, unosonic wrote:
>>> > 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 use Icecast as a nginx or apache
>>> > replacement ;)
>>>
>>> Uno, could you create a sub-domain, like radio.yoursite.com, and have
>>> it
>>> point to the Icecast server?
>>> _______________________________________________
>>> Icecast mailing list
>>> Icecast at xiph.org
>>> http://lists.xiph.org/mailman/listinfo/icecast
>>>
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org
>> http://lists.xiph.org/mailman/listinfo/icecast
>>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200611/1d2af6c4/attachment.htm>


More information about the Icecast mailing list