Skip to content

HTTPS Configuration Guide

Configuration Scenario

Cloud Protection supports HTTPS service. You can deploy it by uploading certificates or directly deploying certificates already hosted in Cloud Protection SSL Certificate Management to the Cloud Protection platform, enabling HTTPS acceleration service to achieve encrypted data transmission across the entire network.

Configuration Guide

Method 1:

In the menu bar, select 【Domain Management】, click 【Configure】 on the right side of the domain name to enter the domain configuration page 【Advanced Configuration】, and proceed to configure.

Certificate configuration includes self-owned certificates and hosted certificates. Below is the configuration method for self-owned certificates:

Below is the configuration method for hosted certificates. Note that the certificates must be uploaded in the certificate hosting section first. For details, refer to Hosted Certificates.

Method 2:

Go to the 【Certificate Configuration】 page in the left menu bar. You can choose either single certificate configuration or batch certificate configuration. Generally, single-domain certificates use certificate configuration, while wildcard certificates use batch certificate configuration.

Domain Configuration

  1. Select the domain name under the 【Certificate Configuration】 menu bar, choose the accelerated domain name that needs certificate configuration, and select either self-owned certificates or hosted certificates. Below is the configuration method for self-owned certificates:

  1. For hosted certificates, select the accelerated domain name that needs certificate configuration and choose hosted certificates:

  1. Origin Protocol

In addition to setting the origin protocol when connecting to the Cloud Protection domain or in the origin server configuration module, you can also adjust the origin protocol when configuring certificates. Cloud Protection supports the following two origin protocols:

  • HTTP Origin: All requests use HTTP for origin, meaning the origin server does not have a certificate configured.
  • Protocol Follow: The origin protocol follows the request protocol. HTTPS requests use HTTPS for origin, and HTTP requests use HTTP for origin. Choose this method if the origin server has a certificate configured.

Batch Certificate Configuration

Click 【Batch Certificate Configuration】 above to automatically match suitable domain names for batch configuration by uploading certificates:

  1. Select Domain Certificate

If you already have a certificate, you can directly paste the PEM-formatted certificate content and private key into the corresponding fields:

  • Cloud Protection now supports ECC certificate deployment.
  • The certificate content must be in PEM or CRT format. For certificates in other formats, refer to PEM format conversion.
  • You can choose Cloud Protection hosted certificates for one-click deployment.

  1. Select Domain Name

Based on the uploaded/selected certificate, CDN will automatically match the list of domain names that can be configured. You can select the required domain names for configuration:

  1. Origin Protocol

In addition to setting the origin protocol when connecting to the accelerated domain or in the origin server configuration module, you can also adjust the origin protocol in bulk during batch certificate configuration. Cloud Protection supports the following two origin protocols:

  • HTTP Origin: All requests use HTTP for origin.
  • Protocol Follow: The origin protocol follows the request protocol. HTTPS requests use HTTPS for origin, and HTTP requests use HTTP for origin.

Note: After submitting batch configuration, the selected domain names will deploy certificates one by one. If an exception occurs, the list page will show a "Update Failed" status, and the original configuration will remain effective. In case of update failure, click 【Edit】 on the right to reconfigure.

Certificate Update

Click 【Edit】 on the right side of the certificate to update the certificate for a specific domain name or perform batch configuration again to overwrite the original certificate configuration.

Certificate updates take effect node by node across the entire network seamlessly, without affecting the current HTTPS service. You can also click 【Delete】 to cancel the HTTPS acceleration service.

Certificate Expiration

Cloud Protection will send expiration reminders via SMS and email to the user account 30 days, 15 days, 7 days before expiration, and on the day of expiration.