Skip to main content
All CollectionsSSL Certificates
Where to locate a misplaced SSL Private Key
Where to locate a misplaced SSL Private Key

Where to look if you've misplaced your private key

Garrett Saundry avatar
Written by Garrett Saundry
Updated today

Locating Your Private Key for an SSL Certificate

Your private key is located on (and was created by) the server for which the resulting SSL certificate is intended for. When you create a CSR, the private key is generated alongside it. This private key is crucial for the encryption and decryption processes that secure your communications. Here’s how you can re-locate your private key after it has been created:

1. During the Certificate Creation Process

  • Command Line Interface (CLI): If you used a CLI tool like OpenSSL to generate your SSL certificate, the private key is typically saved in the same directory where you ran the command. The file might be named something like private.key or server.key.

2. Web Hosting Control Panels

  • Plesk: If you are Webnames.ca hosting customer, go to the "Websites & Domains" section, select your domain, and then navigate to "SSL/TLS Certificates" to find your private key.

3. Server Configuration Files

  • Apache: The private key is usually stored in a file specified by the SSLCertificateKeyFile directive in your Apache configuration file (e.g., /etc/httpd/conf.d/ssl.conf).

  • Nginx: Look for the ssl_certificate_key directive in your Nginx configuration file (e.g., /etc/nginx/nginx.conf).

4. Operating System Specific Locations

  • Linux: Private keys are often stored in /etc/ssl/private/ or /etc/pki/tls/private/.

  • Windows: If you used IIS to generate the certificate, the private key is stored in the Windows Certificate Store. You can access it via the "Certificates" MMC snap-in.

Security Tips

  • Keep It Secure: Always store your private key in a secure location. Unauthorized access to your private key can compromise your SSL certificate.

  • Backup: Regularly back up your private key in a secure manner to prevent loss.

Did this answer your question?