CAA issue error not clear what is wrong

Help
1

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:stage.hyperproof.app

I ran this command:using cert-manager Docker image for auto-cert renewal

It produced this output:

E0517 18:03:31.698256 1 sync.go:356] cert-manager/controller/challenges/acceptChallenge "msg"="error waiting for authorization" "error"="acme: authorization error for stage.hyperproof.app: 403 urn:ietf:params:acme:error:caa: CAA record for stage.hyperproof.app prevents issuance" "dnsName"="stage.hyperproof.app" "resource_kind"="Challenge" "resource_name"="tls-secret-new-ggxm9-3006079906-481070845" "resource_namespace"="default" "resource_version"="v1" "type"="DNS-01"

My web server is (include version):nginx 1.19.6

The operating system my web server runs on is (include version): Nginx Docker

My hosting provider, if applicable, is:Azure Kubernetes

I can login to a root shell on my machine (yes or no, or I don't know): yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): no

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

2

I had to delete my CAA record to get a cert issued for now.
Record had Flags: 0, tag: issue, value "letsencrypt.org"
All per LetsEncrypt documentation. I expected this to work and it caused cert issuance to fail.

3

Hi @dbrennan

now you have a certificate.

Can you create that CAA entry again? May be there is a problem with your dns.

PS: But a raw check doesn't show problems, doesn't look like a DNSSEC problem because DNSSEC isn't used.

Are you sure there was no typo?

1 Like
4

Hi @JuergenAuer ,
I've recreated the record. It didn't seem like there was a typo.

5

Thanks. There is no problem visible - https://check-your-website.server-daten.de/?q=stage.hyperproof.app#caa

Not with your CAA entries, not with your name servers, DNSSEC isn't used. Same result with a local unbound and unboundtest - https://unboundtest.com/m/CAA/hyperproof.app/7NWNJEC6

And there is no typo (#comments part):

A good: CAA entries found, creating certificate is limited: digicert.com is allowed to create certificates
A good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates

So I don't find a reason why it didn't worked.

1 Like
6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.