• 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 2 public ip for domains

vmcastro

New Pleskian
Hi, i have 2 public ip(diferent provideer) one is dedicated and one is shared, but when use the shared ip for 1 domain, i have

SSL_ERROR_BAD_CERT_DOMAIN , because it´s use the cert for dedicated ip and not cert of my shared ip, what can i do to use 2 ips of diferent provider​

​


thanks a lot
 
What happens when you navigate to the Hosting Setting for your domain in Plesk and select another certificate (or no certificate). Does that solve your issue?
Schermafbeelding 2021-07-06 om 17.21.48.png
 
Back
Top