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

Cross-linking of SSL certificate repositories

D

djten

Guest
I am managing a Linux web server with Plesk 8.2.1. There are about 65 shared domains on this server. I have obtained and set up dedicated IP addresses and SSL certificates for 4 those domains so far, with no problems. The fifth and latest SSL certificate, however, has been a problem.

For this new domain, which I will call here "domain-one," I had once again arranged for another dedicated IP address and certificate. I added the certificate under domain-one's setup. Once the certificate setup was completed, I went to domain-one's setup page, then selected the dedicated IP address I had previously obtained and set up for domain-one. When I went to select the certificate I had set up for domain-one, among the other certificates (previously obtained, as I mentioned above) that show up in the drop-down was the one I wanted. However, while entry had the name of the certificate "Domain-one," the name was followed by "(repository of domain domain-two)".

I thought perhaps I had mistakenly added the certificate under domain-two, so I removed the certificate and started over. This did not help. Going back and forth, I finally realized that any time I create a certificate under domain-one, it shows up in the certificate repository of domain-one and domain-two. And vice-versa: any time I create a certificate under domain-two, it shows up under both domain-two and domain-one. There seem to be some wires crossed here. Domain-one is pretty new. Domain-two has been on the server for a long time, I have not had to change any settings for domain-two in a long time, and domain-two does not have, nor ever has had an SSL certificate set up.

Has anyone else encountered this particular problem, or know of a fix for it?
 
Back
Top