Skip to content

Commit 39a4fc8

Browse files
[SSL] Remove auto switch to HTTP callout (cloudflare#25022)
1 parent 5914460 commit 39a4fc8

File tree

1 file changed

+0
-11
lines changed

1 file changed

+0
-11
lines changed

src/content/docs/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv.mdx

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -100,20 +100,9 @@ _acme-challenge.example.com. 3600 IN CNAME example.com.<COPIED_VALIDATI
100100

101101
### Renewal
102102

103-
Currently, at certificate renewal, Cloudflare attempts to automatically perform DCV via HTTP if your certificate matches certain criteria:
104-
105-
- Hostnames are proxied.
106-
- Hostnames on the certificate resolve to the IPs assigned to the zone.
107-
- The certificate does not contain wildcards.
108-
109-
Note that settings that interfere with the validation URLs can cause issues in this case. Refer to [Troubleshooting](/ssl/edge-certificates/changing-dcv-method/troubleshooting/) for guidance.
110-
111-
:::note
112-
113103
If a hostname becomes unreachable during certificate renewal time, the certificate will not be able to be renewed automatically via Delegated DCV. Should you need to renew a certificate for a hostname that is not resolving currently, you can send a PATCH request to [the changing DCV method API endpoint](/api/resources/ssl/subresources/verification/methods/edit/) and change the method to TXT to proceed with manual renewal per [the TXT DCV method](/ssl/edge-certificates/changing-dcv-method/methods/txt/).
114104

115105
Once the hostname becomes resolvable again, [Delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/) will resume working as expected.
116-
:::
117106

118107
### Moved domains
119108

0 commit comments

Comments
 (0)