I doubt you generated a cert with OpenSSL that just happens to match an established public root. Do you maybe mean you generated a key and CSR (cert request) with OpenSSL and used the CSR to get a cert from a CA such as Comodo that is under (or bridges under) AddTrust External?Anyway, something is messed up in your files. I generated the self-signed SSL certificate using OpenSSL & shared with them along with the private key (I know we shouldn't). They asked me to share a valid public key & SSL certificate. I even generated a certificate & private key on DigiCert, but couldn't figure out how to generate a public key. What I am trying to do is, create a CSR and with a private key that is password protected (the key). In OpenSSL I can create a private key with a password like so: openssl genrsa -des3 -out privkey.pem 2048 Is there some way I can use the key I just created and generate a CSR using the key?
Our QR Management and Tracking solution “” offers dynamic, changeable QR codes with analytics (especially suitable for advertising agencies). Qr code generator enter key.
- Comodo Generate Csr With Openssl Private Key Mismatch Tool
- Comodo Generate Csr With Openssl Private Key Mismatch Download
The following instructions will guide you through the CSR generation process on Nginx (OpenSSL). To learn more about CSRs and the importance of your private key, reference our Overview of Certificate Signing Request article. If you already generated the CSR and received your trusted SSL certificate, reference our SSL Installation Instructions and disregard the steps below.
1. Log in to your server’s terminal.
You will want to log in via Secure Shell (SSH).
2. Enter CSR and Private Key command
Generate a private key and CSR by running the following command:
Here is the plain text version to copy and paste into your terminal:
Note:Replace “server ” with the domain name you intend to secure.
3. Enter your CSR details
Enter the following CSR details when prompted:
- Common Name: The FQDN (fully-qualified domain name) you want to secure with the certificate such as www.google.com, secure.website.org, *.domain.net, etc.
- Organization: The full legal name of your organization including the corporate identifier.
- Organization Unit (OU): Your department such as ‘Information Technology’ or ‘Website Security.’
- City or Locality: The locality or city where your organization is legally incorporated. Do not abbreviate.
- State or Province: The state or province where your organization is legally incorporated. Do not abbreviate.
- Country: The official two-letter country code (i.e. US, CH) where your organization is legally incorporated.
Note: You are not required to enter a password or passphrase. This optional field is for applying additional security to your key pair.
4. Generate the order
Locate and open the newly created CSR in a text editor such as Notepad and copy all the text including:
Note 1: Your CSR should be saved in the same user directory that you SSH into unless otherwise specified by you.
Note 2: We recommend saving or backing up your newly generate “.key ” file as this will be required later during the installation process.
Return to the Generation Form on our website and paste the entire CSR into the blank text box and continue with completing the generation process.
Upon generating your CSR, your order will enter the validation process with the issuing Certificate Authority (CA) and require the certificate requester to complete some form of validation depending on the certificate purchased. For information regarding the different levels of the validation process and how to satisfy the industry requirements, reference our validation articles.
After you complete the validation process and receive the trusted SSL Certificate from the issuing Certificate Authority (CA), proceed with the next step using our SSL Installation Instructions for Nginx using OpenSSL.