# New certificate is not coming

**URL:** <https://community.letsencrypt.org/t/new-certificate-is-not-coming/107534>\
**Category:** Help\
**Created:** [November 30, 2019, 11:18am UTC](https://community.letsencrypt.org/t/new-certificate-is-not-coming/107534 "2019-11-30T11:18:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![turkdoktoru](https://avatars.discourse-cdn.com/v4/letter/t/3e96dc/32.png) [@turkdoktoru](https://community.letsencrypt.org/u/turkdoktoru)\
**Post date:** [November 30, 2019, 11:18am UTC](https://community.letsencrypt.org/t/new-certificate-is-not-coming/107534/1 "2019-11-30T11:18:14Z")

</div>

I’m using a docker.  
frontend and backend are running on separate servers.  
I can’t get the certificates I got before. and works without SSL.

certbot is running.  
Can we delete old certificates and obtain new ones?

Can you help me ?

My domain is: [api.dr-mobi.com](http://api.dr-mobi.com) and [dr-mobi.com](http://dr-mobi.com)

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [November 30, 2019, 11:58am UTC](https://community.letsencrypt.org/t/new-certificate-is-not-coming/107534/2 "2019-11-30T11:58:21Z")

</div>

Hi @turkdoktoru

> [@turkdoktoru](#):
>
> Can we delete old certificates and obtain new ones?

please read

> **[Rate Limits - Let's Encrypt](https://letsencrypt.org/docs/rate-limits/)**
>
> Let’s Encrypt provides rate limits to ensure fair usage by as many people as possible. We believe these rate limits are high enough to work for most people by default. We’ve also designed them so renewing a certificate almost never hits a...

You have already certificates created - [https://check-your-website.server-daten.de/?q=dr-mobi.com#ct-logs](https://check-your-website.server-daten.de/?q=dr-mobi.com#ct-logs)

| Issuer | not before | not after | Domain names | LE-Duplicate | next LE |
| --- | --- | --- | --- | --- | --- |
| Let's Encrypt Authority X3 | 2019-11-23 | 2020-02-21 | [api.dr-mobi.com](http://api.dr-mobi.com) - 1 entries | duplicate nr. 1 | |
| Let's Encrypt Authority X3 | 2019-11-23 | 2020-02-21 | [api.dr-mobi.com](http://api.dr-mobi.com) - 1 entries | | |
| Let's Encrypt Authority X3 | 2019-11-23 | 2020-02-21 | [dr-mobi.com](http://dr-mobi.com) - 1 entries | | |
| Let's Encrypt Authority X3 | 2019-11-23 | 2020-02-21 | [dr-mobi.com](http://dr-mobi.com) - 1 entries | | |
| Let's Encrypt Authority X3 | 2019-11-23 | 2020-02-21 | [api.dr-mobi.com](http://api.dr-mobi.com) - 1 entries | | |
| Let's Encrypt Authority X3 | 2019-11-22 | 2020-02-20 | [api.dr-mobi.com](http://api.dr-mobi.com) - 1 entries | | |
| Let's Encrypt Authority X3 | 2019-11-22 | 2020-02-20 | [api.dr-mobi.com](http://api.dr-mobi.com) - 1 entries | | |

So use one of these 60 - 85 days, **then** create the next.

Creating the same certificate again and again is wrong.

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [November 30, 2019, 8:49pm UTC](https://community.letsencrypt.org/t/new-certificate-is-not-coming/107534/3 "2019-11-30T20:49:44Z")

</div>

> [@turkdoktoru](#):
>
> I’m using a docker.

You need to ensure the certificates are stored in a location that will survive a restart.  
[otherwise you will be creating a new cert every time you restart]

---

<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:** [December 30, 2019, 8:49pm UTC](https://community.letsencrypt.org/t/new-certificate-is-not-coming/107534/4 "2019-12-30T20:49:49Z")

</div>

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