HOW-TO - Not get Plesk Certificate Error or get rid off "This Connection is Untrusted" message.
It is more and more frustrating when customers call to complain about the control panel - PLESK, provided with your hosting service does not work. They are returned a screen with the following message "This Connection is Untrusted" (in Firefox) or " There is a problem with this website's security certificate. " (in Internet Explorer). In most of the cases they turn off the browser in order to avoid doing something stupid, without reading the message, knowing it is UNTRUSTED or NOT SECURED. Magical words that scare them.
On the PLESK forums and other types of forums as well, users haven't really found solutions. A certificate may be purchased from different providers, including cheap ones, but they tend to solve the problem only partially. Usually a "wildcard" certificate is needed, i.e. *.domain.com to get rid of the problem and a secred URL may be purchased by the customer. Yes, but a wildcard certificate costs somewhere around 199USD (the lowest price we have come across) and up to 495USD (or maybe more). Yes, the price would be justified in case we would be doing ecommerce, where having a trusted certificate is vital and important. But in case you'd like to use this certificate just so that your customers wouldn't be scared off that page, the price is not at all justified.
And here is the solution, not a perfect one, but still a good one to avoid the obstacles. What if, you as a hosting company, would sign a certificate, that would be valid and we ra esure that your customers who trust you, wouldn't mind having a Certificate signed by the X Hosting Company instead of Comodo or Verisign. And this is totally doable. We offer you a FREE tutorial and a small shell script (in case you need it) for 39USD/lifetime, a very low price considering that a wildcard certificae would cost you 200USD or more. But be aware that our solution will work only in PLESK, on port 8443, and we do not recommend using it as an ecommerce certificate or any other similar site, even if it is possible.
If we have made you interested, read the below article and you will find extra information and in case you need the SHELL file in 10 minutes, ORDER NOW.
We need just to go through a process of installing and configuring a Certificate Authority (CA) System to use with Plesk for Server Certification and Secure website access. The role of this application is to generate a CA system to be used internally, with the possibility to publish the CA public keys in order to recognize the certificates issued by this CA.
The process works by installing the CA public keys in the browser of the clients who access the secured services. This way, the browser will recognize, using the CA public key, the certificate of the website that was signed by the CA private key. Of course, a general PKI system can be much more complex, including intermediate authorities signed by a Root CA or multiple PKI schemes. We shall stick to a simple authority that signs certificates for use by Plesk.
What is a digital certificate?
A digital certificate is an electronic document that serves to prove the identity of a website or person when using secured transactions. We shall stick to the Server Certificates in the application. A certificate has two main roles: to assure encryption between the entities communicating and to prove the identity of an entity. A digital certificate also contains a public key which, amongst other things, is used to encrypt the data from the client to the server. The server can decrypt the data using the private key from witch this certificate's public key was generated.
Example of a certificate:
What is a secured website?
The Internet contains a lot of interesting things, from presentation websites, news websites, social networks, personal home pages, blogs, to special portals, e-commerce websites, e-banking or special access pages containing sensitive information.
The HTTP protocol in its base form is the main protocol used on the World Wide Web to transfer information across computer networks. Unfortunately, the base form transfers information in plain form, meaning that the bytes that are transferred can be intercepted by a third party with access to a router or cable or any other information carrying method. This third party is able to partially reconstruct the initial data and thus can read the sensitive data that was transferred between the communicating parties.
In order to avoid this kind of eavesdropping, encryption must be used. Suppose we have two entities that wish to communicate securely. One must encrypt the data with a key that the other can decrypt with the same key or with the corresponding key, depending on the security scheme used. This way, even if someone eavesdrops, they will get a non-sense stream of data. Without the right key, they can't decrypt the stream thus they can't read the sensitive data.
What is the trust relationship?
Now that we have defined what is a secure communication and what are the certificates, now we move on to the trust part of this scheme. In a Public Key Infrastructure (P.K.I.) system we have 3 entities: 2 communicating entities and an Authority which acts an intermediary. Both entities that wish to communicate securely trust the Certification Authority (C.A.) That is why, the Server has it's certificate signed by the Authority, Authority which is trusted by the connecting client.
How can I generate this key?
There are two methods of doing so, a manual one that requires advanced Linux knowledge and an automated one, the script we offer that may be ordered through this link for only 39USD.
The program has 2 main operations (also called subroutines). You will need to have OpenSSL on your server.
- The PKI Installation Subroutine: which installs a PKI system on the system: directory structure and a Root CA key and certificate
- The Signing Subroutine: which is used to sign any Certificate Signing Request (CSR) with the Root CA private key.
The PKI Installation Subroutine
This portion of the program deals with installing the CA structure and the CA's private key and certificate.
Note that the CA certificate is a self-signed one, do NOT use it for server operations or other purpose beside signing other certificates.
- You need root privileges to run these operations.
- You need to have OpenSSL installed on your system.
The Signing Subroutine
This portion of the program deals with the signing of already existing CSR (Certificate Signing Request).Of course, the Script is more complex, giving you the posibility to sign any csr. This tutorial only deals with the Plesk Certificate Signing.
Practical Guide in a few step
This is a 10 step practical guide to a step-by-step installation. This guide will “install” a PKI system onto a machine and sign a CSR to obtain a Server Certificate.
1. Login to your system
2. Make sure you are root (“su” if you have to)
3. Install this script in /root folder and give execution permissions.
4. Launch this script with -ca parameter.
5. Fill in the fields (if you do not understand something please use the previous chapter)
6. Create a server CSR on the Plesk Portal
7. Copy the server CSR in /root/
8. Launch this script with -s parameter.
9. Copy the contents of the newly created CRT (Certificate) into the Plesk Portal (at the certificate's section) or upload the certificate file.
10. That's all !
Tell your client how to use it.
Now that everything is installed, we need to let the customer know how to acess these pages so that everything is OK. First of all, we need to place the rootca.crt certificate on ur domain, http://www.domain.com/rootca.crt that is publicly available.Below you have 3 different and well-known setup methods:
- Step 1: Navigate with a bowser to http://www.domain.com/rootca.crt
- Step 2: Depending on the browser you are using , you will be returned the following windows:
- Step 1 (and the only one): Mark all three checkboxes and click OK
- Step 1: When the download window is launched, select OPEN
- Step 2: In the certificate window you will see that it is not yet recognised, access "Install Certificate"
- Step 3: Select the repository where the certificate will be stored: access Browse, and then "Trusted Root Certificates"
- Step 4: Summary window, confirm using Finish
- Step 5: Additional security confirmation, access "YES"
- Step 1 (and the only one): Access OPEN, and the rest of the procedures are the same as in Internet Explorer
In our welcome message we usually send out to our customers (each company sends out such a mail) we includ a line for the PLESK access, ex: Before accessing the control panel, follow this link http://www.domain.com/rootca.crt and follow the steps on the screen. You should also provide a link to the manual that you receive from us in Word and PDF format so that you can personalise them (only on script command). In Firefox it is simple, the link is followed and click OK, but in Internet Explorer it is harder, the certificate needs to be imported (in case the customers works with Vista or Windows 7), but everything is covered in the documentation we have provided.
It is not a perfect solution, it has its flaws that we have to live with due to the security excess. The only other solution is to purchase a recognised certificate that will cost 200USD or even more. You decide.
HOW-TO setup Plesk with Samba Share and OpenVPN on CentOS - 15 April 2010
HOW-TO configure PLESK with NGinx (proxy reverse) - 15 March 2010
HOW-TO install ffmpeg, Mplayer, mencoder,FLVtool2 and Yamdi on Plesk Linux based server - 25 September 2009
HOW-TO restart automatically on Linux Kernel Panic if hanging on boot - 23 September 2009
Web Site hacked, iframe inserted, where to start? - 10 August 2009
Spam blacklist unlisting from sorbs.net - 31 July 2009
How to find out PLESK admin password? - 12 July 2009
Plesk 9.2.x - Postfix SMTP authentication error - 16 May 2009
Automated Remote FTP Backup shell script - 26 October 2008