Installing a Third Party SSL
In this tutorial:
You can purchase a dedicated SSL for your website either through InMotion Hosting or from a third party SSL vendor. This article focuses on the steps to take when ordering an SSL from a third party. If you would like to order an SSL through InMotion Hosting, please see our article on ordering an SSL certificate.
Request a CSR for a Third Party SSL
In order to properly key your website's SSL, your third party vendor will need a CSR (Certificate Signing Request). This CSR needs to be generated for your website by us, and our Support Team will be happy to assist you with the creation of your CSR. To request your CSR, please follow the steps below:
- Log into AMP.
- Click Simple CSR Request button.
- On the next page enter your desired certificate name. The most common certificate names are secure. or www. followed by the domain name. For example, if I was ordering a CSR for inmotionhosting.com, and I wanted the host name to be www, I would enter www.inmotionhosting.com.
- Click Next.
- In this next screen enter in the information you want associated with the SSL you are ordering from your third party vendor. This information should match the SSL information you will give the SSL vendor.
- Click Next.
- On the final page, review and confirm that you agree to the Terms of Service and click Submit.
Installation of your Third Party SSL
Once your CSR request is submitted, our Support Team will respond via email with your CSR. The email should be the one refrenced by the SSL and not necessarily with the primary email address on the hosting account. You will then provide the CSR to your SSL vendor so they can properly key your SSL. When you receive the SSL from your vendor, please respond to our email and attach your SSL. Our Support Team will then install your third party SSL.
SSL certificates require a dedicated IP address at a cost of $2.00 per month, billed yearly for $24.00. With all SSL certificates (ordered through us or through a third party vendor) there is a one-time $25 installation fee.
Wildcard SSL Installations
You can have Wildcard SSL certificates installed on VPS or Dedicated servers. We do not sell Wildcard SSL certificates, so you will need to contact a 3rd party SSL provider to obtain one. Also, Wildcard SSL certificates cannot be installed on shared hosting plans.
Important! In order to install a Wilcard certificates on VPS and Dedicated server, that each site needs to be on a separate cpanel account in order for us to install the certificate on your server.
To have a Wildcard SSL installed, you will need a CSR generated for each domain on your server that will use the Wildcard SSL. You then take the CSR and key the Wildcard certificate for each domain. You then email the CRT to support for installation. We install the same certificate to each cPanel account you created for each domain that will use the SSL.
How do I check on the status of my CSR request?
There is no need to check on the status of a CSR, since you will be emailed to the email address referenced by the SSL immediately, when it is generated.
Here is some additional information: When you request a CSR, it creates a ticket for Tech Support. They answer these tickets in the order they are received, and you will get an email as soon as your CSR is generated.
We value your feedback!
There is a step or detail missing from the instructions.
The information is incorrect or out-of-date.
It does not resolve the question/problem I have.
new! - Enter your name and email address above and we will post your feedback in the comments on this page!
2014-08-29 11:26 am
The article is helpful, but I noticed two things that would be VERY helpful to know while doing this process.
1.) Under "Installation of your Third Party SSL" and "How do I check on the status" you should include the fact that you email the CSR to the email address associated with the SSL certificate, NOT the email address on file with the InMotion Hosting account. This will inform your customers of what to expect.
My experience - I requested a CSR yesterday via my account at inmotionhosting.com at 9:28 AM CDT and assumed that it would take a few hours to work through the queue. I still had not received the emailed CSR info at 9:58 AM CDT today, so I called tech support. My email account is on file with InMotion Hosting since I am handling this migration for our company. I am really frustrated that I waited all day yesterday for the CSR to arrive, only to find out today that it WAS emailed yesterday at 10:48 AM to my boss's email address (it's associated with the SSL certificate). If I had known to expect the CSR to arrive at her account, I would have communicated with her to forward it to me. She went on vacation yesterday afternoon and I do not have access to her email. I have since received the CSR from a helpful tech agent (Sean B), but this information about where it was emailed would have been incredibly helpful yesterday.
2.) Clarify these instructions: "When you receive the SSL from your vendor, please respond to our email and attach your SSL." You should tell the customer to email email@example.com with the subject "SSL install" instead of responding to "our email" - tech agent Sean B advised me of this. Also, you should tell the customer to include their verification code to verify the account (either last 4 of credit card on file or the AMP password). If they don't include that phrase in their support email, the response will be delayed. Lastly, the customer should include that they authorize the charges for the install and the dedicated IP address to be charged to the credit card on file - again, so as not to delay the process.
I appreciate the assistance I've received from tech support, but I do feel that if these pieces of information had been available in your support articles, I would not have needed to call them so many times during this process.
2014-08-29 11:37 am
Thank you so much for your suggestions for improvement to the article. We will implement your first item immediately. As for the second item, responding to our email directly is the current best way and preferref policy. The reason is it would already be considered verified and ready to go, avoiding all the other details required in sending a fresh request. I will speak with the Support Supervisors to see if they wish to change that policy. If so, we will certainly reflect that in the article.