In this article, we will show you how to install an SSL Certificate on Plesk Onyx. You will also learn how to generate a CSR code from Plesk directly, and, as a bonus, a few interesting facts about Plesk’s history. Finally, we will give you useful tips on where to buy the best SSL Certificate for Plesk.
Generate CSR in Plesk
First, you need to lay the foundations for your SSL installation. The CSR (Certificate Signing Request) code is required during the SSL verification and validation. You can generate the CSR code for your domain from your Plesk dashboard. Here is how you can do it:
- Log into your Plesk dashboard
- From the left pane, select Domains and locate the domain name you want to secure
- From the main central menu click on SSL/TLS Certificates
- In the new page, click Add SSL/TLS Certificate
- Now, you have to submit a list of parameters. Make sure the info about your company is up to date
- Certificate Name: Enter an easy-to-remember name so you can identify this certificate from other similar files
- Bits: From the drop-down list, select the encryption level for your certificate. We recommend the standard 2048
- Country: From the drop-down list indicate your company’s country of origin
- State or province: Enter the full name of the state where your business is legally located. For instance, Florida
- Location (city): Specify the city where your organization is registered. For example, Miami
- Organization name (company): If you bought a Business Validation or an Extended Validation Certificate, type the legal name of your company (e.g. GPI Holding LLC) For Domain Validation (DV), enter your full name, or your website’s name
- Organization department or division name: If you’re not sure, type “IT” or “Web Administration”. For a DV certificate, enter NA (not available)
- Domain Name: Submit the FQDN (Fully Qualified Domain Name) of the website you want to encrypt. For example, ssldragon.com
Note: If you have a Wildcard certificate, the domain name must start with an asterisk. For example, *.ssldragon.com
- Email: Provide a valid email address so that the CA can verify the domain ownership
- Double-check the information you’ve just provided, then click Request. Plesk will now generate your CSR code and private key
- To view both codes, on the next page, from the list of certificates click on your certificate name
- Now, you can copy the CSR code (including the —–BEGIN CERTIFICATE REQUEST—– and —–END CERTIFICATE REQUEST—– tags) and use it during your SSL order process. As for the private key, you will use it later during the SSL configuration.
Install an SSL Certificate on Plesk Onyx
- Log into your Plesk account
- If you’re a Server Administrator or Reseller, navigate to Domains section, select the domain name you want to protect, and click SSL/TLS Certificates. If you have a default customer account, go to Websites and Domains, choose the relevant domain name, then click on SSL/TLS Certificates. Further steps are identical for both groups of users
- Click on the SSL certificate name for which you generated the CSR code and private key
- On the next page, you need to upload your certificate files. Here you have two options: upload the files directly, or copy the files’ contents in the corresponding fields and upload them in text format. No matter what option you pick, make sure you have all the necessary files. You will the SSL certificate (.crt) and the optional CA certificate (.ca-bundle) for older browsers’ versions. If you didn’t generate the CSR in Plesk, you will also need the private key (.key) file. When you have finished, click Upload Certificate
- You will receive a message about the successful installation. Next, you have to assign your SSL certificate to the hosting services
- Click on Hosting Settings from the main dashboard of your domain, and from the Certificate drop-down list, select your SSL certificate. Click OK
- Another message will confirm the successful SSL configuration
- To force the HTTPS connection, return to the previous step (6), tick the Permanent SEO-safe 301 redirect box, then Apply > OK.
That’s it! Now, all you have to do is test your SSL certificate for potential errors and vulnerabilities. Use these excellent SSL tools to get instant status reports for your certificate.
Plesk history and versions
Plesk is a popular, commercial web hosting platform for Linux and Windows servers. It offers a full suite of managing tools for server administrators, hosting resellers, and end customers. Plesk has its origins in the Siberian city of Novosibirsk. It went live for the first time in 2001. From 2003 to 2015 Plesk was part of SWSoft (later Parallels). Plesk became an independent entity in 2015 until Oakley Capital acquired it for $105 million in 2017.
As of now, only two Plesk releases receive updates and support:
- Plesk Onyx – released on October 11, 2016, it has extended support until October 11, 2020, while its EOL (End of Life) cycle is on April 20, 2021.
- Plesk 12 – released on June 16, 2014, it has extended support until June 16, 2018, while its EOL cycle is on January 1, 2019.
Where to buy an SSL Certificate for Plesk?
SSL Dragon is the only SSL vendor you’ll ever need to know. We’ve built strong partnerships with the best Certificate Authorities in the industry and offer jaw-dropping prices across the entire range of SSL products. All our certificates are compatible with Plesk. Whether you want to protect a personal blog or your corporate email correspondence, we’ve got you covered. Below are the types of SSL certificates available at SSL Dragon:
- Domain Validation
- Business Validation
- Extended Validation
- Code Signing
- IP Address
You can find the perfect SSL Certificate for your project and budget with the help of our exclusive SSL tools. The SSL Wizard offers a quick and precise way to determine the right SSL for you, while the Advanced Certificate Filter allows you to sort and compare different certificates by price, validation, and features.
If you find any inaccuracies, or you have details to add to these SSL installation instructions, please feel free to send us your feedback at [email protected]. Your input would be greatly appreciated! Thank you.