Hi there,
our monitoring service reports problems with a let’s encrypt certificate daily. It reports the following error and after a few minutes reports that everything is fine again:
##################################################
The following monitor failed on one or more recent checks.
Error: 3019 - HTTPS certificate could not be validated
Monitor: http://www.diakonie-ruhr-hellweg.de
URL: https://www.diakonie-ruhr-hellweg.de
Start of error: 18.02.2019 12:22 (View error: https://app.uptrends.com/Report/ProbeLog/Check/33303558500)
Consecutive errors: 3
Last checked: 18.02.2019 12:42
Last checkpoint: New York, NY, USA
Warnung
This is an automated message from Uptrends. Do not reply to this e-mail.
##############################################################
When there error doesn’t occur, the cert works just fine. Can you anyone help us with this?
greetings from germany
Fabio Stegmeyer
Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: https://www.diakonie-ruhr-hellweg.de
I ran this command:
It produced this output:
My web server is (include version): Apache 2.2.22
The operating system my web server runs on is (include version): Debian 3.2.88
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don’t know): yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): no
The version of my client is (e.g. output of certbot --version
or certbot-auto --version
if you’re using Certbot):