This article will provide steps for uploading and installing your 3rd-party SSL certificate.
What is a TLS/SSL Certificate?
SSL (Secure Sockets Layer) certificates are digital certificates used to identify ownership of a public key. This provides a way of assuring the user that the site can be trusted.
To obtain a certificate, a Certificate Sign Request (CSR) must be provided to a Certificate Authority (CA). We cover this in our Generating a CSR in Atomic article.
There are two paths to uploading and installing your certificate:
- If you generated your certificate using our "Generating a CSR in Atomic" article, follow these steps.
- If you generated your certificate using a CSR NOT provided by our new Atomic interface, follow these steps
How to install your certificate, If your CSR was obtained through the Atomic Interface.
Log into your Atomic dashboard, and click on the SSL section to your Left.
1. Select "upload certificate"
2. You will be prompted to either copy and paste your certificate, or upload a file containing your certificate (accepted file types for your certificate are .crt, .txt, .pem).
Scroll down to hit "submit"...
and you are done!
How to install your certificate, If your CSR was NOT provided by our Atomic interface
1. If your SSL cert was provisioned with a CSR not provided by the new Atomic dashboard you'll need to select "Add Certificate"...
2. Next, click on the "Import Existing Private Key & Certificate" near the bottom of the new window.
3. You will first have to provide your PRIVATE KEY by either copying and pasting the contents in the first text field, or uploading a file containing your private key...
4. In the second text field you will need to either copy and paste your certificate, or upload a file containing your cert.
1. Often multiple certificates, such as the Certificate Authority certificate, are provided along with your site's official cert. Your actual site's certificate should ALWAYS go first. The order of certificates after this (in general) do not matter.
2. If you uploaded a private key, and it does not match your certificate, issues may arise. Contact support if you have any questions about this.
3. Verify your site is now properly rendering under by visiting https://<yoursite> and making sure the lock appears without any warnings. Optionally enforce https on your entire site.