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

Question SSLs shortening validity period

Dave W

Regular Pleskian
Server operating system version
Alma 9.2
Plesk version and microupdate number
18.0.56 #2.
Greetz,
Just wondering what everyones plans are for SSLs shortening validity periods?
We use Sectigo but the Sectigo extension doesnt seem to perform ACME style validation

Just wanted to open the discussion.
D.
 
Hi, @Dave W . Support for short-lived certificates was introduced in Sectigo SSL version 1.5.0 (December last year). The methods that will be used are AutoReplaceSSL and AutoRevokeSSL.
 
Last edited:
No, at this point, there's no option to configure a Sectigo reseller account within the extension. When the ACME extension is released, you will be able to issue Sectigo certificate through the Sectigo ACME directory. Our team's aim is to deliver the extension by the end of March.
 
Hi, @D3nnis3n . When you navigate to the SSL installation page, is the "Recommended" radio button on? If yes, please slide it off and you should be able to see it.
 
Thank you for the feedback. We understand that the UX is not ideal, but given the urgency of adapting to the SSL requirement changes our team prioritized delivering the extension as quickly as possible. There is already an initiative for improving the placement of the ACME SSL option for a more intuitive user experience. These changes will be introduced in the upcoming releases.
 
Just trying to understand the Sectigo extension a little better.
When a user purchases an SSL via the extension the commercial transaction is processed by Sectigo or Plesk?
 
When a user purchases an SSL via the extension the commercial transaction is processed by Sectigo or Plesk?
When a customer buys a Sectigo SSL certificate through the Sectigo SSL extension, the purchase is handled by Plesk: the extension sends the customer to the Plesk online store, and payment goes through Plesk. Plesk then places the order with Sectigo as a Sectigo partner. Sectigo acts only as the Certificate Authority: it validates the domain or organization and issues the certificate. Billing, payment and refund questions go to Plesk. Validation questions for OV/EV certificates, such as document checks or callbacks, go through the Sectigo dashboard.
 
Back
Top