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

Resolved Installing an SSL via the API requires a CSR, whereas the UI and CLI don't require it

dg11

New Pleskian
Installing Certificates
upload_2019-1-25_13-38-34.png

This is a huge problem for us when migrating SSL certificates in to Plesk, as we don't store the CSR once the certificate has been issued.

Currently the dirty work around is to establish an SSH connection and use the certificate utility to install the SSL without an CSR, but that really shouldn't be necessary when there's an API.

Should I raise this as a bug in the reports forum? It's more like the specification of this API feature was initially incorrect.

To be in line with the UI and certificate CLI utility, the API certificate/install/csr node should be changed from 'required' to 'optional'.
 
ahhh it would be nice if the documentation mentioned that the csr node can be a blank string.

Closing as resolved.
 
Back
Top