Troubleshooting Certificate Manager

This page describes the most common errors you might encounter when using Certificate Manager. It also provides steps to diagnose and resolve those errors.

For help with resolving issues related to TLS (SSL) certificates, see Troubleshooting SSL certificates.

Error when detaching a certificate map from a target proxy

When detaching a certificate map from a target proxy, you receive the following error:

"There must be at least one certificate configured for a target proxy."

This error occurs when there are no certificates assigned to the target proxy aside from those specified in the certificate map that you are trying to detach. To detach the map, first assign one or more certificates directly to the proxy.

Problems related to certificates issued by a CA Service instance

This section lists the most common errors you might encounter when using Certificate Manager to deploy Google-managed certificates issued by your CA Service instance and their possible causes.

If you receive the Failed to create Certificate Issuance Config resources error, check the following:

  • The lifetime. Valid certificate lifetime values are from 21 to 30 days.
  • The rotation window percentage. Valid rotation window percentages are from 1 to 99 percent. You must set the rotation window percentage in relation to the certificate lifetime so that certificate renewal occurs at least 7 days after the certificate has been issued and at least 7 days before it expires.
  • The key algorithm. Valid key algorithm values are: RSA_2048 and ECDSA_P256.
  • The CA pool. The CA pool either doesn't exist or is misconfigured. The CA pool must contain at least one enabled CA and the caller must have the privateca.capools.use permission on the target Google Cloud project. For regional certificates, the certificate issuance configuration resource must be created in the same location as the CA pool.

If you receive a Failed to create a managed certificate error, check the following:

  • The certificate issuance configuration resource you specified when creating the certificate exists.
  • The caller has the certificatemanager.certissuanceconfigs.use permission on the certificate issuance Configuration resource you specified when creating the certificate.
  • The certificate is in the same location as the certificate issuance configuration resource.

If you receive a Failed to renew certificate or a Failed to provision certificate error, check the following:

  • The Certificate Manager service account has the roles/privateca.certificateRequester permission on the CA pool specified in the certificate issuance configuration resource used for this certificate.

    Use the following command to check permissions on the target CA pool:

    gcloud privateca pools get-iam-policy CA_POOL
--location REGION

    Replace the following:

    • CA_POOL: the full resource path and name of the target CA pool
    • REGION: the target Google Cloud region

  • A certificate issuance policy is in effect. For more information, see Problems related to issuance policy restrictions.

Problems related to issuance policy restrictions

If Certificate Manager doesn't support the changes to a certificate made by the certificate issuance policy, certificate provisioning fails and the state of the managed certificate changes to Failed. To resolve the issue, confirm the following:

  • The identity constraints of the certificate allow for subject and subject alternative name (SAN) passthrough.
  • The maximum lifetime constraint of the certificate is greater than the lifetime of the certificate issuance configuration resource.

For the previous issues, because CA Service already issued the certificate, you're billed according to CA Service pricing.

If you receive the error Rejected for issuing certificates from the configured CA Pool, it indicates that the certificate issuance policy has blocked the requested certificate. To resolve the error, check the following:

  • The issuance mode of the certificate allows certificate signing requests (CSRs).
  • The allowed key types are compatible with the key algorithm of the certificate issuance configuration resource being used.

For the previous issues, because CA Service hasn't issued the certificate, you're not billed by CA Service.