Today, I was notified that my certificate will expire soon. I was surprised because caddy is supposed to update it automatically. So I've looked in the logs and I see this entry:
{"error": "[*.example.com] Renew: [*.example.com] solving challenges: presenting for challenge: adding temporary record for zone \"example.com.\": (2306) Parameter value policy error. Reason: (maxDNSRecordsReached) maxDNSRecordsReached (order=https://acme.zerossl.com/v2/DV90/order/xxx-yyy) (ca=https://acme.zerossl.com/v2/DV90)", "attempt": 1, "retrying_in": 60, "elapsed": 4.508000445, "max_duration": 2592000}Logging into INWX, I can see hundreds of _acme-challenge entries (which I have to manually delete).
When looking at the current certificate, it was issued on October 2025, so it should have been successful at least once but I'm unsure. I guess it will renew every 3 months, so it missed it in December. Unfortunately, I don't think I've retained the logs from that long ago.
After manually deleting a bunch of the entries, it succeeded creating the certificate which is now valid for the next 3 months.
Today, I was notified that my certificate will expire soon. I was surprised because caddy is supposed to update it automatically. So I've looked in the logs and I see this entry:
{"error": "[*.example.com] Renew: [*.example.com] solving challenges: presenting for challenge: adding temporary record for zone \"example.com.\": (2306) Parameter value policy error. Reason: (maxDNSRecordsReached) maxDNSRecordsReached (order=https://acme.zerossl.com/v2/DV90/order/xxx-yyy) (ca=https://acme.zerossl.com/v2/DV90)", "attempt": 1, "retrying_in": 60, "elapsed": 4.508000445, "max_duration": 2592000}Logging into INWX, I can see hundreds of
_acme-challengeentries (which I have to manually delete).When looking at the current certificate, it was issued on October 2025, so it should have been successful at least once but I'm unsure. I guess it will renew every 3 months, so it missed it in December. Unfortunately, I don't think I've retained the logs from that long ago.
After manually deleting a bunch of the entries, it succeeded creating the certificate which is now valid for the next 3 months.