Why Is an Error Reported When I Deploy an SSL Certificate with an Uploaded CSR to WAF, ELB, or CDN?

If you select Upload a CSR for CSR when applying for a certificate, the certificate file does not contain the certificate private key file after the certificate is issued. As a result, an error is reported when you deploy the certificate to WAF, ELB, or CDN.

When you manually generate a CSR file, a private key file is also generated. Although you do not need to upload the private key file when uploading the CSR file, you need to keep the private key file properly.

SCM makes it easier for you to quickly deploy such certificates to WAF, ELB, and CDN. Alternatively, you can directly deploy such certificates in those services. The detailed operations are as follows:

• Using SCM to deploy certificates
  1. Download a certificate.

     Download an issued certificate to the local PC. For details, see Downloading an SSL Certificate.

  2. Upload the certificate.

     Upload the certificate downloaded in 1 and the local private key file to SCM. For details, see Uploading an External Certificate.

  3. Deploy a certificate to WAF, ELB, or CDN.

     Deploy the uploaded certificate to WAF, ELB, and CDN in just few clicks. For details, see Deploying an SSL Certificate to Other Cloud Products.

• Not using SCM to deploy certificates
  1. Download a certificate.

     Download an issued certificate to the local PC. For details, see Downloading an SSL Certificate.

  2. Upload a certificate to WAF, ELB, or CDN.

     Upload the certificate downloaded in 1 to a specific cloud product, such as WAF, ELB, and CDN. For details, see the corresponding product documentation.