Automating TLS on Plesk
Connect a subscription, discover bindings, deploy a replacement certificate, reload the vhost, keep a rollback copy.
Answer first
Connect a subscription, discover bindings, deploy a replacement certificate, reload the vhost, keep a rollback copy.
How the platform treats it
Use scoped API tokens. Do not store the server admin password in the app if a token exists.
Operational checklist
Confirm the hostname or product is in the correct organization. Prefer scoped credentials. Record the audit event. Subscribe to the matching webhook. Do not enable production ACME from a guide.
Failure modes
Expect DNS propagation delay, CA rate limits, and expired tokens. The API returns stable error codes rather than HTML error pages. Retry with backoff; do not loop validate calls from a browser tab.
Related inventory
After a successful change, inspect certificates, orders, deployments and billing documents. Unexpected Certificate Transparency entries are observations, not compromise claims.
Sources and limits
This guide describes software behavior. It is not legal, tax or CA-policy advice. Provider capabilities are cited from official documentation and fact-checked in admin content. Fact-check date: 2026-09-19.