• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • 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 Can I automate SSL renewal using a custom PFX/CRT certificate (Not Let's Encrypt)?

peteeeeeee

New Pleskian
Server operating system version
CentOS Linux 7.9
Plesk version and microupdate number
Plesk Obsidian 18.0.77 Update #5
With the industry moving toward much shorter SSL lifespans, is there a way to automate this process for a domain?

Currently, my manual workflow is:
  1. Receive a .pfx file from the client.
  2. Extract the .crt and .key files using a password.
  3. Upload and update the certificate via Plesk > Subscription > Domain > SSL/TLS Certificates.
Any advice or example scripts would be greatly appreciated.
Thanks!
 
If your certificate provider supports the ACME protocol, you'd be able to use the ACME extension to automate to whole process (requesting, issuing, validation, installation).

If not, you'll have to get creative and write your own script. For which you can use the Plesk CLI certificate utility alongside with OpenSSL to handle pfx file.
 
Last edited:
Back
Top