During provisioning, if multiple scripts attempt to modify the aggregate interface, the database installation fails with the following error:

[attribute "vdom" check error - runtime error -2: Virtual domain must be same as virtual domain () for all aggregate/redundant interfaces]

This issue occurs only with aggregate interfaces.

In the HA Status section of the managed FortiGate, the Uptime and State Changed fields are not populated.

Unable to edit route-map due to the following error "rule/2/set-priority is out of range (property: set-priority)"

The maximum number of managed FortiSwitches on FortiManager does not match with the maximum number of managed FortiSwitches by FortiGate, resulting in a copy failure error during installation to FortiGates.

Workaround:

Disabling the central management on FortiManager for FortiSwitch may bypass this error.

Unable to Upgrade the FortiAP or FortiSwitch from FortiManager.

When EMS is added as a Fabric Connector to these FortiGates from FortiManager, all devices appear under FortiManager-managed devices, but only the primary FortiGates serial number is displayed.

In the FortiProxy ADOM type, navigating to Device Manager always redirects to the Feature Visibility page, preventing access to FortiProxy configuration settings. This issue has been observed when the ADOM mode is set to Advanced Mode.

FortiManager constantly changes the UUID of some objects.

FortiManager cannot modify rat-timeout-profile in Policy Packages.

When checking the policy package diff, FortiManager shows that the "system replacemsg spam" entry will be deleted; however, this change is not reflected in the install log.

Installation of "config system ddns" configuration fails.

Unable to move policy packages & move/delete folders. Error "cannot get pkg path" is displayed.

Workaround:

Use the JSON API.

FortiManager attempted to remove internet-service-custom objects from the FortiGates; however, the installation failed due to syntax incompatibility caused by static entries that cannot be deleted.

Workaround:

Recent FortiGuard updates have introduced new static entries on the FortiGates that FortiManager does not recognize. During housekeeping, FortiManager may attempt to delete these entries, assuming they are unused. Create a CLI script to have entries created on the ADOM DB:

config firewall internet-service-custom
    edit "BuiltIn-Brightree-Brightree"
        set comment "BuiltIn ffdb-fqdn entry"
        config entry
            edit 4
            next
            edit 6
                set addr-mode ipv6
            next
        end
    next
    edit "BuiltIn-PagerDuty-PagerDuty"
        set comment "BuiltIn ffdb-fqdn entry"
        config entry
            edit 4
            next
            edit 6
                set addr-mode ipv6
            next
        end
    next
    edit "BuiltIn-JFrog-JFrog"
        set comment "BuiltIn ffdb-fqdn entry"
        config entry
            edit 4
            next
            edit 6
                set addr-mode ipv6
            next
        end
    next
end

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.

FortiGates may be unexpectedly renamed during policy package installation when deploying to multiple devices (more than 5).

Workaround:

Install to less than 5 devices at the same time or create metadata variable to config hostname in system template.

MEAs cannot be enabled from FortiManager's GUI.

Workaround:

Use the following CLI command to enable them (in this example, universalconnector):

config system docker

set status enable

set universalconnector enable

end

In a FortiGate HA setup running on the public cloud platform, the FortiManager attempts to install changes on static routes, which may cause routes to be deleted after an HA failover.

When attempting to upload the firmware image from FortiGuard, FortiManager returns the following error "Code: -1, Invalid image". This issue has primarily been observed on FortiGate hardware platforms running special build firmware versions, where the image contains an encrypted MBR—such as on the FortiGateRugged-70G-5G-Dual, FortiGateRugged-70G, FortiGateRugged-50G-5G, FortiWiFi-70G models.

Unable to add physical FortiProxy to FortiManager.

Unable to upgrade ADOM from v7.2 to v7.4 due to HTTP3(QUIC) error in deep-inspection profile.

The FortiView tile is missing after adding FortiAnalyzer as a managed device to FortiManager.

FortiManager does not properly support the "FortiGate-50G-SFP-POE" platform.

Not able to create a new VDOM or remove any interfaces from VDOMs when Workspace mode is enabled.

Workaround:

Use a script like the following and run it against the Device Database CLI:

config vdom

edit vdom_name

end

FortiManager try to install unset qos-policy and installation fails.

In FortiManager, creating a threat feed connector and applying it to multiple VDOMs results in the same UUID being assigned across all instances. This behavior may lead to duplicate UUID issues.

When no port setting (empty value) has been set for HTTPS on SSL/SSH Inspection Profile, the installation preview shows error, "https ... Must set at least one port (default port:443) or enable ssl inspect-all".

Workaround:

Modify the profile by adding port setting for HTTPS under "Protocol Port Mapping" even if they were disabled. (Enable the option first, input port setting, such as "443", then disable the option and save the profile).

In FortiManager under Policy & Objects > Firewall Objects > Internet Service > IP Reputation Database, most entries show “0” in the Number of Entries column, while the same entries display data on FortiGate devices.

FortiSandbox v5 is not supported for FortiGuard update download (for an air gapped environment).

Unable to import a local certificate into FortiManager. This issue may occur if the certificate is encrypted with a newer OpenSSL version that FortiManager does not yet support.

Workaround:

Convert the latest certificate to the legacy format before uploading it to FortiManager.