Resolved Issues
The following issues have been fixed in 7.6.4. To inquire about a particular bug, please contact Customer Service & Support.
AP Manager
|
Bug ID |
Description |
|---|---|
| 1131117 | Not able to activate Factory Default profiles; GUI returns error, "The selected platform is no longer supported." |
|
1148572 |
SSID per-device-mapping cannot save the DHCP server settings. |
| 1150508 |
Unable to set the Override Radio feature for managed APs under the AP Manager. |
Device Manager
|
Bug ID |
Description |
|---|---|
| 1094451 | If the Timezone field in the System Template is left blank, FortiManager may apply its default timezone and overwrite the existing timezone on the FortiGates. |
|
1119223 |
FortiManager erroneously tries to "unset annex" on DSL interface on the FortiGate "FGT-50G-DLS". |
| 1129574 | Unable to restrict Firmware upgrade via Admin Profile. |
| 1148864 |
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. |
|
1149973 |
In the HA Status section of the managed FortiGate, the Uptime and State Changed fields are not populated. |
| 1152564 | Unable to edit route-map due to the following error "rule/2/set-priority is out of range (property: set-priority)" |
| 1153376 |
If devices are added to FortiManager after SD-WAN is enabled, then Traffic Shaping/SD-WAN may display No Data or No Records Found. If the user enables SD-WAN after the device is already managed by FortiManager, there should be no issue. |
| 1166830 |
FortiGates may be unexpectedly renamed during policy package installation when deploying to multiple devices (more than 5). |
| 1167436 |
FortiManager displays "retrievehaconffail" error when performing retrieve config for FortiGate's HA cluster. |
FortiSwitch Manager
|
Bug ID |
Description |
|---|---|
| 1097467 |
There is a mismatch in the per-VDOM limit between the Managed FortiSwitch on the FortiManager and the actual FortiGate, causing a copy failure error when installing the configuration. So far, this issue has been observed on the FGT-90G. |
|
1153287 |
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. |
|
1161320 |
FortiManager shows an incomplete FortiSwitch topology compared with FortiGate. |
Global ADOM
|
Bug ID |
Description |
|---|---|
| 1141123 |
Installing the Global Header Policy fails with the error: "invalid value", this issue has been observed after upgrading FortiManager to v7.2.10. |
Others
|
Bug ID |
Description |
|---|---|
| 1065593 | Not able to upgrade ADOM. |
| 1066240 |
The FortiSASE Connector is supported only on FortiManager VM platforms and is not supported on FortiManager hardware models. |
| 1071646 | Formatted Event logs do not display the correct timestamp. |
| 1103008 | Not able to edit DNS Filter profile in FortiProxy ADOM. |
| 1113799 | Unable to upgarde the FortiAP or FortiSwitch form FortiManager. |
| 1125382 | 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. |
| 1142559 | 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. |
| 1145473 | Upgrading ADOM fails with FortiExtender object errors "Fail (errno=0):invalid value" and "fail: err=-999,The string contains XSS vulnerability characters" |
| 1147636 | Universal connector card on Fabric View page is missing under Fabric View > Endpoint/Identity connectors. |
| 1157981 |
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. |
| 1158842 | The FortiManager dashboard FortiGuard license status does not display the same data as shown on the FortiGuard page. |
| 1160086 | Unable to upgrade ADOM from v7.2 to v7.4 due to HTTP3(QUIC) error in deep-inspection profile. |
| 1161082 | FortiManager HA cluster status mismatch between GUI and CLI during force-resync. |
|
1162845 |
It is not possible to delete the FortiExtender after performing a Quick Install on the model FortiGate. The FortiExtender can be deleted from Device Manager > Managed FortiGate > CLI Configuration; however, it will still appear in FortiExtender Manager. |
| 1163922 |
The FortiView tile is missing after adding FortiAnalyzer as a managed device to FortiManager. |
| 1168422 | FortiManager does not properly support the "FortiGate-50G-SFP-POE" platform. |
| 1169450 | When Backup ADOM is enabled and auto-sync is configured, FortiManager is not able to automatically retrieve the changes from FortiGate devices. Devices should remain in sync without the need for manual retrieval. |
| 1170281 |
Not able to create a new VDOM or remove any interfaces from VDOMs when Workspace mode is enabled. |
| 1177051 | "retrievehaconffail" error has been observed when performing retrieve config on the FortiManager GUI. |
| 1188452 | Downstream FortiManagers in cascade mode does not download the Webfilter database from the Upstream FortiManager. |
Policy and Objects
|
Bug ID |
Description |
|---|---|
| 971065 | When the number of Custom Internet Services exceeds 256, installation fails due to this limitation. |
| 1011220 | FortiManager constantly changes the UUID of some objects. |
| 1054707 | FortiManager try to install "unset qos-policy" and installation fails. |
| 1078598 | Unable to import policy due to issues related to the protocol-options feature. |
|
1083504 |
FortiManager attempts to configure the service in the ISDB6 policy (IPv6), but FortiOS rejects it, causing the installation to fail. |
| 1087777 | During policy installation, FortiManager tries to delete firewall address object for the SSID interface UUID causing PP Modifying |
| 1089894 | The Policy Package import may hang indefinitely on a specific FortiGate VDOM due to recursive object references. |
| 1092581 | FortiManager cannot modify rat-timeout-profile in Policy Packages. |
| 1096879 | 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. |
|
1131041 |
Not able to create a ZTNA server due to the certificate error. |
| 1134276 | Installation of "config system ddns" configuration fails. |
| 1142983 | 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. |
| 1152640 |
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". |
| 1154383 |
Unable to move policy packages & move/delete folders. Error "cannot get pkg path" is displayed. |
| 1157272 | When creating a new entry under the Logical Relationship for a DLP dictionary, the Pattern field must be completed only for the applicable entry types; it should remain blank for those that do not require it. |
|
1162327 1113980 |
Install preview may get stuck if another user is simultaneously pushing an install on a different FortiGate within FortiManager. |
| 1167035 | Installation to FortiGates with multiple VDOMs might fail with the following error message: "max entry. object: firewall internet-service-custom. detail: global limit. solution: limit is 512" |
|
1168866 |
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. |
| 1169058 | Installation might fail to these devices "FGT/FWF-30G/31G" due to some unsupported syntax. |
| 1171386 | Install failure might be observed when pushing proxy-based antivirus profile to FortiGate models FGT-40F and FGT-60F. |
| 1173197 | Where Used feature is not working for objects that contain a forward slash (/). |
| 1179704 |
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. |
| 1180805 | FortiManager is attempting to purge the "webfilter ftgd-risk-level"
entries; however, because these are static, default built-in entries on the
FortiGates, the installation fails. |
| 1186242 | Policy package installation with VIP type "server-load-balance" fails when VDOM exception "firewall.vip" is enabled. |
Services
|
Bug ID |
Description |
|---|---|
|
1150398 |
FortiSandbox v5 is not supported for FortiGuard update download (for an air gapped environment). |
| 1170893 | When FortiManager is acting as Local FortiGaurd Servers, FortiClient applications running on Linux machines are not receiving any signature updates. |
System Settings
|
Bug ID |
Description |
|---|---|
|
1151919 |
During policy installation, FortiManager unexpectedly pushed the |
| 1169081 |
When clicking on the Approve this request link in the Workflow mode, the following error message can be observed. "Unable to complete action, failed to 'approve'. " |
VPN Manager
|
Bug ID |
Description |
|---|---|
| 1166323 |
The VPN Manager > IPsec VPN Communities page no longer displays correctly the page loads but shows only a blank (white) screen. |
Common Vulnerabilities and Exposures
Visit https://fortiguard.com/psirt for more information.
| Bug ID | CVE references |
|---|---|
|
1172235 |
FortiManager 7.6.4 is no longer vulnerable to the following CVE Reference:
|
|
1194450 |
FortiManager 7.6.4 is no longer vulnerable to the following CVE Reference:
|