Known issues
Known issues are organized into the following categories:
To inquire about a particular bug or to report a bug, please contact Fortinet Customer Service & Support.
New known issues
The following issues have been identified in version 7.6.4.
Device Manager
|
Bug ID |
Description |
|---|---|
| 1198163 |
When installing an SD-WAN static route via a template, the push fails with a duplicated route error. |
FortiSwitch Manager
|
Bug ID |
Description |
|---|---|
|
1193285 |
When changing the name of a FortiSwitch from FortiSwitch Manager, the next Installation will reset the ports configuration of the switch to default configuration. Workaround: Ensure the switch name in both FortiSwitch Manager and device DB (switch-controller managed-switch) are the same prior to installation. |
Others
|
Bug ID |
Description |
|---|---|
| 1196043 |
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. |
|
1199504 |
When Workspace is in Workflow mode, the fmg-admin may observe "You have no write permission to do this operation" error message when attempting to modify an interface. |
|
1201751 |
Unable to add managed FortiAnalyzer to FortiManager. |
|
1230277 |
If the ADOM in an earlier FortiManager version contains DLP dictionary entries named “ |
Policy & Objects
|
Bug ID |
Description |
|---|---|
| 1198075 |
Upon any modification, policy installation will result in attempt to purge dns-database even though no changes are made to dns database. Workaround: Attach CLI template to device with the
|
|
1212118 |
Reinstalling policy packages for more than three devices may cause the Application Security Console to crash. Workaround:
|
Existing known issues
The following issues have been identified in a previous version of FortiManager and remain in FortiManager 7.6.4.
AP Manager
|
Bug ID |
Description |
|---|---|
| 1086946 |
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. |
| 1173274 | FortiManager is trying to enable ddscan when it is not enabled on ADOM db, device db, and AP Manager profile |
|
1174004 |
After FortiManager's upgrade to 7.4.7, FortiManager may suggest to "set ddscan enable" during the first installation, and this may create some issue on FortiAPs connected to the FortiGate. |
| 1178251 | FortiManager is attempting to unset the auth-cert on the wireless-controller VAP
during every installation. |
|
1204035 |
FAP-231K is not supported by FortiManager. |
Device Manager
|
Bug ID |
Description |
|---|---|
|
1028515 |
The Greenwich time zone on FortiGate is not supported on the FortiManager. |
|
1102790 |
FortiManager pushes the unset auto-connect command to config system lte-modem, where the default value is disabled on FortiOS but still enabled on FortiManager. |
|
1152287 |
HA group-id not inherited from CSV file or from pre-run script. |
|
1173182 |
CLI Template Installation Fails with error message "SSID rename not allowed". |
|
1176785 |
Getting error while importing certificate 'no write permission to do this operation'. Workaround: Run script on device database to import the certificate. |
Others
|
Bug ID |
Description |
|---|---|
| 1126662 |
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. |
| 1143100 |
Unable to add physical FortiProxy to FortiManager. |
|
1158842 |
The FortiManager dashboard FortiGuard license status does not display the same data as shown on the FortiGuard page. |
|
1199504 |
When Workspace is in Workflow mode, the fmg-admin may observe "You have no write permission to do this operation" error message when attempting to modify an interface. |
|
1217534 |
During an upgrade of a 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 |
|
1217951 |
FortiManager may not recognize the 1000F serial number as valid for applying the corresponding Device Blueprint, preventing the CSV file from being loaded. |
Policy & Objects
|
Bug ID |
Description |
|---|---|
| 1160047 |
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. |
| 1181585 | "Where Used" feature does not function. |
| 1196308 | EMS server security posture tags are not fully synchronized with FortiManager; ZTNA tags comment are missing. |
|
1200063 |
Failed to update EMS tags from EMS cloud server on FortiManager v7.6.x. |
|
1209756 |
Policy package installation fails for FGT-30G due to SSL VPN settings not supported by this FortiGate model. |
| 1212118 |
Reinstalling policy packages for more than three devices may cause the Application Security Console to crash. Workaround:
|
|
1215349 |
FortiManager may delete policies or settings during device installation due to concurrent database interactions from tasks like auto-updates, policy installs, or HA-related updates running simultaneously. Workaround: Consider using policy package installations instead of device installations whenever possible. It is recommended to use Installation Preview before committing any changes to FortiGates. If you observe any unexpected actions, run an Integrity Check. If the issue is confirmed, retrieve the device configuration before proceeding. |
| 1218648 | The Alternative Resources setting under AWS connector is not pushed to FortiGate. |
System Settings
|
Bug ID |
Description |
|---|---|
| 1063040 |
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. |
|
1086386 |
Unable to save changes for SNMP users in FortiManager if more than one notification host is configured. Workaround:
|