Thanks for the reply. I put all the different certs into different subdirectories, so I know it's that one, e.g.: /apachepath/conf.d/cert1 /apachepath/conf.d/cert2 /apachepath/conf.d/cert3 It, too, complains about the "/apachepath/conf.d/cert3/domain.crt" file, which comes from the provider anyway. I know it's the correct/new/latest one (date,size and from tests). Jobst On Mon, Jan 20, 2014 at 03:01:20AM +0100, Reindl Harald (h.reindl at thelounge.net) wrote: > > > Am 20.01.2014 02:23, schrieb Jobst Schmalenbach: > > I updapted the ssl certificate on the 15th of Jan using the providers update facility. > > Then I downloaded the new certificate, installed it and restarted httpd. > > > > Then I checked with the providers "ssl installation diagnostic tool" whether everything is fine - and it is, all reported good. > > > > Then I opened a browser, loaded the https website, checked the certificate and it's valid until 8/02/2017, which was reported by above, as well. > > > > I know I could turn certwatch off, but I like the warning as I have a few certs on different websites, domains and machines. > > > > How come certwatch is still complaining? > > look about *what* certificate it complains > certwatch looks at *all* certificates and you have changed *one* > -- If proof denies faith, and uncertainty denies proof, then uncertainty is proof of God's existence. | |0| | Jobst Schmalenbach, jobst at barrett.com.au, General Manager | | |0| Barrett Consulting Group P/L & The Meditation Room P/L |0|0|0| +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia