• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

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