The FortiAP upgrade via FortiManager may fail (on FortiGate 7.6.1). The process could stop at the controller_download_image step or experience a prolonged stall, eventually resulting in a timeout.

When SSID configured with per-device mapping, during the installation, the FortiManager will report error: Commit failed: ssid fortinet is used by vap.

The Firmware Version column in Device Manager incorrectly shows 'Upgrading FortiGate from V1 to V2' even after a successful upgrade has been completed.

The Greenwich time zone on FortiGate does not supported on the FortiManager.

FortiView and Log View fail to display logs when FortiAnalyzer is configured as a managed device in FortiManager.

Enabling the Power Supply Failure option in an SNMP v2 configuration applied via a System Template results in the following installation error: multi-option(power-blade-down) not exist".

Certificate generation fails when using variable mapping in SAN field with a certificate template.

The install preview does not load if a device in the device group is offline, but it works fine if all the devices are online.

Workaround:

Unselect the offline device to allow the install preview to function.

When centrally managing switches via FortiManager, the "Switch-id" is limited to 16 characters. Configuring a hostname exceeding this limit triggers the error: "Switch-id: Value too long."

When global policy package assignment fails, it may impacts the policy packages on the ADOM.

Geography field is blank when creating firewall address type in FortiProxy ADOM.

Workaround:

Create a CLI template with these addresses and add them to fw policy.

The syslog server is unable to receive FortiManager event logs when the reliable option is enabled.

Unable to add physical FortiProxy to FortiManager.

The API interface performance in version 7.6 may appear slower compared to previous versions.

The local log syslog feature set facility is not functioning properly.

Copy Policy Package operations may take longer than usual and remain stuck for an extended duration, even for small changes. This issue may occur when FortiOS does not return a response to FGFM requests from FortiManager.

Failed to create Event Handlers or Reports on FortiManager when a Fortinet Fabric Connection is established on FortiAnalyzer to connect to the FortiManager device.

Workaround:

Go back to the specific ADOM on FortiAnalyzer and create the Event Handlers or Reports there. After synchronization, the new entries should become available on FortiManager.

FortiManager does not support the diagnose fdsm fap-fsw-contract-download request, so the fgdhttpd daemon rejects FortiGate attempts to retrieve FortiAP/FortiSwitch registration status.

Central-management settings are deleted on the primary unit when adding a FortiProxy HA cluster via Device Discover. This issue may occur when the FortiManager ADOM is configured in backup mode and the FortiProxy central-management setting is also set to the backup mode. Refreshing the device may trigger the issue.

Workaround:

Add both devices in the cluster as two separate units instead of as one device.

During an upgrade of an FortiGate-HA cluster via FortiManager, if the disk-check feature is enabled, it may cause all cluster members to reboot simultaneously. This can result in an unexpected traffic interruption.

Workaround:

To prevent this issue, disable the disk check before performing the upgrade:

config fmupdate fwm-setting

set check-fgt-disk disable

end

If the ADOM in an earlier FortiManager version contains DLP dictionary entries named fg-* which are reserved in FortiManager 7.6 the upgrade from ADOM 7.4 to 7.6 will fail. The upgrade process attempts to copy these reserved-name objects, but ADOM 7.6 does not allow them to be created or modified.

ADOM upgrade from 7.4 to 7.6 may fail repeatedly during the dynamic_mapping copy phase with the error message: "unexpected input."

Workaround:

Manual deletion of dynamic mappings prior to the upgrade.

FortiManager instances deployed on Azure may lose all data—including configuration, logs, and reports—if the VM is deallocated and subsequently reallocated.

This may occur during Azure-level operations such as VM stop (deallocate) or SKU/size changes. Please refer to the Special Notices for more information.

Unable to create ZTNA Server with SAML SSO Server.

Application control category "GenAI" is missing in FortiManager, but present in FortiGate.

Workaround:

Copy a FortiGate application list (Applist) from the CLI that includes Category 36, and insert it into a CLI template in FortiManager. Assign CLI template to FortiGate.

NAT64 policy and CNAT cannot be created or modified in FortiManager.

The FortiManager configuration attempted to change the order of custom service objects, but this returned an "Unknown action 0" error.

Failed to update EMS tags from EMS cloud server on FortiManager v7.6.x.

The installation may fail with a Current passphrase is invalid error. This can occur when installing an SSID with an MPSK profile, where the MPSK passphrase is not inherited during copy operations or after a FortiManager upgrade.

Policy package installation fails for FGT-30G due to SSL VPN settings not supported by this FortiGate model.

FortiManager tries to delete access-proxy and all ZTNA-related configuration from the firewall.

The Policy Package Diff does not display any differences and throws an error.

Policy package status does not change to "Out of Sync" on FortiManager when local changes are made on FortiGate.

In FortiOS 7.4.10, CLI syntax changes can cause install failures on low-memory (2GB) models when pushing configuration for:

• web-proxy global proxy-fqdn

• firewall ssl-ssh-profile ssh

For more details, please review Special Notices.

Policies disappear from policy block GUI when policy block name contains '/' character.

Workaround:

Remove the '/' character from the policy block name.

The GUI permits configuring the management port to a port number already in use, resulting in loss of access to the GUI.