Install SSL certificates with clear PEM downloads

After issuance, download the certificate PEM and private key PEM from your SSL domains page. Point nginx, Apache, Caddy, or your panel at those files — keep hosting where it is.

Home / SSL / Installation

Download what servers expect

Issued domains expose a download action that returns certificatePem and privateKeyPem. Save them as fullchain/cert and key files on the machine that terminates TLS.

Certificate PEM (leaf + chain as issued)
Private key PEM (keep secret; never commit to git)
In-app notes for nginx, Apache, and Caddy

Typical install flow

Issue → validate DNS → download PEMs → configure your web server or load balancer → reload → confirm HTTPS in a browser.

nginx: ssl_certificate + ssl_certificate_key
Apache: SSLCertificateFile + SSLCertificateKeyFile
Caddy / panels: paste or point at the PEM paths

Keep hosting separate

docstoc is not your CDN or shared host. Installation stays on your infrastructure — we automate the certificate lifecycle, not the HTML.

Security note

Treat private keys like passwords. Download over HTTPS while signed in; store only on the server that needs them.
After renewals, replace the files and reload the web server (or automate that step yourself).

Try it

Tools for a quick check — or open the product when you’re ready to issue.

Download from SSL console → · Then set up monitoring

FAQ

Do you push certificates into Cloudflare or my host automatically?

Not today. You download PEMs and install them where TLS terminates. Edge platforms that issue their own certs (e.g. Cloudflare Universal SSL) remain a separate architecture choice.