Resolved issues
The following issues have been resolved in FortiADC 7.6.3 release. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.
|
Bug ID |
Description |
|---|---|
| 1168921 | After upgrading to firmware version 7.6.2, IPv6 routes are missing and the default route becomes inactive due to delayed initialization of rtmd, which fails to load global address information during startup. |
| 1163215 | DNS zone transfers fail through FortiADC when the zone file is large, as the system sends a TCP RST to the backend after partial transfer (~25,000 records), due to an insufficient backend receive buffer size. |
| 1160460 | SCEP certificate retrieval fails when the server returns a full certificate chain containing multiple certificates. |
| 1159739 | In HA mode, when a session with the same 5-tuple is recreated on the primary ADC but maps to a different real server (RS), the updated RS name is not synced to the secondary, resulting in stale session data. |
| 1151892 | FortiADC services were interrupted due to multiple httproxy-ssl crashes, triggered when an HTTPS virtual server received HTTP/2 requests that were not properly processed.
|
| 1150240 | FortiADC (secondary) enters a reboot loop when connected to the network with the heartbeat interface active, triggered by a buffer overflow caused by an excessively long certificate file name. |
| 1143314 | FortiADC drops ESP traffic in an IPsec tunnel setup, replying with ICMPv6 "Unrecognized Next Header" messages. This occurs because ESP packets do not match existing IKEv2-created UDP sessions using 5-tuple keys, preventing proper session association and DNAT processing. |