# Certificate renewed, old one is used

**URL:** <https://community.letsencrypt.org/t/certificate-renewed-old-one-is-used/39632>\
**Category:** Help\
**Created:** [August 6, 2017, 9:12pm UTC](https://community.letsencrypt.org/t/certificate-renewed-old-one-is-used/39632 "2017-08-06T21:12:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mat-m](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mat-m/32/15422_2.png) [@mat-m](https://community.letsencrypt.org/u/mat-m)\
**Post date:** [August 6, 2017, 9:12pm UTC](https://community.letsencrypt.org/t/certificate-renewed-old-one-is-used/39632/1 "2017-08-06T21:12:29Z")

</div>

My domain is: [grenier.mcxi.eu](http://grenier.mcxi.eu)

I ran this command:

```
certbot certificates

```

It produced this output:

```
Certificate Name: grenier.mcxi.eu
Domains: grenier.mcxi.eu
Expiry Date: 2017-10-01 21:41:00+00:00 (VALID: 56 days)
Certificate Path: /etc/letsencrypt/live/grenier.mcxi.eu/fullchain.pem
Private Key Path: /etc/letsencrypt/live/grenier.mcxi.eu/privkey.pem

```

My web server is (include version):

```
nginx version: nginx/1.10.3
built with OpenSSL 1.0.2k 26 Jan 2017
TLS SNI support enabled

```

The operating system my web server runs on is (include version): `Raspbian GNU/Linux 8.0 (jessie)`

My hosting provider, if applicable, is: self-hosted

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

But if you connect to my server, you see the old certificate.  
My current config in nginx is:

```
listen 443 ssl;
server_name grenier.mcxi.eu ;

ssl on;
ssl_certificate /etc/letsencrypt/live/grenier.mcxi.eu/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/grenier.mcxi.eu/privkey.pem;

```

Let me know if you need more details

---

<div class="post-metadata">

**Author:** ![sahsanu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sahsanu/32/89984_2.png) [@sahsanu](https://community.letsencrypt.org/u/sahsanu)\
**Post date:** [August 6, 2017, 9:46pm UTC](https://community.letsencrypt.org/t/certificate-renewed-old-one-is-used/39632/2 "2017-08-06T21:46:20Z")

</div>

Hi @mat-m,

Your web server is using the last certificate that is vaild till October 1st:

 ![imagen](https://sea3.discourse-cdn.com/letsencrypt/uploads/default/original/2X/2/2322e7a478dcb0f9596ffedb6911eb50751c91f1.png)

I see no problem at all.

Cheers,  
sahsanu

---

<div class="post-metadata">

**Author:** ![jsha](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jsha/32/12_2.png) [@jsha](https://community.letsencrypt.org/u/jsha)\
**Post date:** [August 6, 2017, 9:56pm UTC](https://community.letsencrypt.org/t/certificate-renewed-old-one-is-used/39632/3 "2017-08-06T21:56:34Z")

</div>

The most common cause of this kind of problem is that nginx isn’t being reloaded after renewal. If you use --nginx this happens automatically; otherwise use --deploy-hook (–renew-hook on older versions)

---

<div class="post-metadata">

**Author:** ![mat-m](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mat-m/32/15422_2.png) [@mat-m](https://community.letsencrypt.org/u/mat-m)\
**Post date:** [August 6, 2017, 10:05pm UTC](https://community.letsencrypt.org/t/certificate-renewed-old-one-is-used/39632/4 "2017-08-06T22:05:05Z")

</div>

Ok, so I probably had a certifcate cache issue in my browsers.  
But I may have missed a previous reloading.

Now it is fine.

I will investigate the hook option.

Thank you

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [September 5, 2017, 10:05pm UTC](https://community.letsencrypt.org/t/certificate-renewed-old-one-is-used/39632/5 "2017-09-05T22:05:17Z")

</div>

Closed on September 5, 2017, 10:05pm UTC

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