• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Issue SSL certificate to secure Plesk IP address issue (Not Lets Encrypt)

Matt63

New Pleskian
Server operating system version
Ubuntu 22.04.4 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.60 Update #1,
Hi there,

I need to secure the public IP address for the Plesk portal (requested by a client). I have purchased a specialist SSL certificate that can be used to secure IP addresses. The site I have running on the hosting has its own Lets Encrypt certificate on it.

I have installed the new certificate on plesk and it is showing in the list of available certificates.
I have then gone to 'IP addresses', selected the required public IP address and selected the new certificate in the dropdown.

When I go then access the IP address at HTTPS, it still gives me the usual security warning and in the browser info, it's still trying to use the old free certificate.

Has anyone got any ideas as to what could cause this and what deep, dark setting I need to change to get it to realise there's a nice shiny new SSL sitting there!? :)

Thanks,
Matt
 
Hi. They still display the certificate that is securing the domain URL, not the IP address. That's the strange thing
 
Just to be sure is the certificate selected as the "Certificate for securing Plesk" in Tools & Settings > SSL/TLS Certificates? As shown in this example image.

Screenshot_2019-03-26_SSL_TLS_Certificates_-_Plesk_Onyx_17_8_11_1___1_.png
 
Back
Top