Skip to Content
Open Beta — managed Kubernetes, DNS & more are live.
📜

TLS certificates

Updated 2026-11-20
On this page

TLS certificates

Order and manage publicly trusted TLS certificates so your sites and services are served over HTTPS. Certificates are issued automatically through ACME and renew before they expire.

Certificates are issued with the ACME protocol (Let's Encrypt) using a DNS-01 challenge. Because the challenge is answered in DNS, the domain must be delegated to Patrii Cloud DNS: the console checks your zone's delegation before it lets you order, and issuance fails if the nameservers are not pointed at the platform.

A single certificate can cover several names using Subject Alternative Names (SANs), as long as every name belongs to the selected zone. Once issued, the certificate is stored alongside your secrets and can be attached to services such as load balancers. Renewal is automatic; you can also renew, extend or delete a certificate manually.

Screenshot — The ACME Certificates drawer listing certificates with their status, environment and days until expiry
The ACME Certificates drawer listing certificates with their status, environment and days until expiry

Key concepts

ACME — The automated protocol used to prove domain control and obtain a certificate without manual steps.

DNS-01 challenge — A validation method that proves control by publishing a record in your DNS zone; requires the domain to be delegated to Patrii Cloud DNS.

SAN — Subject Alternative Name; lets one certificate cover multiple domain names.

Environment — Production issues browser-trusted certificates; staging issues test certificates for trying the flow without hitting rate limits.

Renewal cooldown — A short window after a renewal during which another renewal is throttled; can be forced if needed.

Before you start

  • A DNS zone hosted on Patrii Cloud DNS for the domain.
  • The domain's nameservers delegated to the platform at your registrar.
  • The exact domain names you want on the certificate.

Step by step

  1. Open the certificate manager

    Go to Security and open Certificates (the ACME Certificates view). Choose Order New to start.

    Screenshot — The Certificates list with the Order New button
    The Certificates list with the Order New button
  2. Select the DNS zone

    Pick the zone that holds your domain. The console runs a delegation check and warns you if some or all nameservers are not yet pointed at Patrii Cloud DNS.

    Screenshot — The order form with the green delegation-OK notice
    The order form with the green delegation-OK notice
  3. Add the domains

    Enter one or more names to include as SANs. Every name must belong to the selected zone; the bare domain is suggested for you.

  4. Choose the environment

    Leave it on Production for a browser-trusted certificate, or pick Staging to rehearse the flow without consuming production rate limits.

  5. Order and let validation run
    • Submit the order. The certificate moves through pending and validating while the DNS-01 challenge is answered automatically.
    • When it reaches issued, it is ready to attach to a service.
    Screenshot — A certificate row showing the ISSUED status and days until expiry
    A certificate row showing the ISSUED status and days until expiry
  6. Attach, renew or extend
    • Attach the issued certificate to a load balancer or other service that terminates TLS.
    • Renewal happens automatically before expiry; use Renew to do it early, or Add Domains to re-issue with extra names.

Examples

Order a multi-domain certificate (Patrii CLI)
patrii certificate order \
  --domain example.com \
  --domain www.example.com
# add --staging for an untrusted test certificate first
Renew an existing certificate
patrii certificate list
patrii certificate renew <certificate-id>
Order a certificate with Terraform
resource "patrii_certificate" "web" {
  zone_id     = patrii_dns_zone.main.id
  domains     = ["example.com", "www.example.com"]
  environment = "production"
}

Limits & specifications

Certificate lifecycle states:

StatusMeaning
pendingThe order was accepted and is queued for validation.
validatingThe DNS-01 challenge is being answered.
issuedThe certificate is valid and ready to use.
renewingAn automatic or manual renewal is in progress.
failedValidation or issuance did not complete; check delegation and retry.
expiredThe certificate passed its validity window without a successful renewal.

Best practices

  • Confirm the delegation check is green before ordering to avoid a failed challenge.
  • Use Staging first for a new or unusual setup so you do not spend production rate limits on mistakes.
  • Put every hostname a service answers on one certificate with SANs rather than juggling several certificates.
  • Leave automatic renewal on and watch the days-to-expiry column for anything stuck.
  • Remove certificates you no longer serve so the list reflects reality.

FAQ

Why did my certificate fail validation?
The most common cause is DNS delegation. The DNS-01 challenge needs your domain's nameservers pointed at Patrii Cloud DNS. Fix the delegation at your registrar until the console's check is green, then retry.
It says a renewal cooldown is active. What now?
A renewal was attempted recently and further renewals are briefly throttled. Automatic renewal will still happen on schedule; if you must renew now, confirm the Force Renew prompt.
Can one certificate cover several subdomains?
Yes. Add each name as a SAN when ordering, or use Add Domains on an issued certificate to re-issue it with the extra names. All names must be in the same DNS zone.

Learn more

Everything you can do here in the console is also available through the Patrii Cloud API for automation and scripting.

Was this article helpful?
Thank you for your feedback. Still stuck? Contact us