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.

Starting from version 7.2.11, FortiGate devices use a different password type for the administrator's password field. FortiManager versions released before this change cannot verify the administrator password when installing to an FortiGate, which may result in an installation failure.

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

The upgrade task failed when the FortiManager attempted to send the image to the FortiGates. The image file transfer between FortiManager and FortiGate appeared to fail over the FGFM tunnel. FortiManager timed out and was unable to retrieve the FortiGate version (first observed in FortiGate version 7.6.1)

Workaround:

Enable option "Let Device Download Firmware From FortiGuard" in FortiManager side.

Unable to add physical FortiProxy to FortiManager.

FortiManager attempts to install a config to FortiProxy may result in the removal of physical ports. This can occur randomly and originates from the FortiProxy side, due to syntax support compatibility issues. A fix is planned for the next FortiProxy release.

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

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.

During an upgrade of an FortiGate-HA cluster via FortiManager Cloud, 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

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.