• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question 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