uacme: failed to finalize order at https://acme-v02.api.letsencrypt.org/acme/finalize/2745389911/442025748431
uacme: the server reported the following error:
{
"type": "urn:ietf:params:acme:error:caa",
"detail": "Error finalizing order :: rechecking caa: During secondary validation: While processing CAA for snac.r-ricci.it: CAA record for r-ricci.it prevents issuance",
"status": 403
}
The "secondary" validation failure means the primary Let's Encrypt center saw a good CAA but one or more of the secondary centers around the world did not.
Do you know why your DNS servers would respond differently depending on where in the world the DNS query comes from? Such as distributed DNS with some kind of sync problem?
I don't see any problem with some common tools we use. Does this problem repeat or was it just a one-time thing?
I use the DNS servers of my registrar, so I don't know why they are out of sync. Maybe I just have to wait more and let the changes propagate. I only enabled CAA today.
I know. I should have used the staging environment. I've been testing different configurations. Once it works, I'll remove the --force flag and set up a cron job.