# Rate limit problem

**URL:** <https://community.letsencrypt.org/t/rate-limit-problem/96296>\
**Category:** Help\
**Created:** [June 21, 2019, 11:50am UTC](https://community.letsencrypt.org/t/rate-limit-problem/96296 "2019-06-21T11:50:59Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fernien](https://avatars.discourse-cdn.com/v4/letter/f/ea5d25/32.png) [@Fernien](https://community.letsencrypt.org/u/Fernien)\
**Post date:** [June 21, 2019, 11:50am UTC](https://community.letsencrypt.org/t/rate-limit-problem/96296/1 "2019-06-21T11:50:59Z")

</div>

Hello,

my problem is that certbot doesn’t renew one of my certificates anymore. “[günauer.de](http://xn--gnauer-3ya.de) ([günauer.de](http://xn--gnauer-3ya.de))” is my domain and i got 3 subdomains. The domain and the subdomains all got their own certificate (-\> no wildcard). I can’t figure out why im getting above the rate-limit and what i can do about it. I hope someone can help me. Would much appreciate it.  
Thank you very much

My domain is: [günauer.de](http://xn--gnauer-3ya.de) ([günauer.de](http://xn--gnauer-3ya.de))

I ran this command: certbot renew

It produced this output: “Attempting to renew cert ([günauer.de](http://xn--gnauer-3ya.de)) from /etc/letsencrypt/renewal/xn–gnauer-3ya.de.conf produced an unexpected error: urn:ietf:params:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new order :: too many certificates already issued for exact set of domains: [günauer.de](http://xn--gnauer-3ya.de): see [https://letsencrypt.org/docs/rate-limits/](https://letsencrypt.org/docs/rate-limits/). Skipping.”

My web server is (include version): Apache2 2.4.25-3+deb9u7

The operating system my web server runs on is (include version): Raspbian GNU/Linux 9 \n \l

My hosting provider, if applicable, is: Hosting it myself at home on a RaspberryPi with no static IP address but a script which pushes the new IP address into the nameserver.

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.28.0

---

<div class="post-metadata">

**Author:** ![orangepizza](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/orangepizza/32/19597_2.png) [@orangepizza](https://community.letsencrypt.org/u/orangepizza)\
**Post date:** [June 21, 2019, 12:54pm UTC](https://community.letsencrypt.org/t/rate-limit-problem/96296/2 "2019-06-21T12:54:00Z")

</div>

[https://letsdebug.net/xn--gnauer-3ya.de/45159](https://letsdebug.net/xn--gnauer-3ya.de/45159)

[RateLimit](https://letsdebug.net/xn--gnauer-3ya.de/45159#RateLimit-Error)

Error

[günauer.de](http://xn--gnauer-3ya.de) is currently affected by Let’s Encrypt-based rate limits ([https://letsencrypt.org/docs/rate-limits/](https://letsencrypt.org/docs/rate-limits/)). You may review certificates that have already been issued by visiting [https://crt.sh/?q=%xn--gnauer-3ya.de](https://crt.sh/?q=%25xn--gnauer-3ya.de) . Please note that it is not possible to ask for a rate limit to be manually cleared.

The Duplicate Certificate limit (5 certificates with the exact same set of domains per week) has been exceeded and is affecting the domain “[günauer.de](http://xn--gnauer-3ya.de)”. The exact set of domains affected is: “[günauer.de](http://xn--gnauer-3ya.de)”. It may be possible to avoid this rate limit by issuing a certificate with an additional or different domain name.  
where are all those certificates gone and why you don’t use those?

---

<div class="post-metadata">

**Author:** ![Fernien](https://avatars.discourse-cdn.com/v4/letter/f/ea5d25/32.png) [@Fernien](https://community.letsencrypt.org/u/Fernien)\
**Post date:** [June 21, 2019, 1:17pm UTC](https://community.letsencrypt.org/t/rate-limit-problem/96296/3 "2019-06-21T13:17:29Z")

</div>

@orangepizza A few weeks/months ago I had a couple more certificates but for subdomains only. I messed around at the beginning because I had not much experience with all this. I removed and revoked all of them except the 4 (3 subdomains + 1 main domain cert). Since these are not even 5 I don’t know where the others come from which exceed my rate limit. I don’t know how not to exceed the limit because i dont know where i exceed it (if that makes sense).

---

<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:** [June 21, 2019, 1:31pm UTC](https://community.letsencrypt.org/t/rate-limit-problem/96296/4 "2019-06-21T13:31:31Z")

</div>

Hi @Fernien

> [@Fernien](#):
>
> I removed and revoked all of them except the 4 (3 subdomains + 1 main domain cert).

revoking certificates doesn't reset the rate limit.

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...

> **Revoking certificates does not reset rate limits** , because the resources used to issue those certificates have already been consumed.

---

<div class="post-metadata">

**Author:** ![Fernien](https://avatars.discourse-cdn.com/v4/letter/f/ea5d25/32.png) [@Fernien](https://community.letsencrypt.org/u/Fernien)\
**Post date:** [June 21, 2019, 1:45pm UTC](https://community.letsencrypt.org/t/rate-limit-problem/96296/5 "2019-06-21T13:45:08Z")

</div>

Hi @JuergenAuer,

i know that revoking them won’t reset the rate limit. I read that. But it should prevent it from using my rate limit in the future or am I wrong?

---

<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:** [June 21, 2019, 1:49pm UTC](https://community.letsencrypt.org/t/rate-limit-problem/96296/6 "2019-06-21T13:49:04Z")

</div>

> [@Fernien](#):
>
> But it should prevent it from using my rate limit in the future or am I wrong?

That's wrong, the certificate is already created

---

<div class="post-metadata">

**Author:** ![Fernien](https://avatars.discourse-cdn.com/v4/letter/f/ea5d25/32.png) [@Fernien](https://community.letsencrypt.org/u/Fernien)\
**Post date:** [June 21, 2019, 2:08pm UTC](https://community.letsencrypt.org/t/rate-limit-problem/96296/7 "2019-06-21T14:08:20Z")

</div>

@JuergenAuer  
I meant with “future” after the certificate expired. I did not express myself correctly. After the certificate expired it shouldn’t contribute to the rate-limit anymore, should it?

---

<div class="post-metadata">

**Author:** ![orangepizza](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/orangepizza/32/19597_2.png) [@orangepizza](https://community.letsencrypt.org/u/orangepizza)\
**Post date:** [June 21, 2019, 2:09pm UTC](https://community.letsencrypt.org/t/rate-limit-problem/96296/8 "2019-06-21T14:09:50Z")

</div>

certificate older then 7 days after Creation isn’t counted

---

<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:** [June 21, 2019, 2:10pm UTC](https://community.letsencrypt.org/t/rate-limit-problem/96296/9 "2019-06-21T14:10:28Z")

</div>

> [@Fernien](#):
>
> After the certificate expired it shouldn’t contribute to the rate-limit anymore, should it?

The rate limit ist "5 identical certificates in 7 days". If you wait 7 days, you can create the next certificate.

---

<div class="post-metadata">

**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\
**Post date:** [June 21, 2019, 7:58pm UTC](https://community.letsencrypt.org/t/rate-limit-problem/96296/10 "2019-06-21T19:58:16Z")

</div>

The only thing contributing to the rate limit is that something keeps making new certificates. As shown in orangepizza’s post:

[https://crt.sh/?q=%xn--gnauer-3ya.de](https://crt.sh/?q=%25xn--gnauer-3ya.de)

(Note that, due to how Certificate Transparency is implemented, almost all of them are listed twice. Only half of them are real certificates that count.)

As a guess, can you post the output of:

```auto
sudo certbot certificates

sudo ls -alR /etc/letsencrypt/{archive,csr,live,renewal}

```

(If your Certbot executable or configuration directory are located elsewhere, substitute the correct paths.)

---

<div class="post-metadata">

**Author:** ![Fernien](https://avatars.discourse-cdn.com/v4/letter/f/ea5d25/32.png) [@Fernien](https://community.letsencrypt.org/u/Fernien)\
**Post date:** [June 21, 2019, 8:55pm UTC](https://community.letsencrypt.org/t/rate-limit-problem/96296/11 "2019-06-21T20:55:38Z")

</div>

certbot certificates output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log  
Revocation status for /etc/letsencrypt/live/xn–gnauer-3ya.de/cert.pem is unknown

* * *

Found the following certs:  
Certificate Name: [günauer.de](http://xn--gnauer-3ya.de)  
Domains: [günauer.de](http://xn--gnauer-3ya.de)  
Expiry Date: 2019-06-07 13:37:07+00:00 (INVALID: EXPIRED)  
Certificate Path: /etc/letsencrypt/live/xn–gnauer-3ya.de/fullchain.pem  
Private Key Path: /etc/letsencrypt/live/xn–gnauer-3ya.de/privkey.pem  
Certificate Name: [cloud.günauer.de](http://cloud.xn--gnauer-3ya.de)  
Domains: [cloud.günauer.de](http://cloud.xn--gnauer-3ya.de) [wiki.günauer.de](http://wiki.xn--gnauer-3ya.de)  
Expiry Date: 2019-09-14 03:58:05+00:00 (VALID: 84 days)  
Certificate Path: /etc/letsencrypt/live/cloud.xn–gnauer-3ya.de/fullchain.pem  
Private Key Path: /etc/letsencrypt/live/cloud.xn–gnauer-3ya.de/privkey.pem  
Certificate Name: [wiki.günauer.de](http://wiki.xn--gnauer-3ya.de)  
Domains: [wiki.günauer.de](http://wiki.xn--gnauer-3ya.de)  
Expiry Date: 2019-08-09 17:12:31+00:00 (VALID: 48 days)  
Certificate Path: /etc/letsencrypt/live/wiki.xn–gnauer-3ya.de/fullchain.pem  
Private Key Path: /etc/letsencrypt/live/wiki.xn–gnauer-3ya.de/privkey.pem  
Certificate Name: [home.günauer.de](http://home.xn--gnauer-3ya.de)  
Domains: [home.günauer.de](http://home.xn--gnauer-3ya.de)  
Expiry Date: 2019-09-10 19:01:30+00:00 (VALID: 80 days)  
Certificate Path: /etc/letsencrypt/live/home.xn–gnauer-3ya.de/fullchain.pem  
Private Key Path: /etc/letsencrypt/live/home.xn–gnauer-3ya.de/privkey.pem

* * *

output ls -alR /etc/letsencrypt/{archive,csr,live,renewal}:

/etc/letsencrypt/archive:  
insgesamt 40  
drwx------ 10 root root 4096 Jun 12 12:04 .  
drwxr-xr-x 9 root root 4096 Jun 21 22:53 …  
drwxr-xr-x 2 root root 4096 Jun 16 06:58 [cloud.günauer.de](http://cloud.xn--gnauer-3ya.de)  
drwxr-xr-x 2 root root 4096 Dez 8 2018 [dieter.günauer.de](http://dieter.xn--gnauer-3ya.de)  
drwxr-xr-x 2 root root 4096 Jun 12 22:01 [home.günauer.de](http://home.xn--gnauer-3ya.de)  
drwxr-xr-x 2 root root 4096 Mai 11 20:12 [wiki.günauer.de](http://wiki.xn--gnauer-3ya.de)  
drwxr-xr-x 2 root root 4096 Dez 8 2018 [www.dieter.günauer.de](http://www.dieter.xn--gnauer-3ya.de)  
drwxr-xr-x 2 root root 4096 Feb 13 20:30 [günauer.de](http://xn--gnauer-3ya.de)  
drwxr-xr-x 2 root root 4096 Mär 9 15:29 xn–gnauer-3ya.de-0001  
drwxr-xr-x 2 root root 4096 Mär 9 15:37 xn–gnauer-3ya.de-0002

/etc/letsencrypt/archive/cloud.xn–gnauer-3ya.de:  
insgesamt 120  
drwxr-xr-x 2 root root 4096 Jun 16 06:58 .  
drwx------ 10 root root 4096 Jun 12 12:04 …  
-rw-r–r-- 1 root root 2208 Okt 17 2018 cert1.pem  
-rw-r–r-- 1 root root 2208 Okt 17 2018 cert2.pem  
-rw-r–r-- 1 root root 2208 Okt 17 2018 cert3.pem  
-rw-r–r-- 1 root root 1964 Dez 17 2018 cert4.pem  
-rw-r–r-- 1 root root 1964 Feb 15 18:47 cert5.pem  
-rw-r–r-- 1 root root 1968 Apr 17 04:13 cert6.pem  
-rw-r–r-- 1 root root 1968 Jun 16 06:58 cert7.pem  
-rw-r–r-- 1 root root 1647 Okt 17 2018 chain1.pem  
-rw-r–r-- 1 root root 1647 Okt 17 2018 chain2.pem  
-rw-r–r-- 1 root root 1647 Okt 17 2018 chain3.pem  
-rw-r–r-- 1 root root 1647 Dez 17 2018 chain4.pem  
-rw-r–r-- 1 root root 1647 Feb 15 18:47 chain5.pem  
-rw-r–r-- 1 root root 1647 Apr 17 04:13 chain6.pem  
-rw-r–r-- 1 root root 1647 Jun 16 06:58 chain7.pem  
-rw-r–r-- 1 root root 3855 Okt 17 2018 fullchain1.pem  
-rw-r–r-- 1 root root 3855 Okt 17 2018 fullchain2.pem  
-rw-r–r-- 1 root root 3855 Okt 17 2018 fullchain3.pem  
-rw-r–r-- 1 root root 3611 Dez 17 2018 fullchain4.pem  
-rw-r–r-- 1 root root 3611 Feb 15 18:47 fullchain5.pem  
-rw-r–r-- 1 root root 3615 Apr 17 04:13 fullchain6.pem  
-rw-r–r-- 1 root root 3615 Jun 16 06:58 fullchain7.pem  
-rw-r–r-- 1 root root 1704 Okt 17 2018 privkey1.pem  
-rw-r–r-- 1 root root 1704 Okt 17 2018 privkey2.pem  
-rw-r–r-- 1 root root 1704 Okt 17 2018 privkey3.pem  
-rw-r–r-- 1 root root 1704 Dez 17 2018 privkey4.pem  
-rw-r–r-- 1 root root 1704 Feb 15 18:47 privkey5.pem  
-rw-r–r-- 1 root root 1704 Apr 17 04:13 privkey6.pem  
-rw-r–r-- 1 root root 1704 Jun 16 06:58 privkey7.pem

/etc/letsencrypt/archive/dieter.xn–gnauer-3ya.de:  
insgesamt 24  
drwxr-xr-x 2 root root 4096 Dez 8 2018 .  
drwx------ 10 root root 4096 Jun 12 12:04 …  
-rw-r–r-- 1 root root 1935 Dez 8 2018 cert1.pem  
-rw-r–r-- 1 root root 1647 Dez 8 2018 chain1.pem  
-rw-r–r-- 1 root root 3582 Dez 8 2018 fullchain1.pem  
-rw-r–r-- 1 root root 1704 Dez 8 2018 privkey1.pem

/etc/letsencrypt/archive/home.xn–gnauer-3ya.de:  
insgesamt 40  
drwxr-xr-x 2 root root 4096 Jun 12 22:01 .  
drwx------ 10 root root 4096 Jun 12 12:04 …  
-rw-r–r-- 1 root root 1931 Apr 13 22:33 cert1.pem  
-rw-r–r-- 1 root root 1931 Jun 12 22:01 cert2.pem  
-rw-r–r-- 1 root root 1647 Apr 13 22:33 chain1.pem  
-rw-r–r-- 1 root root 1647 Jun 12 22:01 chain2.pem  
-rw-r–r-- 1 root root 3578 Apr 13 22:33 fullchain1.pem  
-rw-r–r-- 1 root root 3578 Jun 12 22:01 fullchain2.pem  
-rw-r–r-- 1 root root 1704 Apr 13 22:33 privkey1.pem  
-rw-r–r-- 1 root root 1704 Jun 12 22:01 privkey2.pem

/etc/letsencrypt/archive/wiki.xn–gnauer-3ya.de:  
insgesamt 56  
drwxr-xr-x 2 root root 4096 Mai 11 20:12 .  
drwx------ 10 root root 4096 Jun 12 12:04 …  
-rw-r–r-- 1 root root 1931 Jan 11 12:52 cert1.pem  
-rw-r–r-- 1 root root 1931 Mär 12 14:21 cert2.pem  
-rw-r–r-- 1 root root 1927 Mai 11 20:12 cert3.pem  
-rw-r–r-- 1 root root 1647 Jan 11 12:52 chain1.pem  
-rw-r–r-- 1 root root 1647 Mär 12 14:21 chain2.pem  
-rw-r–r-- 1 root root 1647 Mai 11 20:12 chain3.pem  
-rw-r–r-- 1 root root 3578 Jan 11 12:52 fullchain1.pem  
-rw-r–r-- 1 root root 3578 Mär 12 14:21 fullchain2.pem  
-rw-r–r-- 1 root root 3574 Mai 11 20:12 fullchain3.pem  
-rw-r–r-- 1 root root 1704 Jan 11 12:52 privkey1.pem  
-rw-r–r-- 1 root root 1708 Mär 12 14:21 privkey2.pem  
-rw-r–r-- 1 root root 1704 Mai 11 20:12 privkey3.pem

/etc/letsencrypt/archive/www.dieter.xn–gnauer-3ya.de:  
insgesamt 24  
drwxr-xr-x 2 root root 4096 Dez 8 2018 .  
drwx------ 10 root root 4096 Jun 12 12:04 …  
-rw-r–r-- 1 root root 1948 Dez 8 2018 cert1.pem  
-rw-r–r-- 1 root root 1647 Dez 8 2018 chain1.pem  
-rw-r–r-- 1 root root 3595 Dez 8 2018 fullchain1.pem  
-rw-r–r-- 1 root root 1704 Dez 8 2018 privkey1.pem

/etc/letsencrypt/archive/xn–gnauer-3ya.de:  
insgesamt 56  
drwxr-xr-x 2 root root 4096 Feb 13 20:30 .  
drwx------ 10 root root 4096 Jun 12 12:04 …  
-rw-r–r-- 1 root root 2256 Okt 16 2018 cert1.pem  
-rw-r–r-- 1 root root 2013 Dez 15 2018 cert2.pem  
-rw-r–r-- 1 root root 1915 Jun 21 09:31 cert3.pem  
-rw-r–r-- 1 root root 1647 Okt 16 2018 chain1.pem  
-rw-r–r-- 1 root root 1647 Dez 15 2018 chain2.pem  
-rw-r–r-- 1 root root 1647 Jun 21 09:31 chain3.pem  
-rw-r–r-- 1 root root 3903 Okt 16 2018 fullchain1.pem  
-rw-r–r-- 1 root root 3660 Dez 15 2018 fullchain2.pem  
-rw-r–r-- 1 root root 3562 Jun 21 09:31 fullchain3.pem  
-rw-r–r-- 1 root root 1708 Okt 16 2018 privkey1.pem  
-rw-r–r-- 1 root root 1704 Dez 15 2018 privkey2.pem  
-rw-r–r-- 1 root root 1704 Jun 21 09:31 privkey3.pem

/etc/letsencrypt/archive/xn–gnauer-3ya.de-0001:  
insgesamt 24  
drwxr-xr-x 2 root root 4096 Mär 9 15:29 .  
drwx------ 10 root root 4096 Jun 12 12:04 …  
-rw-r–r-- 1 root root 1919 Mär 9 15:29 cert1.pem  
-rw-r–r-- 1 root root 1647 Mär 9 15:29 chain1.pem  
-rw-r–r-- 1 root root 3566 Mär 9 15:29 fullchain1.pem  
-rw-r–r-- 1 root root 1704 Mär 9 15:29 privkey1.pem

/etc/letsencrypt/archive/xn–gnauer-3ya.de-0002:  
insgesamt 40  
drwxr-xr-x 2 root root 4096 Mär 9 15:37 .  
drwx------ 10 root root 4096 Jun 12 12:04 …  
-rw-r–r-- 1 root root 1915 Mär 9 15:36 cert1.pem  
-rw-r–r-- 1 root root 1919 Mär 9 15:37 cert2.pem  
-rw-r–r-- 1 root root 1647 Mär 9 15:36 chain1.pem  
-rw-r–r-- 1 root root 1647 Mär 9 15:37 chain2.pem  
-rw-r–r-- 1 root root 3562 Mär 9 15:36 fullchain1.pem  
-rw-r–r-- 1 root root 3566 Mär 9 15:37 fullchain2.pem  
-rw-r–r-- 1 root root 1704 Mär 9 15:36 privkey1.pem  
-rw-r–r-- 1 root root 1704 Mär 9 15:37 privkey2.pem

/etc/letsencrypt/csr:  
insgesamt 564  
drwxr-xr-x 2 root root 4096 Jun 21 20:21 .  
drwxr-xr-x 9 root root 4096 Jun 21 22:53 …  
-rw-r–r-- 1 root root 1025 Okt 16 2018 0000\_csr-certbot.pem  
-rw-r–r-- 1 root root 1098 Okt 16 2018 0001\_csr-certbot.pem  
-rw-r–r-- 1 root root 1098 Okt 16 2018 0002\_csr-certbot.pem  
-rw-r–r-- 1 root root 1110 Okt 16 2018 0003\_csr-certbot.pem  
-rw-r–r-- 1 root root 1050 Okt 17 2018 0004\_csr-certbot.pem  
-rw-r–r-- 1 root root 1050 Okt 17 2018 0005\_csr-certbot.pem  
-rw-r–r-- 1 root root 1050 Okt 17 2018 0006\_csr-certbot.pem  
-rw-r–r-- 1 root root 968 Okt 17 2018 0007\_csr-certbot.pem  
-rw-r–r-- 1 root root 968 Okt 17 2018 0008\_csr-certbot.pem  
-rw-r–r-- 1 root root 968 Okt 17 2018 0009\_csr-certbot.pem  
-rw-r–r-- 1 root root 1050 Okt 17 2018 0010\_csr-certbot.pem  
-rw-r–r-- 1 root root 940 Okt 17 2018 0011\_csr-certbot.pem  
-rw-r–r-- 1 root root 936 Dez 8 2018 0012\_csr-certbot.pem  
-rw-r–r-- 1 root root 944 Dez 8 2018 0013\_csr-certbot.pem  
-rw-r–r-- 1 root root 1025 Dez 15 2018 0014\_csr-certbot.pem  
-rw-r–r-- 1 root root 968 Dez 17 2018 0015\_csr-certbot.pem  
-rw-r–r-- 1 root root 940 Dez 17 2018 0016\_csr-certbot.pem  
-rw-r–r-- 1 root root 1009 Jan 7 10:39 0017\_csr-certbot.pem  
-rw-r–r-- 1 root root 972 Jan 10 15:31 0018\_csr-certbot.pem  
-rw-r–r-- 1 root root 936 Jan 11 12:52 0019\_csr-certbot.pem  
-rw-r–r-- 1 root root 940 Jan 11 17:59 0020\_csr-certbot.pem  
-rw-r–r-- 1 root root 940 Jan 11 18:10 0021\_csr-certbot.pem  
-rw-r–r-- 1 root root 1025 Feb 13 20:30 0022\_csr-certbot.pem  
-rw-r–r-- 1 root root 968 Feb 15 18:47 0023\_csr-certbot.pem  
-rw-r–r-- 1 root root 940 Feb 15 18:47 0024\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mär 9 15:29 0025\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mär 9 15:35 0026\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mär 9 15:36 0027\_csr-certbot.pem  
-rw-r–r-- 1 root root 936 Mär 12 14:21 0028\_csr-certbot.pem  
-rw-r–r-- 1 root root 972 Apr 13 21:07 0029\_csr-certbot.pem  
-rw-r–r-- 1 root root 972 Apr 13 21:14 0030\_csr-certbot.pem  
-rw-r–r-- 1 root root 936 Apr 13 21:16 0031\_csr-certbot.pem  
-rw-r–r-- 1 root root 936 Apr 13 21:17 0032\_csr-certbot.pem  
-rw-r–r-- 1 root root 936 Apr 13 21:19 0033\_csr-certbot.pem  
-rw-r–r-- 1 root root 936 Apr 13 21:22 0034\_csr-certbot.pem  
-rw-r–r-- 1 root root 936 Apr 13 21:24 0035\_csr-certbot.pem  
-rw-r–r-- 1 root root 936 Apr 13 22:33 0036\_csr-certbot.pem  
-rw-r–r-- 1 root root 968 Apr 17 04:13 0037\_csr-certbot.pem  
-rw-r–r-- 1 root root 940 Apr 17 04:14 0038\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 9 03:30 0039\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 9 20:53 0040\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 10 03:54 0041\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 10 18:02 0042\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 11 07:15 0043\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 11 20:12 0044\_csr-certbot.pem  
-rw-r–r-- 1 root root 936 Mai 11 20:12 0045\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 12 01:55 0046\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 12 14:49 0047\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 13 08:26 0048\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 13 17:58 0049\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 14 05:35 0050\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 14 22:04 0051\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 15 00:38 0052\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 15 23:18 0053\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 16 04:40 0054\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 16 12:12 0055\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 17 05:00 0056\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 17 18:12 0057\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 18 09:23 0058\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 18 22:29 0059\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 19 08:47 0060\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 19 19:29 0061\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 20 06:22 0062\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 20 16:43 0063\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 21 10:11 0064\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 21 22:24 0065\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 22 07:42 0066\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 22 13:57 0067\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 23 04:38 0068\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 23 21:35 0069\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 24 06:01 0070\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 24 17:00 0071\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 25 04:35 0072\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 25 16:31 0073\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 26 01:22 0074\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 26 22:49 0075\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 27 01:03 0076\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 27 22:53 0077\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 28 10:29 0078\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 28 15:48 0079\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 29 05:02 0080\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 29 15:49 0081\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 30 07:09 0082\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 30 12:28 0083\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 31 04:03 0084\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Mai 31 20:19 0085\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 1 02:35 0086\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 1 12:11 0087\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 2 09:39 0088\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 2 17:51 0089\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 3 07:10 0090\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 3 18:40 0091\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 4 11:54 0092\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 4 20:42 0093\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 5 07:49 0094\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 5 19:12 0095\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 6 04:53 0096\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 6 18:36 0097\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 7 08:21 0098\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 7 18:01 0099\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 8 06:32 0100\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 8 08:16 0101\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 8 08:19 0102\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 8 16:14 0103\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 9 11:40 0104\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 9 18:34 0105\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 10 04:46 0106\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 10 15:11 0107\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 11 07:38 0108\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 11 13:08 0109\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 12 06:17 0110\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 12 11:52 0111\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 12 12:06 0112\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 12 22:01 0113\_csr-certbot.pem  
-rw-r–r-- 1 root root 936 Jun 12 22:01 0114\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 13 05:17 0115\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 13 22:38 0116\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 14 03:04 0117\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 14 16:11 0118\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 15 11:35 0119\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 15 15:06 0120\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 16 06:57 0121\_csr-certbot.pem  
-rw-r–r-- 1 root root 968 Jun 16 06:57 0122\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 16 15:28 0123\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 16 22:36 0124\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 16 22:39 0125\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 17 03:36 0126\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 17 20:12 0127\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 18 05:55 0128\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 18 19:43 0129\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 19 04:23 0130\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 19 21:48 0131\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 20 05:12 0132\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 20 15:38 0133\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 21 09:31 0134\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 21 13:22 0135\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 21 13:23 0136\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 21 13:39 0137\_csr-certbot.pem  
-rw-r–r-- 1 root root 928 Jun 21 20:21 0138\_csr-certbot.pem

/etc/letsencrypt/live:  
insgesamt 28  
drwx------ 6 root root 4096 Jun 12 12:04 .  
drwxr-xr-x 9 root root 4096 Jun 21 22:53 …  
drwxr-xr-x 2 root root 4096 Jun 16 06:58 [cloud.günauer.de](http://cloud.xn--gnauer-3ya.de)  
drwxr-xr-x 2 root root 4096 Jun 12 22:01 [home.günauer.de](http://home.xn--gnauer-3ya.de)  
-rw-r–r-- 1 root root 740 Dez 8 2018 README  
drwxr-xr-x 2 root root 4096 Mai 11 20:12 [wiki.günauer.de](http://wiki.xn--gnauer-3ya.de)  
drwxr-xr-x 2 root root 4096 Jun 21 09:31 [günauer.de](http://xn--gnauer-3ya.de)

/etc/letsencrypt/live/cloud.xn–gnauer-3ya.de:  
insgesamt 12  
drwxr-xr-x 2 root root 4096 Jun 16 06:58 .  
drwx------ 6 root root 4096 Jun 12 12:04 …  
lrwxrwxrwx 1 root root 47 Jun 16 06:58 cert.pem -\> …/…/archive/cloud.xn–gnauer-3ya.de/cert7.pem  
lrwxrwxrwx 1 root root 48 Jun 16 06:58 chain.pem -\> …/…/archive/cloud.xn–gnauer-3ya.de/chain7.pem  
lrwxrwxrwx 1 root root 52 Jun 16 06:58 fullchain.pem -\> …/…/archive/cloud.xn–gnauer-3ya.de/fullchain7.pem  
lrwxrwxrwx 1 root root 50 Jun 16 06:58 privkey.pem -\> …/…/archive/cloud.xn–gnauer-3ya.de/privkey7.pem  
-rw-r–r-- 1 root root 682 Okt 17 2018 README

/etc/letsencrypt/live/home.xn–gnauer-3ya.de:  
insgesamt 12  
drwxr-xr-x 2 root root 4096 Jun 12 22:01 .  
drwx------ 6 root root 4096 Jun 12 12:04 …  
lrwxrwxrwx 1 root root 46 Jun 12 22:01 cert.pem -\> …/…/archive/home.xn–gnauer-3ya.de/cert2.pem  
lrwxrwxrwx 1 root root 47 Jun 12 22:01 chain.pem -\> …/…/archive/home.xn–gnauer-3ya.de/chain2.pem  
lrwxrwxrwx 1 root root 51 Jun 12 22:01 fullchain.pem -\> …/…/archive/home.xn–gnauer-3ya.de/fullchain2.pem  
lrwxrwxrwx 1 root root 49 Jun 12 22:01 privkey.pem -\> …/…/archive/home.xn–gnauer-3ya.de/privkey2.pem  
-rw-r–r-- 1 root root 692 Apr 13 22:33 README

/etc/letsencrypt/live/wiki.xn–gnauer-3ya.de:  
insgesamt 12  
drwxr-xr-x 2 root root 4096 Mai 11 20:12 .  
drwx------ 6 root root 4096 Jun 12 12:04 …  
lrwxrwxrwx 1 root root 46 Mai 11 20:12 cert.pem -\> …/…/archive/wiki.xn–gnauer-3ya.de/cert3.pem  
lrwxrwxrwx 1 root root 47 Mai 11 20:12 chain.pem -\> …/…/archive/wiki.xn–gnauer-3ya.de/chain3.pem  
lrwxrwxrwx 1 root root 51 Mai 11 20:12 fullchain.pem -\> …/…/archive/wiki.xn–gnauer-3ya.de/fullchain3.pem  
lrwxrwxrwx 1 root root 49 Mai 11 20:12 privkey.pem -\> …/…/archive/wiki.xn–gnauer-3ya.de/privkey3.pem  
-rw-r–r-- 1 root root 692 Jan 11 12:52 README

/etc/letsencrypt/live/xn–gnauer-3ya.de:  
insgesamt 12  
drwxr-xr-x 2 root root 4096 Jun 21 09:31 .  
drwx------ 6 root root 4096 Jun 12 12:04 …  
lrwxrwxrwx 1 root root 46 Jun 21 09:31 cert.pem -\> …/…/archive/xn–gnauer-3ya.de-0002/cert2.pem  
lrwxrwxrwx 1 root root 47 Jun 21 09:31 chain.pem -\> …/…/archive/xn–gnauer-3ya.de-0002/chain2.pem  
lrwxrwxrwx 1 root root 51 Jun 21 09:31 fullchain.pem -\> …/…/archive/xn–gnauer-3ya.de-0002/fullchain2.pem  
lrwxrwxrwx 1 root root 49 Jun 21 09:31 privkey.pem -\> …/…/archive/xn–gnauer-3ya.de-0002/privkey2.pem  
-rw-r–r-- 1 root root 692 Mär 9 15:36 README

/etc/letsencrypt/renewal:  
insgesamt 24  
drwxr-xr-x 2 root root 4096 Jun 21 09:31 .  
drwxr-xr-x 9 root root 4096 Jun 21 22:53 …  
-rw-r–r-- 1 root root 690 Jun 16 06:58 cloud.xn–gnauer-3ya.de.conf  
-rw-r–r-- 1 root root 569 Jun 12 22:01 home.xn–gnauer-3ya.de.conf  
-rw-r–r-- 1 root root 569 Mai 11 20:12 wiki.xn–gnauer-3ya.de.conf  
-rw-r–r-- 1 root root 752 Jun 21 09:31 xn–gnauer-3ya.de.conf

---

<div class="post-metadata">

**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\
**Post date:** [June 21, 2019, 9:10pm UTC](https://community.letsencrypt.org/t/rate-limit-problem/96296/12 "2019-06-21T21:10:15Z")

</div>

> [@Fernien](#):
>
> /etc/letsencrypt/archive/xn–[gnauer-3ya.de](http://gnauer-3ya.de):  
> insgesamt 56  
> drwxr-xr-x 2 root root 4096 Feb 13 20:30 .  
> drwx------ 10 root root 4096 Jun 12 12:04 …  
> -rw-r–r-- 1 root root 2256 Okt 16 2018 cert1.pem  
> -rw-r–r-- 1 root root 2013 Dez 15 2018 cert2.pem  
> -rw-r–r-- 1 root root 1915 Jun 21 09:31 cert3.pem  
> -rw-r–r-- 1 root root 1647 Okt 16 2018 chain1.pem  
> -rw-r–r-- 1 root root 1647 Dez 15 2018 chain2.pem  
> -rw-r–r-- 1 root root 1647 Jun 21 09:31 chain3.pem  
> -rw-r–r-- 1 root root 3903 Okt 16 2018 fullchain1.pem  
> -rw-r–r-- 1 root root 3660 Dez 15 2018 fullchain2.pem  
> -rw-r–r-- 1 root root 3562 Jun 21 09:31 fullchain3.pem  
> -rw-r–r-- 1 root root 1708 Okt 16 2018 privkey1.pem  
> -rw-r–r-- 1 root root 1704 Dez 15 2018 privkey2.pem  
> -rw-r–r-- 1 root root 1704 Jun 21 09:31 privkey3.pem
> 
> /etc/letsencrypt/archive/xn–gnauer-3ya.de-0001:  
> insgesamt 24  
> drwxr-xr-x 2 root root 4096 Mär 9 15:29 .  
> drwx------ 10 root root 4096 Jun 12 12:04 …  
> -rw-r–r-- 1 root root 1919 Mär 9 15:29 cert1.pem  
> -rw-r–r-- 1 root root 1647 Mär 9 15:29 chain1.pem  
> -rw-r–r-- 1 root root 3566 Mär 9 15:29 fullchain1.pem  
> -rw-r–r-- 1 root root 1704 Mär 9 15:29 privkey1.pem
> 
> /etc/letsencrypt/archive/xn–gnauer-3ya.de-0002:  
> insgesamt 40  
> drwxr-xr-x 2 root root 4096 Mär 9 15:37 .  
> drwx------ 10 root root 4096 Jun 12 12:04 …  
> -rw-r–r-- 1 root root 1915 Mär 9 15:36 cert1.pem  
> -rw-r–r-- 1 root root 1919 Mär 9 15:37 cert2.pem  
> -rw-r–r-- 1 root root 1647 Mär 9 15:36 chain1.pem  
> -rw-r–r-- 1 root root 1647 Mär 9 15:37 chain2.pem  
> -rw-r–r-- 1 root root 3562 Mär 9 15:36 fullchain1.pem  
> -rw-r–r-- 1 root root 3566 Mär 9 15:37 fullchain2.pem  
> -rw-r–r-- 1 root root 1704 Mär 9 15:36 privkey1.pem  
> -rw-r–r-- 1 root root 1704 Mär 9 15:37 privkey2.pem

> [@Fernien](#):
>
> /etc/letsencrypt/live/xn–[gnauer-3ya.de](http://gnauer-3ya.de):  
> insgesamt 12  
> drwxr-xr-x 2 root root 4096 Jun 21 09:31 .  
> drwx------ 6 root root 4096 Jun 12 12:04 …  
> lrwxrwxrwx 1 root root 46 Jun 21 09:31 cert.pem -\> …/…/archive/xn–gnauer-3ya.de-0002/cert2.pem  
> lrwxrwxrwx 1 root root 47 Jun 21 09:31 chain.pem -\> …/…/archive/xn–gnauer-3ya.de-0002/chain2.pem  
> lrwxrwxrwx 1 root root 51 Jun 21 09:31 fullchain.pem -\> …/…/archive/xn–gnauer-3ya.de-0002/fullchain2.pem  
> lrwxrwxrwx 1 root root 49 Jun 21 09:31 privkey.pem -\> …/…/archive/xn–gnauer-3ya.de-0002/privkey2.pem  
> -rw-r–r-- 1 root root 692 Mär 9 15:36 README

The symlinks in `/etc/letsencrypt/live/xn–gnauer-3ya.de/` are not pointing to `../../archive/xn–gnauer-3ya.de/` so Certbot is constantly issuing certificates and saving them to the the correct directory, but then it can't find them again.

You need to fix `/etc/letsencrypt/live/cert.pem` to point to `../../archive/xn–gnauer-3ya.de/cert3.pem` and so on for the other three links.

After that you can probably also delete `/etc/letsencrypt/archive/xn–gnauer-3ya.de-0001` and `/etc/letsencrypt/archive/xn–gnauer-3ya.de-0002/` if you want to.

---

<div class="post-metadata">

**Author:** ![Fernien](https://avatars.discourse-cdn.com/v4/letter/f/ea5d25/32.png) [@Fernien](https://community.letsencrypt.org/u/Fernien)\
**Post date:** [June 22, 2019, 10:41pm UTC](https://community.letsencrypt.org/t/rate-limit-problem/96296/13 "2019-06-22T22:41:35Z")

</div>

Thank you very much it works now. I struggled with it for some time!

---

<div class="post-metadata">

**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\
**Post date:** [June 22, 2019, 11:19pm UTC](https://community.letsencrypt.org/t/rate-limit-problem/96296/14 "2019-06-22T23:19:12Z")

</div>

> [@mnordhoff](#):
>
> You need to fix `/etc/letsencrypt/live/cert.pem` to point to `../../archive/xn–gnauer-3ya.de/cert3.pem` and so on for the other three links.

I meant `/etc/letsencrypt/live/xn–gnauer-3ya.de/cert.pem`, not `/etc/letsencrypt/live/cert.pem`.

I **almost** made a whole post without any critical errors. ☹

---

<div class="post-metadata">

**Author:** ![Fernien](https://avatars.discourse-cdn.com/v4/letter/f/ea5d25/32.png) [@Fernien](https://community.letsencrypt.org/u/Fernien)\
**Post date:** [June 23, 2019, 8:35am UTC](https://community.letsencrypt.org/t/rate-limit-problem/96296/15 "2019-06-23T08:35:06Z")

</div>

@mnordhoff  
still figured it out because of your help 🙂

---

<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:** [July 23, 2019, 8:35am UTC](https://community.letsencrypt.org/t/rate-limit-problem/96296/16 "2019-07-23T08:35:06Z")

</div>

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