• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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