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

Resolved Securing the Plesk control panel with two access URLs

macadia

Basic Pleskian
Server operating system version
AlmaLinux 9.8
Plesk version and microupdate number
18.0.81 #4
Hello, this might be a silly question, but I’d like to be able to secure the Plesk control panel with two different URLs. Let me explain:

My hosting provider has given me cloud.xxxx.tld:8443 as the URL to access Plesk, and it’s perfectly secure with an SSL certificate

However, as my server has two resellers, I’d like each reseller to be able to log in via cloud.yyyy.tld:8443 or cloud.zzzz.tld:8443, and for these two URLs not to trigger an SSL warning…

Is this possible? Do I need to create subscriptions? Is there an easier way that doesn’t involve using subscriptions? Although my control panel is WebHost, I’m not too worried about it, but I’d prefer not to have subscriptions just for access to Plesk.

Thank you, and apologies for the translation (it was done using Deepl)

Translated with DeepL.com (free version)
 
Back
Top