erroneous.netlify.app

How to generate a CSR in Microsoft IIS 7. Click Start, then Administrative Tools, then Internet Information Services (IIS) Manager. Click on the server name. Download c compiler for mac. From the center menu, double-click the 'Server Certificates' button in the 'Security' section (it is near the bottom of the menu). When you generated that CSR you would have been asked by the server to save two files—for OpenSSL, you can run the command openssl version –a to find the folder where your key files would be saved (/usr/local/ssl   by default). On Windows (IIS), the OS manages your CSRs for you. Crt and key files represent both parts of a certificate, key being the private key to the certificate and crt being the signed certificate. It's only one of the ways to generate certs, another way would be having both inside a pem file or another in a p12 container. Crt and key files represent both parts of a certificate, key being the private key to the certificate and crt being the signed certificate. It's only one of the ways to generate certs, another way would be having both inside a pem file or another in a p12 container.

Generate a certificate signing request

Before you can install a Secure Socket Layer (SSL) certificate, you must first generate a certificate signing request (CSR). You can do this by using one of the following methods:

OpenSSL

The following sections describe how to use OpenSSL to generate a CSR for a single host name. If you want to generate a CSR for multiple host names, we recommend using the Cloud Control Panel or the MyRackspace Portal.

Install OpenSSL

Check whether OpenSSL is installed by using the following command:

• CentOS® and Red Hat® Enterprise Linux®

  The following output provides an example of what the command returns:

• Debian® and the Ubuntu® operating system

  The following output provides an example of what the command returns:

If the preceding packages are not returned, install OpenSSL by running the following command:

• CentOS and Red Hat

• Debian and the Ubuntu operating system

Generate the RSA key

Run the following commands to create a directory in which to store your RSA key, substituting a directory name of your choice:

Run the following command to generate a private key:

Create a CSR

Run the following command to create a CSR with the RSA private key (output is in Privacy-Enhanced Mail (PEM) format):

When prompted, enter the necessary information for creating a CSR by using the conventions shown in the following table.

Note: You cannot use the following characters in the Organization Name or Organizational Unit fields: < > ~ ! @ # $ % ^ * / ( ) ? . , &

Warning: Leave the challenge password blank (press Enter).

Verify your CSR

Run the following command to verify your CSR:

After you have verified your CSR, you can submit it to a CA to purchase an SSL certificate.

Windows IIS Manager

Use the following steps to generate a CSR by using Windows IIS Manager:

Note: The following steps are for IIS 8 or IIS 8.5 on Windows Server 2012.

1. Open IIS Manager.
2. In the left-hand Connections pane, click the server for which you want to generate a CSR.
3. In the center server Home pane under the IIS section, double-click Server Certificates.
4. In the right-hand Actions pane, click Create Certificate Request.

5. In the Request Certificate wizard, on the Distinguished Name Properties page, enter the following information and then click Next.

   Field	Explanation	Example
   Common Name	The fully qualified domain name to which the certificate applies. The domain names example.com and www.example.com are distinct from each other, so be sure to submit your request for the right domain. If you are purchasing a wildcard certificate, use *.example.com.	example.com
   Organization Name	The exact legal name of your organization. The CA might seek to confirm that your organization is real and legally registered, so don’t abbreviate words that aren’t abbreviated in the organization’s legal name.	Example Inc.
   Organizational Unit	The branch of your organization that is making the request.	Marketing
   City/locality	The city where your organization is legally located. Do not abbreviate the city name.	San Antonio
   State/province	The state or province where your organization is legally located. Do not abbreviate the state or province name.	Texas
   Country/region	The two-letter ISO abbreviation for your country.	US

6. On the Cryptographic Server Provider Properties page, enter the following information and then click Next.

   • Cryptographic service provider: Unless you have a specific cryptographic provider, use the default selection.
   • Bit length: 2048 is the recommended bit length.
7. On the File Name page, enter the location where you want to save the certificate request file and then click Finish.

After you have generated the CSR, you can submit it to a CA to purchase an SSL certificate.

Cloud Control Panel

Rackspace provides the CSR Generator for generating a CSR. The CSR Generator shows you the CSRs that you currently have and lets you create new CSRs with a simple form. After you have entered your details, the generator combines them with your private key so that you can submit the combined encoded information to a CA.

When you are done with the generator, you can return to the Cloud Control Panel by clicking any of the links in the top navigation or by going to login.rackspace.com and selecting Rackspace Cloud from the drop-down product menu in the top navigation bar.

Access the CSR Generator

Access the CSR Generator directly or through the Control Panel by using the following steps:

