Resolved issues
The following issues have been resolved in FortiADC 7.4.7 release. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.
|
Bug ID |
Description |
|---|---|
| 1128366 | Continuous IPS and AV packet processing can trigger a crash. |
| 1122921 | httproxy crashes when processing XML files with malformed content. The issue occurs when Adaptive Learning or XML Protection functions (XML Limit Check, XML XSS Check, or SQL Injection Check) are enabled, and a malformed XML file is transferred. |
| 1122331 | REST API crashes when generating an all-in-one debug report. |
| 1120243 | FortiADC 1200F reports incorrect traffic and packet counter values in SNMP and CLI due to improper interface name handling, leading to discrepancies in monitoring data. |
| 1119257 | HA fails to establish between FortiADC nodes on firmware version 7.4.7 B0378 due to heartbeat message decoding errors, preventing synchronization between FortiADC-1 and FortiADC-2 KVM nodes. |
| 1118172 | GeoIP database upgrade fails if the version exceeds 256, causing manual import failures and HA secondary sync issues due to improper version validation. |
| 1116174 | An incorrect error message is triggered when upgrading from 7.4.x to a version beyond 7.6.2 without first upgrading to 7.6.2. |
| 1115210 | LDAP authentication fails over ConsolePort due to the admin_auth function not being invoked during login. |
| 1114401 | Request to increase maximum request header value length limit. |
| 1112914 | FortiADC attempts to connect to 8.8.8.8 on port 53 when the DNS is configured to 0.0.0.0, despite the DNS setting being invalid. |
| 1106109 | Connected route not displaying in HA-VRRP due to insufficient rtmd receiving buffer size configuration. |
| 1103348 | FortiADC AntiVirus does not block the EICAR file during upload (HTTP PUT), but can block it during download (HTTP GET) due to lack of support for scanning HTTP PUT traffic. |
| 1091639 | Local certificate import fails when the passphrase for the private key contains a backslash (), which is not handled properly. |
|
1091469 |
Health check status is not properly updated on the secondary device after an HA failover. When the secondary device is promoted to primary, the status in the logical topology is not reflected correctly, leading to a lack of visibility on service availability and no alerts for service changes. |