Hi Philipp,
Thanks for your reply. For now I will continue with 2.4.4 and just do things
manually, with an eye to using a more automated process when I move over to
version 2.5.
I realise that it is generally not recommended, but can you tell me whether you
think version 2.5 is generally stable enough to use for production at this
stage?
Also, is it recommended that we also follow the LinkedIn page at
https://www.linkedin.com/company/loewenfelsen/
<https://www.linkedin.com/company/loewenfelsen/> for important info about
Icecast development?
Damian
> On 11 Mar 2022, at 6:55 pm, Philipp Schafft <phschafft at
de.loewenfelsen.net> wrote:
>
> Good Morning,
>
> On Fri, 2022-03-11 at 14:05 +1300, Ross Levis wrote:
>> Is there any method to do that on Windows?
>
> There is a reload link on the admin web interface on 2.5.x.
>
> It points to /admin/reloadconfig.xsl; if you want to do it
> programmatically you can just call /admin/reloadconfig with admin
> credentials.
>
> Reloading via API is not yet supported by 2.4.4.
>
>
> With best regards,
>
>> From: Icecast [mailto:icecast-bounces at xiph.org
<mailto:icecast-bounces at xiph.org>] On Behalf Of
>> Alejandro Ferrari
>> Sent: Friday, 11 March 2022 12:54 pm
>> To: Icecast streaming server user discussions
>> Subject: Re: [Icecast] Icecast2 and SSL certificate renewal
>>
>> Hi Damian,
>>
>> Kill -HUP $PID
>>
>> That will reload the config without stop the streams.
>>
>> El jue, 10 mar 2022 a la(s) 18:57, Damian (db76 at riseup.net)
escribi?:
>>> Hi
>>>
>>> I have a question about current best-practice for renewing SSL
>>> certificates for Icecast.
>>> I am looking into automating the renewal process for my SSL
>>> certificate using Let?s Encrypt.
>>> However, it?s my understanding that the Icecast server would need
>>> to be restarted each time the automatic process takes place (every
>>> 3 months) which I think would be disruptive to running a continuous
>>> streaming service.
>>> All the listeners would be kicked off the streams.
>>>
>>> I?d like to know if anyone knows of a better solution or if this is
>>> just an unavoidable problem in terms of running streams via HTTPS.
>>>
>>> Thanks for any help
>>>
>>> Damian
>
>
> --
> Philipp Schafft (CEO/Gesch?ftsf?hrer)
> Telephon: +49.3535 490 17 92
> Website: https://www.loewenfelsen.net/
<https://www.loewenfelsen.net/>
> Follow us: https://www.linkedin.com/company/loewenfelsen/
<https://www.linkedin.com/company/loewenfelsen/>
>
> L?wenfelsen UG (haftungsbeschr?nkt) Registration number:
> Bickinger Stra?e 21 HRB 12308 CB
> 04916 Herzberg (Elster) VATIN/USt-ID:
> Germany DE305133015
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org <mailto:Icecast at xiph.org>
> http://lists.xiph.org/mailman/listinfo/icecast
<http://lists.xiph.org/mailman/listinfo/icecast>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.xiph.org/pipermail/icecast/attachments/20220312/72b9bf4a/attachment.htm>