1. Log in to the Cloud Control Panel and select Rackspace Cloud from the drop-down product menu in the top navigation bar.
2. In the top navigation bar, click Servers > Cloud Servers.
3. Click the name of the server for which you want to generate a CSR.
4. In the right-hand Managing Your Server section under Help me with, click Generate a CSR.

The generator lists your existing CSRs, if you have any, organized by domain name.

Generate a CSR

1. Click Create CSR.

2. Enter the following information, which will be associated with the CSR:

   Field	Explanation	Example
   Domain Name	The fully qualified domain name to which the certificate applies. The domain names example.com and www.example.com are distinct from each other, so be sure to submit your request for the right domain. If you want to secure both domains, you can use the Alt Names field. If you are purchasing a wildcard certificate, use *.example.com.	example.com
   Alt Names	(Optional) Additional domains that you want to add to the request. Each CA treats these differently, and the CA might charge for additional names. You can submit a comma-separated list.	www.example.com, secure.example.com
   Email Address	(Optional) A contact email address for the certificate.	support@example.com
   Organization Name	The exact legal name of your organization. The CA might seek to confirm that your organization is real and legally registered, so don’t abbreviate words that aren’t abbreviated in the organization’s legal name.	Example Inc.
   Organizational Unit	(Optional) The branch of your organization that is making the request.	Marketing
   City	The city where your organization is legally located. Do not abbreviate the city name.	San Antonio
   State or Province	The state or province where your organization is legally located. Do not abbreviate the state or province name.	Texas
   Country	Choose your country from the drop-down menu. The two-letter ISO abbreviation for your country is included in the CSR.	United States
   Private Key Bit Length	Key sizes smaller than 2048 are considered insecure and might not be accepted by a CA.	1024,2048,4096
   Hashing Algorithm	Both algorithms are currently trusted in mainstream browsers and offer industry recommended security. SHA-512 requires additional CPU processing.	SHA-256, SHA-512

   Note: You cannot use the following characters in the Organization Name or Organizational Unit fields: < > ~ ! @ # $ % ^ * / ( ) ? . , &

3. After you have entered all the required information, click Create CSR.

It can take between 5 and 60 seconds for the CSR to be generated. You might need to refresh the page that displays your CSRs before the new CSR is listed.

View CSR details

When CSR has been generated, you can click its UUID (unique identifier) in the CSR list to view its details screen.

This screen displays the information that you provided, the text of the CSR, and its associated private key.

Submit the CSR to the CA

The text in the Certificate Request field is the CSR. It contains encoded details of the CSR and your public key.

To request your SSL certificate, copy the Certificate Request text and submit it to your CA. Include all the text, including the BEGIN and END lines at the beginning and end of the text block.

Install the private key

Copy the private key to the server that will host the certificate. See your application documentation to determine where to install the private key and certificate on your server.

MyRackspace Portal

If you are a Managed or Dedicated customer, you can request a CSR through the MyRackspace Portal by using the following steps:

1. Log in to the MyRackspace Portal and select Dedicated Hosting from the drop-down product menu in the top navigation bar.
2. In the top navigation bar, click Tickets > Create Ticket.
3. On the Tickets / Create New Ticket page, select Generate Certificate Signing Request (CSR) from the Subject drop-down list.

4. Enter the following information in the Ticket Details section:

   Field	Explanation	Example
   Device(s)	The server or servers for which you want to generate a CSR. Use the drop-down menu to select your servers.
   Common Name	The fully qualified domain name to which the certificate applies. The domain names example.com and www.example.com are distinct from each other, so be sure to submit your request for the right domain. If you want to secure both domains, you can use the Alt Names field. If you are purchasing a wildcard certificate, use *.example.com.	example.com
   Alt. Names	(Optional) Additional domains that you want to add to the request. Each CA treats these differently, and the CA might charge for additional names. You can submit a comma-separated list.	www.example.com, secure.example.com
   Email Address	(Optional) A contact email address for the certificate.	support@example.com
   Organization	The exact legal name of your organization. The CA might seek to confirm that your organization is real and legally registered, so don’t abbreviate words that aren’t abbreviated in the organization’s legal name.	Example Inc.
   Organizational Unit	(Optional) The branch of your organization that is making the request.	Marketing
   Locality (City)	The city where your organization is legally located. Do not abbreviate the city name.	San Antonio
   State or Province Name	The state or province where your organization is legally located. Do not abbreviate the state or province name.	Texas
   Country	Choose your country from the drop-down menu. The two-letter ISO abbreviation for your country is included in the CSR.	United States

   Note: The bit length is automatically set to 2048.

5. Click Create Ticket.

Next steps

