Skip to content

Commit 1c3c048

Browse files
authored
[SSL] Clarify USSL disablement vs impact to TLS connections (#26410)
Clarifying Universal SSL disablement and the (non) impact to ongoing/new TLS connections if another certificate is active
1 parent 4af0dfa commit 1c3c048

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,10 @@ Some customers may need to manage their own SSL certificates or rely on specific
1111

1212
If you disable your domain's Universal SSL certificate, Cloudflare removes that certificate from our network and will not order or renew any additional Universal SSL certificates.
1313

14+
Disabling Universal SSL will not cause any interruption to ongoing TLS connections to your domain on Cloudflare's network, they will continue to be served according the the Universal SSL certificate used when they were first established. Eventually these connections will naturally end.
15+
16+
New TLS connections are expected to succeed as long as you have another valid certificate active, such as a [custom](/ssl/edge-certificates/custom-certificates/)) or [advanced](/ssl/edge-certificates/advanced-certificate-manager/) certificate. New TLS connections will receive the highest priority certificate from our edge as per our [certificate and hostname priority](/ssl/reference/certificate-and-hostname-priority/). If a valid certificate is not active before disabling, TLS connections will fail. For more information, refer to [Potential errors](#potential-errors) below.
17+
1418
## Potential errors
1519

1620
To avoid errors with your domain, either [upload a custom certificate](/ssl/edge-certificates/custom-certificates/) or purchase [Advanced Certificate Manager](/ssl/edge-certificates/advanced-certificate-manager/) before disabling Universal SSL.

0 commit comments

Comments
 (0)