What FortiOS does on its own
FortiOS has a built-in ACME client, documented as ACME certificate support from FortiOS 7.0. You create a local certificate with ACME as the enrolment method, and the FortiGate requests it, answers the challenge itself and replaces it before it expires. The interface it uses is set under config system acme.
The challenge is answered on the FortiGate: HTTP-01 on TCP port 80, and in newer releases TLS-ALPN-01 on TCP port 443. Let’s Encrypt is the default CA. Fortinet also describes using other ACME certificate services from FortiOS 7.0.2.
For one internet-facing FortiGate with a public name, that is often enough.
Why FortiGate ACME renewals fail
Fortinet lists the common causes of renewal failure. Most come down to the CA not reaching the FortiGate on the challenge port:
- Port 80 or 443 is blocked upstream, or a virtual IP or port forward on the same interface takes the traffic.
- Traffic to the ACME server leaves through a different interface than the one configured, for example in an HA cluster.
- From FortiOS 7.6.1 the default IKE TCP port is 443, which can collide with the TLS-ALPN-01 challenge.
- With VDOMs, the ACME settings belong in the global VDOM.
A renewal that fails quietly is only noticed when the certificate expires, so check the expiry of what the FortiGate serves, not only its configuration.
Where the built-in client stops
- Wildcards. CAs such as Let’s Encrypt only issue wildcard names with the DNS-01 challenge, and the FortiGate answers its challenges on the device itself.
- Internal devices. A FortiGate that the CA cannot reach on port 80 or 443 cannot pass HTTP-01 or TLS-ALPN-01.
- Many devices. Each FortiGate renews its own certificates. Nothing tells you centrally which ones failed.
- Shorter lifetimes. Public certificates are moving to 47 days by 2029, as we explain in certificate lifetimes are falling to 200, 100 and 47 days, so every failure mode above happens more often.
Renewing outside the FortiGate
The alternative is to get the certificate elsewhere, with DNS-01, and push it to the FortiGate:
- Issue the certificate from a host that can write the DNS challenge record. No inbound port is needed and wildcards work.
- Import the certificate and key into the FortiGate as a new local certificate, through the REST API.
- Point the settings that use it, such as SSL VPN, the admin interface or SSL inspection profiles, at the new certificate.
- Check that the FortiGate serves the new certificate, and keep the old one until it does.
clm.mt follows these steps: an agent or runner renews with DNS-01, uploads the certificate through the FortiOS API, updates the settings that use it, and can undo the change.
clm.mt status
Preview for FortiGate. Contract-tested APIs. Appliance models and firmware need customer-specific acceptance. See the integrations board for every tested scope, and the documentation to plan a pilot.
Other platform guides
- AD CS certificate autoenrollment and auto renewal
- AWS load balancer certificate renewal with ACM
- Azure Key Vault certificate auto renewal, and when it does not happen
- F5 BIG-IP SSL certificate renewal automation
- IIS SSL certificate auto renewal on Windows Server
- Kubernetes certificate management and TLS Secret renewal
- NetScaler ADC SSL certificate renewal and update
- NGINX SSL certificate auto renewal with ACME
- Palo Alto firewall certificate renewal automation