I agree, but here are the errors when that is set to -1. If I don’t use that those don’t appear and the record is written and I’m back to the original propogation timeout error.
*.sj312.net {
tls sj111.net@gmail.com {
propagation_timeout -1
dns route53 {
max_retries 10
}
}
111-caddy | {"level":"info","ts":1707761221.745903,"logger":"http.acme_client","msg":"trying to solve challenge","identifier":"*.sj111.net","challenge_type":"dns-01","ca":"https://acme-staging-v02.api.letsencrypt.org/directory"}
111-caddy | {"level":"error","ts":1707761223.2379522,"logger":"http.acme_client","msg":"challenge failed","identifier":"*.sj111.net","challenge_type":"dns-01","problem":{"type":"urn:ietf:params:acme:error:unauthorized","title":"","detail":"No TXT record found at _acme-challenge.sj111.net","instance":"","subproblems":[]}}
111-caddy | {"level":"error","ts":1707761223.2381208,"logger":"http.acme_client","msg":"validating authorization","identifier":"*.sj111.net","problem":{"type":"urn:ietf:params:acme:error:unauthorized","title":"","detail":"No TXT record found at _acme-challenge.sj111.net","instance":"","subproblems":[]},"order":"https://acme-staging-v02.api.letsencrypt.org/acme/order/135555693/14461997903","attempt":1,"max_attempts":3}
at this point I won’t believe this is anything but some issue with the host OS/docker setup. That host OS/docker is a couple years old I need to get that updated before wasting any more time on this.