Certinite issues the certificate, publishes the validation record into Plesk's DNS zone, installs it and binds it to the site — without touching the server.
Plesk Obsidian hosts websites for agencies, resellers and in-house teams across Linux and Windows, and each subscription manages its own certificate store. The bundled Let's Encrypt extension handles the straightforward path, but it only speaks to one certificate authority and leaves you with no consolidated view of what expires when across a fleet of servers.
Installing a certificate by hand in Plesk means uploading four separate pieces — the request, the private key, the certificate and the CA bundle — into the correct subscription repository and then binding the result to the right site. Repeat that across every domain, every renewal cycle, and the probability of an outage stops being theoretical.
Why Plesk SSL Automation with Certinite?
Certinite integrates with Plesk over its management APIs. Reachability and credentials are verified through the REST API on port 8443, while certificate installation goes through the XML-RPC interface: certificate.install adds the material to the subscription repository and site.set binds it to the website and enables SSL. Certinite generates the certificate request server-side, so all four parts Plesk expects are always present.
Plesk offers no remote file-write API, so HTTP-01 validation is impossible from outside the server. Certinite works with that constraint rather than around it: because Plesk already hosts the DNS zone, the ACME DNS-01 TXT record is published straight into it through the panel and retracted after issuance. Validation is therefore fully automatic — you never publish a record by hand, not at issuance and not at renewal.
To bring every Plesk server under one certificate lifecycle, issue free and premium certificates through the same pipeline, and let renewals validate themselves through the panel's own DNS, start using Certinite's Plesk automation today.