Creating CDN services with SSL enabled

Introduction

Secure Sockets Layer (SSL) allows you to access CDN services over HTTPS protocol.

We provide the following SSL solutions for our CDN services: CDN Static, CDN Static Push and CDN HTTP Live.

SNI LE SSL We provide you an SSL certificate (issued by the Let's Encrypt certificate authority) for your domain for free and we enable it for your CDN service for free.
SNI SSL You provide us an SSL certificate for your domain and we enable it for your CDN service for free.

How to enable SNI LE SSL / SNI SSL

  • Create a CDN Static (Pull/Push) or CDN HTTP Live service.
  • Go to Services/Certs.
  • Select your desired SSL type and CDN service.
  • For SNI LE SSL just click Add Certificate and that's all.
  • For SNI SSL continue to the next step:
    • Please note that every SSL certificate contains a Common Name (CN) and, alternatively, Subject Alternative Names (SANs). If you intend to use your certificate for your CDN service, your CDN Service Domain must match your certificate's Common Name or be included in its Subject Alternative Names. You can verify your certificate details using our SSL certificate viewer. If your CDN Service Domain does not match your certificate's Common Name and is not included in its Subject Alternative Names, browsers will throw an SSL error when accessing your CDN service via https://. In the following examples, let's assume that your CDN Service Domain is static.mycompany.com.

      Examples

      CN:mycompany.com
      SANs:mycompany.com, www.mycompany.com
      You can not use this SSL certificate.
      CN:static.mycompany.com
      SANs:N/A
      You can use this SSL certificate.
      CN:mycompany.com
      SANs:mycompany.com, www.mycompany.com, static.mycompany.com
      You can use this SSL certificate.
      CN:*.mycompany.com
      SANs:N/A
      You can use this SSL certificate.
    • You can use our SSL certificate viewer to verify your SSL certificate details. If your certificate matches your CDN service, navigate to the Services/Certs page and input your certificate in PEM format. To prevent unintended white space symbols (such as spaces or new lines), it's advisable to first paste your certificate into a text editor and then copy-paste it into our form. This ensures that the format of your certificate is supported. Your certificate may be either a single-domain certificate or a wildcard certificate. Ensure that you also include all intermediate certificates necessary for a complete certificate chain, appending them below your certificate as illustrated in the following example.

      -----BEGIN CERTIFICATE-----
      MIIF7zCCA9egAwIBAgIUPoIIvvvppIGsF9xZgJ6qQnVyQwEwDQYJKoZIhvcNAQEL
      BQAwgYYxCzAJBgNVBAYTAlhYMRIwEAYDVQQIDAlTdGF0ZU5hbWUxETAPBgNVBAcM
      CENpdHlOYW1lMRQwEgYDVQQKDAtDb21wYW55TmFtZTEbMBkGA1UECwwSQ29tcGFu
      eVNlY3Rpb25OYW1lMR0wGwYDVQQDDBRDb21tb25OYW1lT3JIb3N0bmFtZTAeFw0y
      NDAzMTAxNjM5MTdaFw0zNDAzMDgxNjM5MTdaMIGGMQswCQYDVQQGEwJYWDESMBAG
      -----END CERTIFICATE-----
      -----BEGIN CERTIFICATE-----
      /f4G1mgUXQ37RNELDMBOiGbjdLjXTI3COfR4qj1O1d1iQ6JW1pfwo6BUyklZE4Dp
      ByZHRuguSgvBRiWCs2lK/wPUuN5ZfkodugzIjwUE2GeMoxsOyDBnNSTkXEJ83C7e
      oCoL+8YGbcchn+w/r+JKnHaPy7Vtm5S3T/TcYR0inMr4Fe/3fyzqX0pUDaj4GGZv
      +zzlPluDOYKbUF/3OiK5TCoiz6/WveOviI4nQ/TN79hICy9snxICMpHHhNfbXdPj
      -----END CERTIFICATE-----
      
    • Fill in your certificate key in the non-encrypted format. You can use this online SSL certificate key matcher to check if your certificate and key match.

      -----BEGIN PRIVATE KEY-----
      MIIJQwIBADANBgkqhkiG9w0BAQEFAASCCS0wggkpAgEAAoICAQDDV77lanoZ+b4c
      eQ+eaYNZozQYnKZB9g7CB3FO4U1DnLpTv4eszo+sRAk/G2rAqGUANe+oealTR0Mv
      v//V4Rpzfl+4BQHcpPMF1JpQsle+oy5xnuMETtSiz5KyB9JEU5TwhTVu7aZT4IjG
      FtmmJbwY9ATRYb6ZA5MUFnbZWuM29OjPadJH1TyWA67dT7a3koT9et2RlFtcJWt2
      dF5T/mgkfPTj4wHJTgbufNtfi/p4eTO2Sz/2rp9r3tDMwirA0xbw/U3tihcqtv3o
      -----END PRIVATE KEY-----
      
  • Click on the Add Certificate button.
  • That's all.

Updating SNI LE certificate domains

When you create an SNI LE SSL certificate, it is issued for the CDN Service Domain and Secondary Service Domains configured for your CDN service at that time. Changing these settings does not automatically update the existing certificate.

  • For SNI SSL, you are responsible for providing a valid certificate that covers all domains configured for your CDN service. If you add or change a domain, make sure that your certificate covers it before using it over HTTPS.
  • For SNI LE SSL, you can update the certificate to match the current CDN Service Domain and Secondary Service Domains. Go to Services/Certs and open the certificate settings. If the CDN configured domains differ from the certificate domains, the Update Certificate button appears. Click it to issue an updated certificate for the domains currently configured for your CDN service.

Before updating an SNI LE SSL certificate, make sure that the DNS CNAME records for all configured domains point to your CDN service as described in Services/How-To. The DNS records must be in place and resolvable before the certificate can be issued.

Note: You can also use this feature together with Secondary Service Domains to change your CDN Service Domain without downtime.

Notes

Contact Us

 __   _     _____      _____  
| || | ||  |  ___||   / ___// 
| '--' ||  | ||__     \___ \\ 
| .--. ||  | ||__     /    // 
|_|| |_||  |_____||  /____//  
`-`  `-`   `-----`  `-----`