Facebook
Twitter-
Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
-
The BIND DNS server has already been deprecated and removed from Plesk for Windows.
If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release. -
The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
SSL Certificate for Control Panel
- Thread starter KrazyBob
- Start date
F
faris
Guest
Any valid SSL certificate will do, as long as it is designed to protect web pages (i.e NOT "Code Signing Certificates" or "Email validation Certificates").
e.g. Visit: http://www.c1-domains.com -> click on SSL certificates -> Select See all Certificates:
Any of those three types will work, even the cheapest "Standard SSL Certificate".
**** Disclosure: We generate income from www.c1-domains.com. Shop around to see what the alternatives are and what they cost. There are literally 100s of companies and resellers offering SSL certificates and many will be cheaper than ours.
Essentially, in Plesk (Servers -> Certificates) you Add New Certificate, fill in the form at the top, and click on the Request button. *** You must use the full domain, if necessary including the www in the "Domain Name" box. For example if your customers visit https://www.myhostingcompanyname.com:8443 to get to Plesk then you should enter www.myhostingcompanyname.com in the Domain Name box ***. Also be sure to select 1024 bits not 512 or 2048.
Doing the above generates a CSR ( = Certificate Signing Request, I think) which is a block of gibberish text. You then copy it and then past into the appropriate box on the SSL certificate signup web page during the signup process. You pay your money, then you get two things back: The certificate itself and usually what's known as a "CA Certificate".
Back in Plesk, go to the certificate you just created and paste these things into the appropriate boxes and click on Send Text
All being well you should get no errors, and the certificate should show up in the list of certificates (Server -> Certificates) with all its parts (CA, Certificate) shown as being present (gold coloured icons rather then grayed out ones). Put a check in the box next to it, and click on Secure Control Panel just above the list.
You may need to restart Plesk (service psa restart) in order to get the new certificate working.
You can see if it is the right one if get no errors when logging in. If you still get errors, in Internet Explorer click on File -> Properties -> click on Certificate to see what's happening (and similarly for FF or Safari or whatever)
Hope this helps.
Faris.
e.g. Visit: http://www.c1-domains.com -> click on SSL certificates -> Select See all Certificates:
Any of those three types will work, even the cheapest "Standard SSL Certificate".
**** Disclosure: We generate income from www.c1-domains.com. Shop around to see what the alternatives are and what they cost. There are literally 100s of companies and resellers offering SSL certificates and many will be cheaper than ours.
Essentially, in Plesk (Servers -> Certificates) you Add New Certificate, fill in the form at the top, and click on the Request button. *** You must use the full domain, if necessary including the www in the "Domain Name" box. For example if your customers visit https://www.myhostingcompanyname.com:8443 to get to Plesk then you should enter www.myhostingcompanyname.com in the Domain Name box ***. Also be sure to select 1024 bits not 512 or 2048.
Doing the above generates a CSR ( = Certificate Signing Request, I think) which is a block of gibberish text. You then copy it and then past into the appropriate box on the SSL certificate signup web page during the signup process. You pay your money, then you get two things back: The certificate itself and usually what's known as a "CA Certificate".
Back in Plesk, go to the certificate you just created and paste these things into the appropriate boxes and click on Send Text
All being well you should get no errors, and the certificate should show up in the list of certificates (Server -> Certificates) with all its parts (CA, Certificate) shown as being present (gold coloured icons rather then grayed out ones). Put a check in the box next to it, and click on Secure Control Panel just above the list.
You may need to restart Plesk (service psa restart) in order to get the new certificate working.
You can see if it is the right one if get no errors when logging in. If you still get errors, in Internet Explorer click on File -> Properties -> click on Certificate to see what's happening (and similarly for FF or Safari or whatever)
Hope this helps.
Faris.
KrazyBob
Regular Pleskian
I should have better defined the question. I own many Plesk servers and since IE7, IE8 and Firefox users have complained about the self-signed certificate. I can add a control panel certificate but there are three ways to access the CP: by IP, by host name, or by web site name :8443. Do I need a shared certificate, or other?
F
faris
Guest
If you have many servers, the best option is a wildcard SSL certificate.
If each server has a hostname like [something].yourhostingcompanyname.com then buy a wildcard certificate for yourhostingcompanyname.com and installed it on all your servers.
Then ask your customers to use https://[something].yourhostingcompanyname.com:8443
Or you could buy individual certificates for the domain name of each Plesk box.
They will still get errors if they try to access plesk by IP or by using their own domain names though.
Faris.
If each server has a hostname like [something].yourhostingcompanyname.com then buy a wildcard certificate for yourhostingcompanyname.com and installed it on all your servers.
Then ask your customers to use https://[something].yourhostingcompanyname.com:8443
Or you could buy individual certificates for the domain name of each Plesk box.
They will still get errors if they try to access plesk by IP or by using their own domain names though.
Faris.
S
SeanJ
Guest
Keep in mind that unless you can apply the Virtuozzo node 'fix' by Parallels, you may not be able to replace the root server's SSL.
We've run into that issue with Media Temple, and as they are unwilling to apply the fix from parallels to the Virtuozzo node, logins are still processed by the self-signed SSL and the SSL for the VDS can be replaced.
Sean
We've run into that issue with Media Temple, and as they are unwilling to apply the fix from parallels to the Virtuozzo node, logins are still processed by the self-signed SSL and the SSL for the VDS can be replaced.
Sean
64bithost.com
Regular Pleskian
Section Three is bad practice
Each domain should have it's own SSL cert if requested. Otherwise just issue the domain name as
https://www.theirwebsite.com:8443
login:
password:
click on the "no"
Similar threads
