• 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.

How do I secure control panel access for customers?

P

purple2

Guest
Hello,

Our Plesk server has one default certificate that works fine when accessing the control panel using the servername. If a customer wants to provide control panel access to their customers using their own domain name, how can you secure this with a certificate?

For example, they want to be able to login to the control panel through https://theirname.com:8443/ and not https://servername.com:8443/.

At the moment, if they try to do this they will encounter an error in their web browser stating that the certificate doesn't match the hostname.

Many thanks,

Richard
 
Back
Top