Skip to main content
pbangari
Staff
Staff
Dec 26, 2022 8:39 AM UTC

Issue using custom server certificate for GUI or HTTPS access in HA setup

  • Oct 21, 2026 1:29 PM UTC
  • 0 replies
  • 1235 views
  • Translate All

Description

An issue when using a server certificate for GUI or HTTPS access to FortiGate(s) in HA setup.

When a custom server certificate is used for GUI or HTTPS access to FortiGate, this configuration is synced to the other members of the cluster as well.

If FQDN or IP addresses are used to access FortiGate, since the FQDN or IP addresses are different and if the certificate has only one FQDN or IP address added as the CN (Common Name), a CN mismatch (invalid certificate error) occurs while accessing the FortiGate.

Scope

FortiOS.

Solution

Example:

If the FortiGate(s) access details are as follows:

Fortigate-1: fqdn- fortigate1.xyz.com (192.168.1.1) and Fortigate-1: fortigate2.xyz.com (192.168.1.2)

It is possible to use a wildcard certificate with fqdn: *.xyz.com or with both fqdn added as CN in the certificate, which holds good for both the FortiGate(s) in HA.

Alternatively, generate a CSR for a new certificate that includes the SAN field, ensuring that all required information is entered correctly.

Enter the FortiGate management IP address or FQDN, depending on how the FortiGate is accessed.

In the SAN field, use DNS:fortigate2.xyz.com for the FQDN and IP:192.168.1.2 for the management IP address. Separate multiple entries with a comma and do not use a space.

For example:

DNS:fortigate2.xyz.com,IP:192.168.1.2


If the FortiGate is accessed using both an FQDN and an IP address, include both entries in the SAN field.

Related documents:

    Risk and Resilience in the Age of AI. An OT Thought Leadership Summit for Houston's Critical Infrastructure Leaders. Date: Thursday, December 3, 2026. Time: 8:30 am - 1:30 pm (CT). Location: The Westin Houston, Memorial City | 945 Gessner Road, Houston, TX 77024