Reference

Experience what Rackspace has to offer.

©2020 Rackspace US, Inc.

Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License

Finding your Private Key on Different Servers or Control Panels
Linux-Based (Apache, Nginx, LightHttpd)
Windows Operating Systems
Mac OS X
Tomcat
cPanel
WHM
Plesk
Synology NAS DSM
Webmin
VestaCP
DirectAdmin
Webuzo

What Is a Private Key?

What Is a Private Key?

You’ve received your SSL Certificate, and now you need to install it.

Firstly, let’s go through some basics. Public Key Infrastructure (PKI) security is about using two unique keys: the Public Key is encrypted within your SSL Certificate, while the Private Key is generated on your server and kept secret.

All the information sent from a browser to a website server is encrypted with the Public Key, and gets decrypted on the server side with the Private Key. Together the key pair keeps communication secured, and one key will not work without the other.

How do I get it?

The Private Key is generated with your Certificate Signing Request (CSR). The CSR is submitted to the Certificate Authority right after you activate your Certificate. The Private Key must be kept safe and secret on your server or device, because later you’ll need it for Certificate installation.

Note: all Certificates except Multi-Domains support Private Key generation in your browser. The key is always saved during SSL activation, we never receive this information. That’s why it’s important you save and back it up during the process if you use the in-browser automatic generation method. If the Private Key key file is lost, you’ll need to reissue your Certificate.

Can I generate a new Private Key for my Certificate if I lose the old one?

Yes. You can generate a new private key and CSR, or use the automatic CSR and key generation during Certificate reissue (this option is available for all Certificates except for the Multi-Domains).

What does the Private Key look like?

It looks like a block of encoded data, starting and ending with headers, such as —–BEGIN RSA PRIVATE KEY—– and —–END RSA PRIVATE KEY—–.

You may not get to see this code when generating your CSR. Usually, it gets generated in the background with the CSR, and is automatically saved on your server. The system also fills the corresponding field automatically during installation of your Certificate in some control panels, such as cPanel.

The way this works varies depending on your web server, control panel, or any other tools used for CSR generation. Select the one that applies to you in the following section for specific guidance.

Finding your Private Key on Different Servers or Control Panels

Linux-based (Apache, NGINX, LightHttpd)

Normally, the CSR/RSA Private Key pairs on Linux-based operating systems are generated using the OpenSSL cryptographic engine, and saved as files with “.key” or “.pem” extensions on the server.

But no specific extensions are mandatory for text files in Linux, so the key file may have any name and extension, or no extension at all.

If you remember the whole name of the key file or at least part of it, you can use the following command in your console to find the file and its directory:

The slash symbol in this command implies that the search begins from the root directory of the server. This way you have more file options to view. The name of the file in between the single quotation marks should be the part of the name that you remember. To search for the file by extension, enter “*.key” to view all the files with the “.key” extension on your server.

Tip: often the name of the file corresponds to the domain name it was generated for e.g. “domain_tld.key” or “domain.tld.pem”.

Here’s another useful command that lets you search files by their content:

This command will return the absolute path to the Private Key file if it’s located on your server.

Windows Operating Systems (IIS, Exchange, Small Business server)

Windows servers don’t let you view the Private Key in plain text format. When you import your Certificate via MMC or IIS, the Private Key is bound to it automatically if the CSR/Key pair has been generated on the same server.

