• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Plesk SSL

It definitely *is* possible, we have our control panels configured this way.

We originally had this set up back when we were using Plesk 7.5; but were initially told that it wasn't possible due to the Virtuozzo integration on Plesk 8.

However, the techs at the datacentre did manage to work out a way to achieve it and it all works very nicely for us now.

I'll ask them to explain how they managed it...
 
I quizzed the tech about it and in his own words, "To be honest, I do not remember. I know there is a setting in the management console for it."

Sorry I couldn't offer more insight on this one, but hopefully this might point you in the right direction.
 
Originally posted by jefwic
Hello,

I currently have a domain with an SSL cert (https://www.mydomain.com). I access Plesk via https://www.mydomain.com:8443 - is it possible it can use my main sites SSL cert rather than the one issued to 'plesk'?

Thanks.
For this you need, first of all add certificate into Server -> Certificates section, after that check it there and click on Setup. For more information you can read Plesk documentation here:
http://download1.swsoft.com/Plesk/Plesk8.1/Doc/plesk-8.1-unix-administrators-guide/index.htm -> Configuring Your Control Panel -> Securing Your Control Panel
 
The link you've provided explains how to install a server-wide certificate in Plesk (I was assuming jefwic had already done this, so well spotted!)

Unfortunately it doesn't cover how to replace the default certificate with your own purchased certificate for the control panel on port 8443. I'm also interested to know how to do this given that our tech can't recall what he did to get ours working.
 
Currently my Plesk uses it's own certificate that I bought.

All I did was install the certificate from Server >> Certificates and then set it as the default certificate for the IP for the domain.

See as I have it so that clients type domain.com/plesk to get to plesk (This redirects to a subdomain on my main domain with :8443 on the end it means all customers get a valid SSL certificate without it being on every single domain as the default.

Does that make sense? I'm not so great with explaining.
 
Its also written in the onlinehelp:

Install the cert in the Servercerts.

Mark the cert and hit the SETUP button.

Ready.

HTH
 
Back
Top