SSL Certificate options

You can install your own SNI Certificate or have us cover your streams with our InstantSSL certificates.

You can manage the SSL used for your Streaming Channels in the CDN77 client portal when you select the Stream and go to the "CNAMEs & SSL" section.

When uploading your certificate, please remember to include also the Intermediate certificates provided by your certification authority.

The format in which you add your certificate should be as follow:

First column "Certificate (CRT) - along with intermediate certificates"

-----BEGIN CERTIFICATE-----
[your certificate's CRT data]
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
[your certificate's CRT data]
-----END CERTIFICATE-----

Second column "Private Key"

-----BEGIN PRIVATE KEY-----
[your certificate's key data]
-----END PRIVATE KEY-----

Note: Does not work with any Internet Explorer versions that run on Windows XP, and default Android 2.X browsers). One certificate can be connected to multiple Resources if issued for such.

Additionally, we offer these SSL options.

  1. Instant SSL* - once you add your CNAME to the Streaming Channel and it is pointing to our CDN URL in your DNS, we automatically create a certificate from Let's Encrypt for you and install it on your resource (as SNI), so your CNAME is accessible via SSL, more about this can by found here, the SSL will still work also for the CDN URL, the certificate validity is automatically renewed as long as all CNAMEs point at provided CDN URL

  2. Custom SAN SSL purchased with us - your CNAME added to our own certificate as a SAN (Subject Alternative Name) – works on any browser / OS. This option is billed, the price is $69 / CNAME / 1 year.

 

If you use SSL also on your Origin, you should select the HTTPS option next to your Origin, when creating the CDN Resource, to make sure our cache servers will access and cache the files from your origin over HTTPS.

 

* It may take up to 30 minutes, after you add the CNAME and point it to the CDN URL, untill new Instant SSL certificate is created and instaled on the Resource. In order for the InstantSSL to work, all the CNAMEs added to the CDN Resource must work and point to the CDN URL in your DNS.