If you need to obtain the Private Key to install your Certificate on a different server, you can export the key in a password protected PFX (PKCS#12) file. To do that, open the MMC Certificates snap-in tools following these steps:

Win+R >> mmc.exe >> OK >> File >> Add/Remove Snap-in >> Certificates >> Add >> Computer account >> Next >> Local computer >> Finish >> OK

Next, go to Certificate Enrollment Requests >> Certificates (if you haven’t completed the Certificate request yet). If you’ve done that, you’d select Personal >> Certificates, then right-click the Certificate >> select All Tasks >> Export. G data 2014 key generator download. The Export wizard will open, and give you instructions. You can find more detailed instructions here.

Once that’s done, you will see the .pfx file containing your Certificate, CA-Bundle, and Private Key. To extract the key, use this tool. Choose the PKCS12 to PEM option, then upload the file and enter your chosen password.

Mac OS X

The Keychain tool in the Server application of Mac OS X won’t allow you to access the Private Key via the graphic user interface. Instead use the Terminal, by opening /etc/certificates/ directory and clicking the file.

Its name should be something like “*.key.pem”. And the terminal commands to open the file are: cd /etc/certificates/ , then ls , and sudo nano test.key.pem.

Note: to check if the Private Key matches your Certificate, go here. Then paste the Certificate and the Private Key text codes into the required fields and click Match.

Tomcat

If your Tomcat SSL connector is configured in JSSE style, the Private Key must be in a password-protected keystore file with a .jks or .keystore extension. This file, unlike most other cases, is created before the CSR. To extract the Private Key, you’ll need to convert the keystore into a PFX file with the following command:

Tips:

1. “Keystore.jks” should be replaced with your actual keystore name,
2. “keystore.p12” will be the name of the PKCS12 file you will receive,
3. <jkskeyalias>, <jkspassword> and <keypassword> are the alias (key and keystore passwords that were entered during keystore generation),
4. <jkskeyalias>, <jkspassword> and <keypassword> should be replaced with your JKS file alias, its password, and Private Key password.
5. <newp12password> and <newkeypassword> should be replaced with the passwords you set for your new PKCS12 file and the Private Key.

After the PKCS12 file is generated, you can convert it to a PEM file with separated CRT, CA-Bundle and KEY files using this tool. Alternatively, use the following command in the terminal:

“Private.key” can be replaced with any key file title you like.

cPanel

1. SSL/TLS Manager
   a) The simplest way to get the appropriate key used during SSL installation is reflected in the below picture:
   b) Alternatively, you can find the Private key in the Private keys section of the SSL/TLS Manager, which can be located in the cPanel main menu. You will see all the Private Keys ever generated in your cPanel. To view the code of the key, click View & Edit. If there are several keys in that menu, you can copy each of them to find a match with your Certificate code by using this tool.
2. File manager
   On the homepage of your cPanel, click File manager. Find the folder named “ssl” in the folder tree to the left (see screenshot). That folder will contain another folder named “keys”. This key folder also contains all the keys ever generated in your cPanel.
   

WHM

WHM stores your private keys and CSR codes in the SSL Storage Manager menu. On the homepage, click SSL/TLS >> SSL Storage Manager. To view the Private Key, click the magnifier icon next to the relevant key in the Key column.

Plesk

Click Domains >> your domain >> SSL/TLS Certificates. You’ll see a page like the one shown below. The key icon with the message “Private key part supplied” means there is a matching key on your server.

To get it in plain text format, click the name and scroll down the page until you see the key code. Alternatively, click the green arrow icon on the right. This will download a PEM file, containing your Private Key, Certificate and CA-Bundle files (if they were previously imported to the server). The files can be opened in any text editor, such as Notepad.

Synology NAS DSM

When generating a CSR in Synology DSM, the Private Key is provided to you in a zip file on the last step. The key code is contained within a server.key file, that can be opened with a text editor, such as Notepad.

Webmin

Webmin works as a graphic user interface (GUI) on top of the command-line interface. There is also a file manager called Filemin, that you can use to browse the server file system and find your Private Key file. Alternatively, go to Others >> Command Shell and run the find or grep command, which you can find in the Linux Operating Systems section above.

VestaCP

When I Generate A Csr Where Is My Key File Online

Your Private Key needs to be saved during CSR generation, as it will not be available via the graphic user interface.

That said, you may be able to retrieve your Private Key via SSH. It is saved as a temporary file in the “/tmp” folder. The path to the file will look something like this: “/tmp/tmp.npAnkmWFcu/domain.com.key”.

Note: the files in the /tmp directory are deleted every time your server is rebooted, so this is not a safe place to store your Private Key.

To get the path to your key file, use this Linux command:

When I Generate A Csr Where Is My Key File Download

Where you see “domain.com”, replace this with the actual domain name you generated the CSR for.

The path to your key file can also be found using the grep command:

DirectAdmin

In the up-to-date version of DirectAdmin, your Private Key is saved on the server. Access it in the “Paste a pre-generated Certificate and key” field during installation.

If that section is empty, it may mean the CSR and key were generated elsewhere, or the key was not saved in DirectAdmin due to a glitch. If a glitch happened, try retrieving the key via SSH. Usually it is saved in this directory:

/usr/local/directadmin/data/users/<user>/domains/<domain>.key

Note: <user> and <domain> are your DirectAdmin details.

Webuzo

When I Generate A Csr Where Is My Key File Free

On the homepage, find the SSL management section by clicking the Private Keys button. This will display a list of all the Private Keys generated in Webuzo. To see the key code, click the pencil icon to the right under the Option column, as shown in the screenshot below:

To sum up, ways to find your private key fully depend on the interface of the web server where you generate the CSR. If the methods described above did not help you find the private key for your certificate, the only solution would be to generate a new CSR/private key pair and reissue your certificate and to make sure that the key is saved on your server/local computer this time.