NET::ERR_CERT_DATE_INVALID event after renewal

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., so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command: certbot renew

It produced this output:

My web server is (include version): JBOSS Wildfly 13

The operating system my web server runs on is (include version): CentOS 7

My hosting provider, if applicable, is: alibaba

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): 0.25.1

More info:


I did server reboot after renewal.
Following site shows the issue:

Hi @vovkind

you don’t use the new certificate:
2 days expired, - 2 entries


certbot -d -d

certbot should find your certificate and should ask, if you want to install that certificate.

If you have your JBoss server directly terminating TLS, then you may have imported the previous certificate by converting it to a different format (thinking of other Java-based web servers which often don’t understand PEM format directly). In that case, the process would need to be repeated every time you renew the certificate in order for the JBoss server to use the new certificate. (If so, you can use a --deploy-hook script with Certbot to automate this step.)

1 Like

10x for a quick reply. I’m using let’s encrypt certificate and renewed it some 2 weeks ago. Yesterday I got the issue with expired certificate.

Seems like I have a valid certificate, published screenshot in my original post.

More info:

[root@iZgw82uc2opm5jqlzywm7wZ bin]# ls -l /etc/letsencrypt/renewal /etc/letsencrypt/live/*
-rw-r–r-- 1 root root 740 Nov 22 00:27 /etc/letsencrypt/live/README

total 4
-rw-r–r-- 1 root root 692 Nov 22 00:27 README
lrwxrwxrwx 1 root root 39 Feb 2 16:21 cert.pem -> …/…/archive/
lrwxrwxrwx 1 root root 40 Feb 2 16:21 chain.pem -> …/…/archive/
lrwxrwxrwx 1 root root 44 Feb 2 16:21 fullchain.pem -> …/…/archive/
lrwxrwxrwx 1 root root 42 Feb 2 16:21 privkey.pem -> …/…/archive/

total 4
-rw-r–r-- 1 root root 689 Feb 2 16:21

What’t the content of this file?

renew_before_expiry = 30 days

version = 0.25.1

archive_dir = /etc/letsencrypt/archive/

cert = /etc/letsencrypt/live/

privkey = /etc/letsencrypt/live/

chain = /etc/letsencrypt/live/

fullchain = /etc/letsencrypt/live/

Options used in the renewal process


authenticator = webroot


server =

installer = None

[[webroot_map]] = /root/SOME_SERVER_FOLDER = /root/SOME_SERVER_FOLDER

You don’t have an installer.

So how did you installed the certificate?


Manually. As described in tutorial.

Is this root cause? How to fix it?
10x a lot for your help!

Yes, every renewal is a new certificate which must be reimported into your web server in the same way as the original was imported. I don’t think a tutorial that omits this information is very helpful!

You can write a script to automate the process and then specify it to Certbot with --deploy-hook; after this, the script will be run automatically every time Certbot performs a renewal.

Which tutorial?

Delete certs (certbot delete) and importing everything from scratch (keys, adding certs via certbot certonly) was working for me.

thank you, guys.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.