Skip to content

[SSL] Expand DCV troubleshooting with all CA error messages#30877

Open
ngayerie wants to merge 1 commit into
cloudflare:productionfrom
ngayerie:ngayerie/SPM-3368
Open

[SSL] Expand DCV troubleshooting with all CA error messages#30877
ngayerie wants to merge 1 commit into
cloudflare:productionfrom
ngayerie:ngayerie/SPM-3368

Conversation

@ngayerie
Copy link
Copy Markdown
Collaborator

Summary

Expands the DCV troubleshooting documentation to include all error messages returned by certificate authorities, with clear resolution steps for each.

Problem

Customers encountering DCV errors often do not know what action to take. The existing documentation only covered a few error types and lacked clear call-to-action guidance.

Solution

Updated /ssl/edge-certificates/changing-dcv-method/troubleshooting/ to document all DCV error messages from the COMS certificate validation system:

Error Resolution
The authority has rate limited these domains... Wait for expiration or try different CA
CAA records block issuance... Remove CAA records or add allowed CAs
Certificate authority encountered a multiple perspective CAA check error... Ensure DNS is resolvable from all locations
MPIC failure... Ensure DNS records are globally reachable
the Certificate Authority had trouble performing a DNS lookup... Check DNS configuration and DNSSEC
The certificate authority will not issue for this domain... Verify domain or try different CA
Internal error with Certificate Authority... Wait and retry, or try different CA

Each error now includes:

  • The exact error message customers will see
  • A clear Resolution section with actionable steps
  • Links to relevant documentation

Ticket

  • SPM-3368

Documents all DCV error messages returned by certificate authorities:
- Rate limiting errors with expiration time
- CAA records block issuance
- Multiple perspective validation errors (MPIC)
- DNS lookup errors (SERVFAIL, NXDOMAIN, DNSSEC)
- Rejected identifier errors
- Internal CA errors

Each error now includes a clear Resolution section with actionable steps.

Addresses SPM-3368
Copy link
Copy Markdown

@nyreegloriani2-prog nyreegloriani2-prog left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SPM-3368 test to finish

Copy link
Copy Markdown

@nyreegloriani2-prog nyreegloriani2-prog left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SPM-3368

For example, for a [Google Trust Services](/ssl/reference/certificate-authorities/#google-trust-services) certificate encountering this issue, you can check for: `<hostname>:CAA:8.8.8.8`.
### CAA records block issuance

Read more from Certificate Authorities specific documentation: [SSL.com](https://www.ssl.com/blogs/multi-perspective-issuance-corroboration-mpic-arrives/), [Let's Encrypt](https://letsencrypt.org/2020/02/19/multi-perspective-validation), and [Google Trust Services](https://pki.goog/faq/#faq-mpic).
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SPM-3368

### CAA records block issuance

Read more from Certificate Authorities specific documentation: [SSL.com](https://www.ssl.com/blogs/multi-perspective-issuance-corroboration-mpic-arrives/), [Let's Encrypt](https://letsencrypt.org/2020/02/19/multi-perspective-validation), and [Google Trust Services](https://pki.goog/faq/#faq-mpic).
The error `CAA records block issuance. Please remove all CAA records or add records for this authority` indicates that your domain's [CAA records](/ssl/edge-certificates/caa-records/) do not allow the selected certificate authority to issue certificates.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Test done complete Finish

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

product:ssl Related to SSL size/s

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants