Name: Servd Hosting
Price range: $$

Documentation

Custom SSL Certificates (Legacy)

The following documentation refers to functionality in use by older projects on our platform.

If you have an existing SSL certificate purchased from an external certificate authority, you can attach it to any of your custom domains for Servd to use.

Servd expects your certificate to have two elements:

The private key used to generate the certificate
The full certificate chain

These can be stored in several different formats and you might need to convert them to match Servd's expectations.

Servd expects your private key to be an RSA 2048 (or greater) key, and look something like this:

The certificate chain should include all of the leaf/server and intermediate certificates which you have been provided. They should be saved in a PEM-encoded X.509, with the leaf/server certificate first, and look something like this:

Once you have these files ready you can add the SSL certificate to any of your custom domains by clicking the 'Use Custom' button on the Project Settings > Domains page in the Servd dashboard.

Simply paste in your files and 'Save'

Once updated you'll need to run a 'Sync' to get your changes deployed.

Converting a pfx bundle to the correct format #

pfx files are a bundle which contain both your certificate chain as well as your private key. Servd requires these in a slightly different format, but we can convert from one to the other using openssl.

1. Extract the encrypted private key

openssl pkcs12 -in [yourbundle.pfx] -nocerts -noenc -out private-encrypted.key

You'll need to enter the password which was used to create the pfx bundle first.

It will then request another password to use to secure the newly extracted private key. Leave this blank.

2. Extract the certificate chain

openssl pkcs12 -in [yourbundle.pfx] -nokeys -out certificates.crt

You should now have a private.key file and a certificates.crt file. The contents of these can be added directly to the Servd dashboard.