Renewed certificate but still using expired

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:www.rinex.org.rw

I ran this command:certbot certificates

It produced this output:Found the following certs:
Certificate Name: www.rinex.org.rw
Domains: www.rinex.org.rw
Expiry Date: 2019-08-26 08:43:06+00:00 (VALID: 89 days)
Certificate Path: /etc/letsencrypt/live/www.rinex.org.rw/fullchain.pem
Private Key Path: /etc/letsencrypt/live/www.rinex.org.rw/privkey.pem


My web server is (include version): Apache/2.4.7 (Ubuntu)

The operating system my web server runs on is (include version):Ubuntu 14.04.5 LTS

My hosting provider, if applicable, is: i have access to the server.

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):certbot 0.31.0

i have renewed the new certificate but it still it is still expired.

Hi @buregeya

there are your older topics:

I don't have a solution. And I don't understand your configuration.

@_az and I had the same question: Your "Apache" doesn't look like an Apache.

So that instance may have it's own configuration file, so the shared configuration isn't used.

But if you don't know the details of your own configuration, it's impossible to find a solution.

these are steps are used to install certificate:
sudo add-apt-repository ppa:certbot/certbot
sudo apt-get install python-certbot-apache
sudo certbot --apache -d www.rinex.org.rw
sudo certbot renew --dry-run

the certificate renewed but using the expired certificate i don’t know why…

Currently, your web server seems not to be replying at all—there is just a firewall or something returning a completely empty reply to HTTPS requests.

hello @schoen now it is replying please help me
with this issue

Thinking about that curious problem, now I had another idea:

Is it possible that you have done these steps

then you have installed another component. That component comes with it's own Apache (or something else), uses the Apache config files to configure the own webserver.

So it's not your original Apache. And updating the certificate of that original Apache doesn't change the configuration of that other component?

1 Like

yaah exactly i have installed new apache and i renewed it using that new apache .
is there any issue with that.

Looks that you have broken your configuration.

Where do you run certbot? What's the ip address of your machine? Not the ip address of your website - perhaps you use Certbot on the wrong machine.

Oh, what’s that? Now your configuration is broken ( https://check-your-website.server-daten.de/?q=rinex.org.rw ):

Domainname Http-Status redirect Sec. G
http://rinex.org.rw/
196.49.7.181 200 1.094 H
http://www.rinex.org.rw/
196.49.7.181 200 1.087 H
https://rinex.org.rw/
196.49.7.181 -4 0.770 W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send. Authentication failed because the remote party has closed the transport stream.
https://www.rinex.org.rw/
196.49.7.181 -4 0.747 W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send. Authentication failed because the remote party has closed the transport stream.

Why is there now a W - answer? Earlier, your configuration had worked.

And why did you create the next certificates?

CertSpotter-Id Issuer not before not after Domain names LE-Duplicate next LE
935790956 CN=Let’s Encrypt Authority X3, O=Let’s Encrypt, C=US 2019-05-28 11:55:37 2019-08-26 11:55:37 rinex.org.rw
1 entries duplicate nr. 1
935564467 CN=Let’s Encrypt Authority X3, O=Let’s Encrypt, C=US 2019-05-28 08:43:06 2019-08-26 08:43:06 www.rinex.org.rw
1 entries duplicate nr. 5 next Letsencrypt certificate: 2019-06-03 08:18:57
935432283 CN=Let’s Encrypt Authority X3, O=Let’s Encrypt, C=US 2019-05-28 07:05:34 2019-08-26 07:05:34 www.rinex.org.rw
1 entries duplicate nr. 4
935962133 CN=Let’s Encrypt Authority X3, O=Let’s Encrypt, C=US 2019-05-28 06:20:59 2019-08-26 06:20:59 www.rinex.org.rw
1 entries duplicate nr. 3
933295841 CN=Let’s Encrypt Authority X3, O=Let’s Encrypt, C=US 2019-05-27 08:20:31 2019-08-25 08:20:31 www.rinex.org.rw
1 entries duplicate nr. 2
933293033 CN=Let’s Encrypt Authority X3, O=Let’s Encrypt, C=US 2019-05-27 08:18:57 2019-08-25 08:18:57 www.rinex.org.rw
1 entries duplicate nr. 1
933211532 CN=Let’s Encrypt Authority X3, O=Let’s Encrypt, C=US 2019-05-27 07:15:26 2019-08-25 07:15:26 rinex.org.rw, www.rinex.org.rw
2 entries duplicate nr. 5 next Letsencrypt certificate: 2019-05-29 12:42:45
927612313 CN=Let’s Encrypt Authority X3, O=Let’s Encrypt, C=US 2019-05-23 13:30:43 2019-08-21 13:30:43 rinex.org.rw, www.rinex.org.rw
2 entries duplicate nr. 4
927287297 CN=Let’s Encrypt Authority X3, O=Let’s Encrypt, C=US 2019-05-23 09:17:39 2019-08-21 09:17:39 rinex.org.rw, www.rinex.org.rw
2 entries duplicate nr. 3
925741597 CN=Let’s Encrypt Authority X3, O=Let’s Encrypt, C=US 2019-05-22 12:53:55 2019-08-20 12:53:55 rinex.org.rw, www.rinex.org.rw
2 entries duplicate nr. 2
925725754 CN=Let’s Encrypt Authority X3, O=Let’s Encrypt, C=US 2019-05-22 12:42:45 2019-08-20 12:42:45 rinex.org.rw, www.rinex.org.rw
2 entries duplicate nr. 1

You have already a lot of working certificates. It doesn’t help if you create new certificates but don’t use these. Now you have two times hittet the limit.

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