How to add and update a TLS certificate and private key

Modified on Thu, 1 Aug at 12:27 PM

To accept and optimise HTTPS traffic for your site, we need to install the public certificate and private key in PEM format on our servers. This step is mandatory to ensure TLS termination of your site.


The files to be supplied are :

  • The certificate: a file starting with -----BEGIN CERTIFICATE-----
  • The private key: a file starting with -----BEGIN RSA PRIVATE KEY-----


To install the certificate :

  1. Go to the Fasterize dashboard.
  2. Go to the Organisation > Certificates section.
  3. Click on Import a certificate and follow the instructions to import your certificate and private key.


Once the certificate has been imported, it will be automatically deployed on the configuration(s) concerned.


You can also request support to help you with this process.



Updating the CDN configuration takes around five minutes.


Caution: A certificate has a limited life. Fasterize sends you a reminder as the expiration date of your certificate (s) expires. 


Updating a TLS certificate and private key

To update an existing certificate, follow these simple steps:


  1. Go to Organisation > Certificates on the Fasterize dashboard.
  2. Locate the certificate you wish to update.
  3. Click on Update in front of the certificate in question.


Generating a new certificate via a CSR request

If you want to generate a certificate only for Fasterize, it is possible to ask us to generate a CSR file. The private key will then be generated on our servers and we will send you a CSR file to send to your CA. Once the public certificate has been generated, we will install it on our platform.


Please note that the length of your key must be 1024 or 2048 bits and cannot exceed 2048 bits.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article