Expiration date and mail

Je peux lire des réponses en Anglais : OUi

Mon nom de domaine est :cloud.rivard-international.com
Debian 9

1- Is it possible to check the sending of renewal mail because I received nothing this time?

cerbot-auto certificates
commande introuvable

2- How do we check the date for renewal of the certificate?

I tried on https://check-your-website.server-daten.de/ but he can not find anything
and if i put cloud.rivard-international.com:xxxx i got this back:
A job with this domain name is already running. Do not start two jobs. Perhaps the Nameservers are terrible slow.

Hi @doubleve

there is your information - https://check-your-website.server-daten.de/?q=cloud.rivard-international.com#ct-logs

Issuer not before not after Domain names LE-Duplicate next LE
Let’s Encrypt Authority X3 2019-11-06 2020-02-04 cloud.rivard-international.com
1 entries duplicate nr. 1
Let’s Encrypt Authority X3 2019-08-08 2019-11-06 cloud.rivard-international.com
1 entries
Let’s Encrypt Authority X3 2019-08-08 2019-11-06 cloud.rivard-international.com
1 entries
Let’s Encrypt Authority X3 2019-08-08 2019-11-06 cloud.rivard-international.com
1 entries

Last certificate is created 2019-11-06, you can use it 90 days -> 2020-02-04.

But your installation is wrong - Grade Q, http over port 443. So you don’t have a working https port.


has the standard Apache page. And your http doesn’t work, looks like a wrong configured http port, so Certbot is unable to create a https port.

1 Like

port 443 and 80 are unusable they are replaced by port 4433 and 8080

1 Like

Then check the port directly.

1 Like

concretely what should I do to remedy the problem?
and for email addressing you have an idea?

There is a check with your port - https://check-your-website.server-daten.de/?q=cloud.rivard-international.com:4433

There is no problem visible. https + 4433 works, Grade B, so the certificate is valid.

expires in 89 days	cloud.rivard-international.com - 1 entry

The not working http is normal, if a port is checked, that’s not a problem.

But I don’t understand why your standard ports aren’t used, you don’t need these non-standard ports.

Mails: Read

1 Like

To focus on the relevant part of that, the Let’s Encrypt expiration e-mails are sent if Let’s Encrypt has not issued a new certificate with exactly the same names as the previous (expiring) certificate. Let’s Encrypt does not attempt to check whether the newly-issued certificate has been installed or is being used anywhere.

1 Like

I do not use standard ports because I have other servers that use them

1 Like

I created my certificate 3 months ago, yesterday my nextcloud told me that my certificate was wrong but I have not received an email to warn me

As @schoen said, Let’s Encrypt does not verify that your certificate is properly installed and functioning. All it does it check if one has been issued. If one has not been issued to replace an expiring certificate you will recieve an email.

Checking crt.sh (https://crt.sh/?q=cloud.rivard-international.com) I can see a new certificate was issued yesterday, November 6th, As a result an expiration email was not sent since your certificate was successfully renewed. You should reconfigure your webserver to use this new certificate.

1 Like