Hi, I trying to use caddy and route53 to automatically renew the certificate through caddy
However, whenever I set and run route53 tls, the following error appears even if I’m using route53 v1.3.0
I’ve been suffering from this problem for more than two days
Can you give me some advice on how to solve this problem?
(route) {
tls {
dns route53 {
region ...
access_key_id ...
secret_access_key ...
}
}
}
my.routing.com {
reverse_proxy staging.routing.com
import route
}
Following is log
2022/11/23 08:11:39.862 e[34mINFOe[0m tls.issuance.acme waiting on internal rate limiter {"identifiers": ["my.routing.com"], "ca": "https://acme-v02.api.letsencrypt.org/directory", "account": ""}
2022/11/23 08:11:39.862 e[34mINFOe[0m tls.issuance.acme done waiting on internal rate limiter {"identifiers": ["my.routing.com"], "ca": "https://acme-v02.api.letsencrypt.org/directory", "account": ""}
2022/11/23 08:11:40.978 e[34mINFOe[0m tls.issuance.acme.acme_client trying to solve challenge {"identifier": "my.routing.com", "challenge_type": "dns-01", "ca": "https://acme-v02.api.letsencrypt.org/directory"}
2022/11/23 08:11:43.056 e[31mERRORe[0m tls.issuance.acme.acme_client cleaning up solver {"identifier": "my.routing.com", "challenge_type": "dns-01", "error": "no memory of presenting a DNS record for my.routing.com (probably OK if presenting failed)"}
2022/11/23 08:11:43.262 e[31mERRORe[0m tls.obtain could not get certificate from issuer {"identifier": "my.routing.com", "issuer": "acme-v02.api.letsencrypt.org-directory", "error": "[my.routing.com] solving challenges: presenting for challenge: adding temporary record for zone routing.com.: Error unquoting TXT/SPF record: invalid syntax (order=https://acme-v02.api.letsencrypt.org/acme/order/732212697/146722220587) (ca=https://acme-v02.api.letsencrypt.org/directory)"}
2022/11/23 08:11:43.264 e[33mWARNe[0m tls.issuance.zerossl missing email address for ZeroSSL; it is strongly recommended to set one for next time
2022/11/23 08:11:45.373 e[34mINFOe[0m tls.issuance.zerossl generated EAB credentials {"key_id": "blabla"}