Resolved issues
The following issues have been resolved in FortiADC 7.6.6 release. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.
|
Bug ID |
Description |
|---|---|
| 1261741 | In GLB FortiView, the host status appeared as "unknown" when the combined character length of the policy, hostname, and domain name exceeded 63. This resulted from an internal hash key truncation bug that incorrectly limited the lookup string to 64 characters instead of 512, though DNS query functionality remained unaffected. |
| 1243266 | In Layer 7 TCP virtual server configurations, FortiADC incorrectly sent TCP resets (RST) immediately following the client SYN. This occurred due to an accumulation of abnormal fnginx worker processes triggered by repeated daemon crashes, or when virtual server names differed only by letter case, which caused configuration update failures during initialization. |
| 1238255 | The SNMP OID for VDOM concurrent connections reported abnormal or excessively high values. This resulted from a synchronization mismatch where the internal VDOM connection counter was decreased multiple times upon session expiration, leading to an underflow and incorrect statistical output. |
| 1235827 | Input validation profiles failed to inspect parameters within decompressed traffic and caused system crashes. This resulted from an out-of-bounds memory write during the decompression process, which prevented security policy enforcement on subsequent application pages and led to CPU spikes and daemon instability. |
| 1232774 | After upgrading to v7.4.8 on the FortiADC 300D, SLB servers in the GLB module failed to retrieve virtual server status when health check options were enabled. This resulted from a communication breakdown between the SLB and GLB modules, which prevented metadata synchronization for Virtual Server Pools and the FortiView Logical Topology. |
| 1222808 | FortiADC sent unexpected, encrypted UDP packets to FortiManager on port 53 every few minutes. This occurred because the URL filter daemon initiated periodic availability checks to FortiGuard Distribution Servers (FDS) even when the Web Filter service was unlicensed and inactive. |
|
1239161 |
Antivirus (AV) profiles triggered "out of memory" errors, causing CPU spikes and FortiGuard update failures. This occurred because the AV engine held memory cache blocks longer than the |