diff --git a/src/content/docs/ssl/edge-certificates/custom-certificates/troubleshooting.mdx b/src/content/docs/ssl/edge-certificates/custom-certificates/troubleshooting.mdx index f3c10ba36162cb8..4d9110dbb7836e2 100644 --- a/src/content/docs/ssl/edge-certificates/custom-certificates/troubleshooting.mdx +++ b/src/content/docs/ssl/edge-certificates/custom-certificates/troubleshooting.mdx @@ -47,6 +47,8 @@ If you are using a Let's Encrypt certificate uploaded by yourself as a custom ce The certificate you are trying to upload is invalid. For example, there might be extra lines, or the BEGIN/END text is not correct, or extra characters are added following a copy/paste. +In the case of an update with the [PATCH API call](/api/resources/custom_certificates/methods/edit/), it can mean the path parameter `{custom_certificate_id}` is invalid. + **Solution** Carefully check the content of the certificate. You may use `openssl` to check all the details of your certificate: @@ -55,6 +57,8 @@ Carefully check the content of the certificate. You may use `openssl` to check a openssl x509 -in certificate.crt -noout -text ``` +When using the API, carefully check the `{custom_certificate_id}` path parameter. You can confirm the certificate ID by [listing the existing custom certificates](/api/resources/custom_certificates/methods/list/) (`id` in the response). + ### You have reached the maximum number of custom certificates. (Code: 1212) **Root cause**