Top Ten Requested Technotes • - How to recover the private key of an SSL certificate in an IIS environment? • - How to generate Certificate Signing Request using Microsoft Management Console (MMC) on Windows 2012 • - How do I resolve the error: 'Certificate has expired or is not yet valid'? • - How do I convert a.pfx to be used with an Apache server?

• - Why do I receive the error SSL_ERROR_BAD_CERT_ALERT - SSL client cannot verify your certificate.)? • - How do I generate a 2048 bit CSR using Java Keytool? • - How can I change the pass-phrase on my private key file for Apache using OpenSSL? • - CSR Generation and Installation using Certreq command (Windows) • - Why do I receive the Error: 'RSA server certificate CommonName (CN) 'www.domain.com' does NOT match server name'? • - How do I convert my.pfx file to a Java Keystore?

You will follow these steps to move or copy that working certificate to the Windows server: Convert the individual certificate files and private key to a.pfx file. Copy the.pfx file to the Windows server. Import the.pfx file to the Windows store. Configure your IIS web sites to use the certificate.

Apache: Creating Your CSR with OpenSSL Use the instructions in this section to create your own shell commands to generate your Apache CSR with OpenSSL. Recommended: Save yourself some time. Use the to generate an OpenSSL command to create your Apache CSR.

Just fill out the form, click Generate, and then paste your customized OpenSSL command into your terminal. How to Generate a CSR for Apache Using OpenSSL If you prefer to build your own shell commands to generate your Apache CSR, follow the instructions below. • Log in to your server via your terminal client (ssh). • Run Command At the prompt, type the following command: Note: Make sure to replace server with the name of your server.

Openssl req –new –newkey rsa:2048 –nodes –keyout server.key –out server.csr • Generate Files • You've now started the process for generating the following two files: • Private-Key File: Used to generate the CSR and later to secure and verify connections using the certificate. • Certificate Signing Request (CSR) file: Used to order your SSL certificate and later to encrypt messages that only its corresponding private key can decrypt. • When prompted for the Common Name (domain name), type the fully qualified domain (FQDN) for the site that you are going to secure. Note: If you're generating an Apache CSR for a, make sure your common name starts with an asterisk (e.g., *.example.com). • When prompted, type your organizational information, beginning with your geographic information. Note: You may have already set up default information.

• Now, your OpenSSL.csr file is created. • Order Your SSL/TLS Certificate • Open the.csr file you created with a text editor.

• Copy the text, including the -----BEGIN NEW CERTIFICATE REQUEST----- and -----END NEW CERTIFICATE REQUEST----- tags, and paste it in to the. • Save Private Key Save (back up) the generated.key file. You need it later to install your SSL certificate.

• Install Certificate After you've received your SSL certificate from DigiCert, you can install it on your server. Apache: Installing & Configuring Your SSL Certificate If you still need to create a certificate signing request (CSR) and order your certificate, see. After we've validated and issued your SSL certificate, you can install it on your Apache server (where the CSR was generated) and configure the server to use the certificate. How to Install and Configure Your SSL Certificate on Your Apache Server • Copy the certificate files to your server. • Log in to your and download the intermediate (DigiCertCA.crt) and your primary certificate ( your_domain_name.crt) files.

• Copy these files, along with the.key file you generated when creating the CSR, to the directory on the server where you keep your certificate and key files. Note: Make them readable by root only to increase security. • Find the Apache configuration file (httpd. Game Maker Exe To Gmkyy. conf) you need to edit. The location and name of the configuration file can vary from server to server—especially if you're using a special interface to manage your server configuration. • Apache's main configuration file is typically named httpd.conf or apache2.conf.

Possible locations for this file include /etc/httpd/ or /etc/apache2/. For a comprehensive listing of default installation layouts for Apache HTTPD on various operating systems and distributions, see. • Often, the SSL certificate configuration is located in a block in a different configuration file.

The configuration files may be under a directory like /etc/httpd/vhosts.d/, /etc/httpd/sites/, or in a file called httpd-ssl.conf. One way to locate the SSL Configuration on Linux distributions is to search using grep, as shown in the example below.

Run the following command. • Identify the SSL block you need to configure.

If your site needs to be accessible through both secure (https) and non-secure (http) connections, you need a virtual host for each type of connection. Make a copy of the existing non-secure virtual host and configure it for SSL as described in step 4.

With Me In Seattle Series Pdf Español. If your site only needs to be accessed securely, configure the existing virtual host for SSL as described in step 4. • Configure the block for the SSL-enabled site • Below is a very simple example of a virtual host configured for SSL. The parts listed in blue are the parts you must add for SSL configuration.

DocumentRoot /var/www/html2 ServerName www.yourdomain.com SSLEngine on SSLCertificateFile /path/to/your_domain_name.crt SSLCertificateKeyFile /path/to/your_private.key SSLCertificateChainFile /path/to/DigiCertCA.crt • Make sure to adjust the file names to match your certificate files. • SSLCertificateFile is your DigiCert certificate file (e.g., your_domain_name.crt). • SSLCertificateKeyFile is the.key file generated when you created the CSR (e.g., your_private.key). • SSLCertificateChainFile is the DigiCert intermediate certificate file (e.g., DigiCertCA.crt) Note: If the SSLCertificateChainFile directive does not work, try using the SSLCACertificateFile directive instead. • Test your Apache configuration file before restarting. As a best practice, check your Apache configuration file for any errors before restarting Apache.

Caution: Apache won't start again if your configuration files have syntax errors. Run the following command to test your configuration file (on some systems, it's apache2ctl). Apachectl stop apachect1 start Restart Notes: If Apache doesn't restart with SSL support, try using apachectl startssl instead of apachectl start. If SSL support only loads with apachectl startssl, we recommend you adjust the apache startup configuration to include SSL support in the regular apachectl start command. Otherwise, your server may require to manually restart Apache using apachectl startssl in the event of a server reboot.

This usually involves removing the and tags that enclose your SSL configuration. • Congratulations! You've successfully installed your SSL certificate. Testing Your SSL/TLS Certificate Installation • Browser Test • For best results, make sure to close your web browser first and then re-launch it.

• Visit your site with the secure https URL (i.e., go to not • Be sure to test your site with more than just Internet Explorer. IE downloads missing intermediate certificates; whereas, other browsers give an error if all the certificates in the certificate chain aren't installed properly.

• DigiCert ® SSL Installation Diagnostic Tool If your site's publicly accessible, use our to test your SSL/TLS certificate installation; it detects common installation problems. Troubleshooting • If your web site's publicly accessible, our tool can help you diagnose common problems. • If you receive a 'not trusted' warning, view the certificate details to see if it's the certificate you expect. Check the Subject, Issuer, and Valid To fields. • If it's the certificate you expect and the is issued by DigiCert, then your SSLCertificateChainFile is not configured correctly. • If you don't see the certificate you expect, then you may have another SSL block before the one you recently configured. Name based virtual hosts aren't possible with https unless you use the same certificate for all virtual hosts (e.g., a Wildcard or a Multi-Domain SSL certificate).

This is not an Apache limitation, but an SSL protocol limitation. Apache must send a certificate during the SSL handshake before it receives the HTTP request that contains the Host header. Therefore, Apache always sends the SSLCertificateFile from the first block that matches the IP and port of the request. • For help moving your certificates to additional servers or across server platforms, see our. • If you need to disable SSL version 2 compatibility in order to meet, add the following directive to your Apache configuration file.