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.5.
Device Manager
|
Bug ID |
Description |
|---|---|
|
1240231 |
After upgrading FortiManager to version 7.6.5, remote access to FortiGate devices may fail with the error “Error reading from remote server” when using non-standard ports. |
|
1246821 |
FortiManager retrieve may fail when an admin’s remote-group exists only in the root VDOM and the VDOM order starts with a non-root VDOM, causing invalid reference detection during device addition. |
Others
|
Bug ID |
Description |
|---|---|
|
1247597 |
FortiManager is unable to sync user information from the pxGrid connector. |
Policy and Objects
|
Bug ID |
Description |
|---|---|
|
1245964 |
In FortiOS 7.4.10, CLI syntax changes can cause install failures on low-memory (2GB) models when pushing configuration for:
For more details, please review Special Notices. |
Existing known issues
The following issues have been identified in a previous version of FortiManager and remain in FortiManager 7.6.5.
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. |
Device Manager
|
Bug ID |
Description |
|---|---|
|
980362 |
The Firmware Version column in Device Manager incorrectly shows 'Upgrading FortiGate from V1 to V2' even after a successful upgrade has been completed. |
|
1028515 |
The Greenwich time zone on FortiGate is not supported on the FortiManager. |
|
1112389 |
FortiView and Log View fail to display logs when FortiAnalyzer is configured as a managed device in FortiManager. |
|
1136080 |
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 a FortiGate, which may result in an installation failure. |
|
1136726 |
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". |
FortiSwitch Manager
|
Bug ID |
Description |
|---|---|
|
1227473 |
FortiManager attempts to install set poe-status disable on FSW ports that already have PoE disabled. The issue persists and reoccurs after configuration installation and synchronization. |
Global ADOM
|
Bug ID |
Description |
|---|---|
|
1177672 |
When global policy package assignment fails, it may impacts the policy packages on the ADOM. |
Others
|
Bug ID |
Description |
|---|---|
| 1081121 | The syslog server is unable to receive FortiManager event logs when the reliable option is enabled. |
|
1126662 |
In an 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. |
| 1185269 | The local log syslog feature set facility is not functioning properly. |
|
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. |
| 1203535 | 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. |
|
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 |
|
1230277 |
If the ADOM in an earlier FortiManager version contains DLP dictionary entries named |
Policy and Objects
|
Bug ID |
Description |
|---|---|
|
1101351 |
Unable to create ZTNA Server with SAML SSO Server. |
|
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. |
| 1171027 | NAT64 policy and CNAT cannot be created or modified in FortiManager. |
| 1189177 | The FortiManager configuration attempted to change the order of custom service objects, but this returned an "Unknown action 0" error. |
|
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. |
|
1224582 |
FortiManager tries to delete access-proxy and all ZTNA-related configuration from the firewall. |
|
1224598 |
The Policy Package Diff does not display any differences and throws an error. |
|
1242707 |
Policy package status does not change to "Out of Sync" on FortiManager when local changes are made on FortiGate. |
System Settings
|
Bug ID |
Description |
|---|---|
|
1158131 |
The GUI permits configuring the management port to a port number already in use, resulting in loss of access to the GUI. |