[SSL] document backup certificate race condition known issue - #33218
Conversation
Review✅ No issues found in commit Code ReviewThis code review is in beta and may not always be helpful — use your judgment. No code review issues found. ConventionsNo convention issues found. Style Guide ReviewNo style-guide issues found. CommandsOnly codeowners can run commands. Post a comment with the command to trigger it.
|
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://dee-3829-backup-cert-known-issue.previews.developers.cloudflare.com (commit 526bce3)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
|
Preview URL: https://526bce31.preview.developers.cloudflare.com Files with changes (up to 15) |
baubuchon-cf
left a comment
There was a problem hiding this comment.
LGTM. Verified the race condition and recovery steps against the underlying escalation — matches the confirmed root cause. ACM workaround checks out too.
|
|
||
| To recover your backup certificate: | ||
|
|
||
| 1. Turn Universal SSL off again. |
There was a problem hiding this comment.
Can we move the TLS continuity requirement before the recovery steps? Turning off Universal SSL can cause new TLS connections to fail unless another valid certificate is already active. “Ordering” an Advanced certificate does not guarantee it is active, and Custom certificates are also supported.
Suggested text:
Before turning off Universal SSL, make sure another valid Advanced or Custom certificate is active and covers the required hostnames. Otherwise, new TLS connections will fail.
Please also confirm that “several minutes” is the validated cooldown from DEE-3829.
da3b83c to
f3c4d7d
Compare
Add a troubleshooting section to the backup certificates page documenting a known race condition where a backup certificate can be deleted immediately after issuance.
DEE-3829
When Universal SSL is disabled and re-enabled in quick succession, certificate processing jobs are not guaranteed to run in submission order. This can cause a newly issued backup certificate to be deleted before it becomes active. The fix documents the issue and the workaround (wait between toggling, use Advanced Certificate Manager for uninterrupted coverage).