• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question How to set certificate to "Not Selected" by command line client?

Bitpalast

Plesk addicted!
Plesk Guru
Forwarded to devs - Let's Encrypt still causing issues with web server configuration on updating certificates has not yet been fixed. We need a solution for it, so we'd like to add an auto-repair to our watchdog scripts doing this:

1) Either set the certificate of the affected subscription to "Not Selected" or to "<server_certificate>" (where <server_certificate> is the name of the host's default certificate. Neither one can be done by
# plesk bin subscription -u <domain> -certificate-name "<certificate_name>"
The command returns "Unable to find certificate" if the server certificate name is used, and it is not for the reason that the server certificate has a specific name. It seems to only accept certificates inside the domain's repository. And there is no way to set "not selected".

2) Then remove the faulty certificate and run the Let's Encrypt extension again to re-recreate a certificate as that will then hopefully be named correctly.

3) Reconfigure the domain web server settings.

Problem: Step (1) does not work. There does not seem to be a way to set the SSL selection of a domain to "Not selected". But how is the GUI doing this when the user makes that choice? There has got to be an undocumented parameter to a client command. Does anyone know it?
 
Back
Top