similar to: Solved: New Certificate - reload or restart

On 31 Jul 2024, at 0:05, Steve Matzura wrote: > I tried everything, including changing the name of the new PEM containing the properly concatenated certificates as specified in the Icecast configuration. The reload command did not, does not appear to, re-read the certificate file even though the filename has been changed. To make it work, I had to restart the Icecast server in the usual

On Sat, 13 Jun 2015 21:57:06 +0200, you wrote: >On Sat, Jun 13, 2015 at 03:41:26PM -0400, Steve Matzura wrote: >> >> > > Trying ::1... # this is certainly suspect >> >> > > Escape character is '^['. >> >> > > Connection closed by foreign host. > >This means the daemon is listening but errors out before able to process.

The public cert part is good, but the private one begins with "Begin private key", not "RSA key." On Sun, 14 Jun 2015 15:54:23 +0200, you wrote: >Am 13.06.2015 um 22:11 schrieb Steve Matzura: >> On Sat, 13 Jun 2015 21:57:06 +0200, you wrote: >> >>> On Sat, Jun 13, 2015 at 03:41:26PM -0400, Steve Matzura wrote: >>>>>>>> Trying

Alex, et al., I spoke too soon. Upon close examination of /var/log/maillog, the errors previously reported via the maillog extracts only happen when I attempt to test the imap connection. Everything appears correctly set up, defined, etc. It's now down to the certificates themselves I think. I have the following files: . A file containing the certificate as issued by the certifying uthority

On 3/14/19 9:32 AM, Yassine Chaouche via dovecot wrote: > The general answere here is try and see, as you could totally test it > on your own. The certificate is read at startup and put in memory for > the rest of the execution time. Dovecot won't monitor the file for > changes on disk, as this would waste CPU cycles and make dovecot only > slower for no reason. The process

On Thu, Mar 14, 2019, at 11:33 AM, Yassine Chaouche via dovecot wrote: > On 3/14/19 9:32 AM, Yassine Chaouche via dovecot wrote: > > The general answere here is try and see, as you could totally test it > > on your own. The certificate is read at startup and put in memory for > > the rest of the execution time. Dovecot won't monitor the file for > > changes on

Looks like a lot of tedium. I'll give it a go on Red Hat, but not before a full backup first. On Wed, 7 Jan 2015 11:26:13 -0800, you wrote: >Hello, > >Fedora and CentOS don't have any prebuilt packages in the standard repos. > >Here are a few guides from the Liquidsoap community, specific to CentOS. >http://puck.in/2013/12/install-liquidsoap-1-1-on-centos-6-4/

I could, but I have this big old Fedora system just waiting for me to get LS working on it, so I think I need to concentrate on making that happen. If it's hard, difficult, tedious, inconvenient, then that's what it is. I want the cue sheet capability some way somehow, so I'm just going to have to knuckle down and buckle down and do it. Right? On Wed, 7 Jan 2015 17:21:27 -0800, you

Looks like it's what I need. Do you know, is there a distro or repo for Fedora? Or should I build it from source? On Wed, 7 Jan 2015 07:56:39 -0800, you wrote: >Hi Steve. > >Liquidsoap supports CUE sheets as an input. > >http://savonet.sourceforge.net/doc-svn/playlist_parsers.html >On Jan 7, 2015 5:04 AM, "Steve Matzura" <sm at noisynotes.com> wrote: >

Running dovecot 2.2, apologies if this question has been asked before: I've done the research but couldn't find anything. I run a server that uses dovecot as a MUA for Postfix and have a Let's Encrypt certificate that auto-renews through certbot on Ubuntu server 16.04. Dovecot did not pick up on the new certificate for the hostname. It did after a restart. To be clear: Let's

Hi, On 14.03.19 09:33, Yassine Chaouche via dovecot wrote: > On 3/14/19 9:32 AM, Yassine Chaouche via dovecot wrote: >> The general answere here is try and see, as you could totally test it >> on your own. The certificate is read at startup and put in memory for >> the rest of the execution time. Dovecot won't monitor the file for >> changes on disk, as this

The general answere here is try and see, as you could totally test it on your own. The certificate is read at startup and put in memory for the rest of the execution time. Dovecot won't monitor the file for changes on disk, as this would waste CPU cycles and make dovecot only slower for no reason. The process (or person) that changes the file is responsible to restart dovecot to reload

On Thu, Mar 14, 2019, at 12:09 PM, Yassine Chaouche via dovecot wrote: > On 3/14/19 9:55 AM, Patrick Cernko via dovecot wrote: > > > [...] the way we have configured exim, it neither needs reload or > > restart but reads the certificate file every time it has to use it. > > What happens if you goof off in the middle of an opeartion, temporarily > putting a wrong file

I purchased a new SSL certificate and installed it correctly, using the same combine procedures I?ve always used. I tried to reload the configuration, but it didn?t work. When I try the secure port, it still tells me my key has expired. I have to really think hard about when it will be appropriate to restart the server, so I was hoping that reload would work. Looks like a restart is needed. Is

On 3/14/19 9:55 AM, Patrick Cernko via dovecot wrote: > [...] the way we have configured exim, it neither needs reload or > restart but reads the certificate file every time it has to use it. What happens if you goof off in the middle of an opeartion, temporarily putting a wrong file instead of the new certificate, and exim starts delivering the new broken certificate right away ? or

Can anyone recommend any program newer than the last release of Liquidsoap, which, unless I misread the page, was in 2007?

On Mon, 6 Apr 2015 17:47:38 +0200, you wrote: >Hello Steve! > >2015-04-02 17:32 GMT+02:00 Steve Matzura <sm at noisynotes.com>: >> Ya know, there are none so blind ... IT'S BEEN COMMENTED OUT! >> >> <security> >> <chroot>0</chroot> >> <!-- >> <changeowner> >>

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

I wound up finding and using an IceS augmentation called Centova Cast, which built, made and installed without a single error on my 64-bit system. It's IceS 0.4 with a couple additions. It's running now and behaving as it should, so this might be a solution for you as well. The install script is intense. It downloads everything you need, resolves dependencies, installs them, logs

Unfortunately, Dennis, my source stream is 128kbps and will never go higher. Is Liquidsoap still a good idea? On Fri, 04 Mar 2016 14:48:41 +0100, you wrote: >Great tool to do this: liquidsoap > >Keep in mind that transcoding degrades the quality of tour stream dramaticly. You can avoid this by feeding liquidsoap or stream transcoder with a highquality or even transparant stream and