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

Shared SSL Question

TimU

New Pleskian
Hello.

I have a Plesk 10.4 build RHEL server for a shared web server, and I have a separate domain/space on it called secureX.mydomain.com (where "X" is a number and "mydomain" is a proper name, not the example)

Customers using their own subscriptions/domains (such as "customerdomain.com") want to be able to use this secure SSL. As it stands, when they are on the shared IP it works but gives out the expected certificate errors.

I am looking for a way to make the SSL segment use the secureX so the SSL certificate can match the domain.

Is this possible in Plesk 10.x? We have some older Plesk servers running this format but I was not present when they were set up and thus am not sure how to go about doing this.

Thanks,
 
Back
Top