SSL errors DuckDNS after snapshot restore

Configuration
1

After having a lot of issues for 2 days with 0.113, I restored a full snapshot from May to a Raspberry Pi. My SSL connection setup with DuckDNS is not working. I get SSL errors on the certificate that it is not trusted.

Anyone point me in the right direction what I need to do ? Thanks

This is the log:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
# INFO: Using main config file /data/workdir/config
+ Account already registered!
[17:30:31] INFO: OK
213.219.153.126
NOCHANGE
# INFO: Using main config file /data/workdir/config
Processing boechout.duckdns.org
 + Checking domain name(s) of existing cert... unchanged.
 + Checking expire date of existing cert...
 + Valid till Jun 15 01:56:05 2020 GMT Certificate will expire
(Less than 30 days). Renewing!
 + Signing domains...
 + Generating private key...
 + Generating signing request...
 + Requesting new certificate order from CA...
  + ERROR: An error occurred while sending post-request to https://acme-v02.api.letsencrypt.org/acme/new-order (Status 429)
Details:
HTTP/2 429 
server: nginx
date: Sat, 08 Aug 2020 15:30:42 GMT
content-type: application/problem+json
content-length: 245
boulder-requester: 49878286
cache-control: public, max-age=0, no-cache
link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
replay-nonce: 01016SEAwQORBzEh6wAlWXbGh0sHPXGEwnmMKwCYM2yT-ik

{
  "type": "urn:ietf:params:acme:error:rateLimited",
  "detail": "Error creating new order :: too many certificates already issued for exact set of domains: boechout.duckdns.org: see https://letsencrypt.org/docs/rate-limits/",
  "status": 429
}```
2

Looks like you hit a rate limit.

From the link:

If you’ve hit a rate limit, we don’t have a way to temporarily reset it. You’ll need to wait until the rate limit expires after a week.

3

I ran into something similar after rolling back to a previous snapshot. The only difference is I only rolled back 1 day but it happened that my let’s encrypt cert updated a day after the snapshot was taken. I ended up going back to the current snapshot which had the latest cert.

4

If you change your domain name that should start a new certificate request.