General settings reference
Every field on Settings → General, grouped exactly as on the page. Settings are stored as a single versioned document — the form uses optimistic concurrency, so if another admin saved while you were editing, your save is rejected with a conflict and the page reloads the current values.
Approval requirements
Approval is no longer set here: each project has its own approval policy under Settings → Approvals — which operators (all, or selected users and groups) need approval for each operation. See Approval workflow. Approval values saved here by an earlier version are ignored.
Certificate defaults
Defaults applied to new certificates; each can be overridden per certificate at issue time.
| Field | What it does | Range | Default |
|---|---|---|---|
default_renewal_threshold_days | Days before expiration at which a certificate becomes eligible for automatic renewal. | 1–90 days | 30 |
default_key_type | Default key algorithm for new certificates. ECDSA is faster and smaller; RSA has broader legacy compatibility. | ECDSA-P256, ECDSA-P384, RSA-2048, RSA-3072, RSA-4096 | ECDSA-P256 |
default_key_rotation_policy | Reuse keeps the same private key across renewals; Rotate generates a fresh key each time. | reuse / rotate | reuse |
default_auto_renew | Whether new certificates are automatically renewed before expiration. | on / off | on |
cert_history_max_versions | How many certificate versions (current + historical) to retain per certificate — labelled History Versions in the UI. Older versions and any private key no longer referenced by a retained version are pruned automatically at every artifact write (issuance, renewal, and certificate import alike — not only at renewal). A version that a distribution still references is pinned and never pruned. 0 = the default (10); -1 = unlimited. | -1–100 | 10 |
See Renewal for how the renewal sweep uses the threshold, and Download a certificate for browsing/downloading retained versions.
Expiry alerts
On the same card. They decide when a certificate raises the Expiring Soon notification — see When an expiry alert is raised.
| Field | What it does | Range | Default |
|---|---|---|---|
expiry_alert_days | Expiry Alerts — the lead times, in days before expiry, at which a certificate that is not renewed automatically (imported, auto-renew off, manual DNS) alerts, once per value. A value longer than a third of a certificate's lifetime is shortened to that third. Empty = the default. | up to 6 distinct values, 1–90 | 30, 14, 7, 1 |
expiry_renewal_grace_hours | Overdue Renewal Grace — how long past its planned renewal an automatically renewed certificate may stay unrenewed before it alerts as overdue. 0 = the default. | 1–168 h | 24 |
Every certificate also alerts once a day in its last 3 days (not configurable).
The same lead times and final days apply to discovered certificates that CertAutoPilot does not manage (discovery.cert_expiring, see Findings → Notifications).
Runtime limits
These settings directly affect system performance and resource usage. The page shows the same warning.
| Field | What it does | Range | Default |
|---|---|---|---|
renewal_check_interval_minutes | How often the scheduler scans for certificates that need renewal. Lower values detect expiring certs faster but increase database load. | 5–1440 min | 60 |
domain_check_interval_minutes | How often tracked domains are checked for certificate changes or expiration on remote endpoints. | 5–1440 min | 60 |
domain_check_batch_size | Number of domains checked concurrently per scan cycle. | 1–500 | 50 |
default_max_job_attempts | Retry attempts for failed jobs before they are marked permanently failed. | 1–10 | 3 |
distribution_execution_timeout_minutes | Maximum time a distribution job may run across all its targets; the job is cancelled if exceeded. | 5–120 min | 30 |
distribution_parallel_execution_enabled | Distribution modules process targets concurrently. Disable to force sequential execution (one target at a time) for every module as a safety fallback — it wins over distribution_ssh_max_concurrency, which is not consulted while this is off. | on / off | on |
distribution_ssh_max_concurrency | System-level override for SSH distribution concurrency. 0 = use the module config default (10). Higher values speed up large deployments but may hit remote sshd connection limits. | 0–50 | 0 |
distribution_windows_max_concurrency | How many distinct Windows hosts an IIS deploy works on at once; targets on the same host always run one after another. 0 = the default (8). Parallel execution switched off forces 1. | 0–32 | 0 |
distribution_fanout_threshold | Target count above which a distribution is split into parallel child jobs. 0 = disabled (single job for all targets). Recommended: 50+. | 0–500 | 0 |
distribution_fanout_batch_size | Targets per child job when fan-out is active. 0 = default (50). Smaller values create more parallel jobs. For IIS and Exchange the batch is automatically made smaller when it would not fit the execution timeout (details). | 0–200 | 0 |
The three distribution_* fan-out fields drive the fan-out execution engine — see Distribution fan-out.
DNS propagation
These fields control the local propagation gate that runs before the CA is asked to validate a DNS-01 challenge. They matter most on locked-down networks — see DNS propagation settings for scenario guidance.
| Field | What it does | Range | Default |
|---|---|---|---|
dns_propagation_timeout_seconds | Maximum time to wait for DNS challenge records to propagate before giving up on ACME validation. | 30–600 s | 120 |
dns_propagation_poll_interval_seconds | How often propagation is re-checked during validation. Must be less than the propagation timeout (the form enforces this). | 2–60 s | 5 |
dns_resolvers | Resolvers used for the DNS-01 propagation pre-check and, when set, for finding the zone a DNS provider writes the challenge record into (issuance, renewal, record cleanup and the credential test). Entries are host or host:port; bare hosts default to port 53 (e.g. 10.0.0.53 or dns.internal:53); a malformed entry (8.8.8.8:, [::1] without a port) is refused at save time, at most 16 entries — an entry saved before this check must be corrected before General settings can be saved again. Empty = the public set (8.8.8.8, 8.8.4.4, 1.1.1.1) for both the propagation pre-check and the zone lookup. A server that cannot reach public DNS must list its own resolvers here. | list | empty |
dns_propagation_allow_partial | Off (strict, default): on the phased flow a TXT record counts as propagated only when every configured resolver returns it; on the synchronous flow (RFC 2136, Cloudflare, DigitalOcean, OVH, Plesk, or every provider with phased mode off) CertAutoPilot instead asks every authoritative nameserver of the zone directly and waits for all of them. On: a single configured resolver returning the record is enough on both flows, and the authoritative nameservers are not asked — for networks that can reach only one (often internal) resolver. See Propagation settings. | on / off | off |
dns_propagation_skip_precheck | Off (default): manual-DNS Validate first confirms the TXT record is visible via the resolvers above before asking the CA. On: skip the local gate and let the CA validate directly — for split-horizon networks where the local check can't see what the CA sees. | on / off | off |
dns_propagation_phased_disabled | Labelled Phased DNS Propagation in the UI, which shows it inverted (switch on = field false). Phased (default): after presenting the DNS-01 TXT record the worker hands off to a gate that re-checks DNS without holding a worker, until the record is visible or the max wait below passes, then asks the CA to validate. Field true: revert to the synchronous flow, which holds a worker for the in-worker wait (capped at 600 s). RFC 2136 and manual-DNS certificates always use the synchronous/manual path. | on / off | false (phased on) |
dns_propagation_deadline_seconds | Labelled Max Propagation Wait (entered in minutes). Total time the phased gate waits for the record to become visible before the attempt fails and cleans up. 0 = the default. An order with a Windows DNS zone waits at least 2 hours (AD replication and the zone's negative TTL). | 300–14400 s (5–240 min) | 1800 (30 min) |
ca_order_deadline_hours | Labelled CA Order Deadline. How long a CA-connector vendor order may wait — domain validation (record propagation and the vendor's check) plus the vendor's own issuance — before it is given up: the order is closed as expired, the validation record removed and the certificate reports CA_ORDER_DEADLINE_EXCEEDED. The vendor poll holds no worker while it waits, so this can be far longer than the ACME propagation wait. A vendor may cap it lower. 0 = the default. The deadline is stamped when an order is placed, so a change applies to orders placed afterwards — running orders keep the deadline they started with. | 1–168 h | 72 |
The pre-check is only an optimisation — the CA is the authoritative validator and does its own lookup. But if you skip the gate and the record isn't actually ready, a CA validation attempt is wasted, and failed validations count against the CA's rate limits.
See Manual DNS validation for the workflow these settings gate.
UI preferences
| Field | What it does | Range | Default |
|---|---|---|---|
default_page_size | Items shown per page in tables throughout the UI. | 5–100 | 20 |
dashboard_refresh_interval_seconds | Intended dashboard auto-refresh interval. The value is validated and stored, but the dashboard pages currently refresh on a fixed 60-second cycle and do not read it. | 10–3600 s | 60 |
See also
- Scheduler status & sweeps — where the interval settings take effect
- Distribution fan-out
- DNS propagation settings
- Certificate policy & approval workflow