Letsencrypt container not presenting full chain cert

[drcornish]

Hi there I am not certain if I am doing something wrong, but when I setup the letsencrypt container, it issued the certs and from what I can see in the nginx config it is using the fullchain.pem.

However if I browse to the ddns address (a duckdns one as you can see from the config below), I cannot see the issuer information implying it is not being presented with the full chain?
Config for the container (I obviously have a .env file for the variables and the ):
letsencrypt:
image: linuxserver/letsencrypt
container_name: letsencrypt
cap_add:
- NET_ADMIN
environment:
- PUID=$UserID
- PGID=$GroupID
- TZ=Europe/London
- URL=sub.duckdns.org
- SUBDOMAINS=
- VALIDATION=duckdns
- DUCKDNSTOKEN=mytoken
- EMAIL=example@gmail.com #optional
- DHLEVEL=4096 #optional (default: 2048)
- ONLY_SUBDOMAINS=false #optional
- EXTRA_DOMAINS=
- STAGING=true #optional
volumes:
- $MountDir$MainVolume$AppsDir/letsencrypt:/config
ports:
- 443:443
- 80:80 #optional
restart: unless-stopped
networks:
- media

Note I have 2 extra domains that I had to take out as the forum is blocking my post for too many urls. I can’t input the whole log either for the same reason but I do see that the challenge had 2 challenge errors but still issued the certs?
I am not following the causes of either of these problems.

[gilbn]

Tried setting staging to false?

[drcornish]

I had but I see for some reason now that I inspect the logs it didn’t actually change the variable.
Now that I’ve ensured it does it gives me an error saying that “There were too many requests of a given type :: Error creating new order :: too many certificates already issued for exact set of domains: …”

But if I go to crt.sh these are the only entries:

2036380033	2019-10-25	2019-10-25	2020-01-23	C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3
2034256581	2019-10-25	2019-10-25	2020-01-23	C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3
2036856801	2019-10-25	2019-10-25	2020-01-23	C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3
2036376235	2019-10-25	2019-10-25	2020-01-23	C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3
2034220732	2019-10-25	2019-10-25	2020-01-23	C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3
1981595826	2019-10-08	2019-10-08	2020-01-06	C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3
1976216771	2019-10-08	2019-10-08	2020-01-06	C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3
1981589369	2019-10-08	2019-10-08	2020-01-06	C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3
1975139812	2019-10-08	2019-10-08	2020-01-06	C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3
1981577375	2019-10-08	2019-10-08	2020-01-06	C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3
1974444612	2019-10-08	2019-10-08	2020-01-06	C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3
1981568545	2019-10-08	2019-10-08	2020-01-06	C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3
1974434204	2019-10-08	2019-10-08	2020-01-06	C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3
1981377572	2019-10-08	2019-10-08	2020-01-06	C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3
1974279464	2019-10-08	2019-10-08	2020-01-06	C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3

There are none for today, so I don’t know what rate violation I could have hit.

The last bit from the internal /var/log/letsencrypt/letsencrypt.log
2019-10-26 15:27:25,498:ERROR:certbot.log:An unexpected error occurred:
2019-10-26 15:27:25,499:ERROR:certbot.log:There were too many requests of a given type :: Error creating new order :: too many certificates already issued for exact set of domains: mydomain.duckdns.org: see https://letsencrypt.org/docs/rate-limits/

So I don’t know what the problem is?