Resolved issues

The following issues have been resolved in FortiADC 8.0.1 release. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.

Bug ID	Description
1205106	In the GUI, the Add Filter option under Network Security > Firewall was incorrectly grayed out and unavailable.
1200598	When HTTPS service was enabled on port2 and port3 in an Active-Active HA cluster, a node could drop out of the cluster due to a GLB process binding failure during HA synchronization. The issue caused temporary cluster instability until the node rejoined.
1194018	After upgrading to version 7.4.8, external connections could experience performance degradation due to dropped packets on the ingress ADC. The issue was caused by an incorrect check in the LRO/GRO handling logic that required TSO to be enabled, resulting in packet drops when receiving large packets assembled by LRO/GRO.
1192054	Maximum Request Header Value Length limit increased to 16,384.
1191529	Editing a virtual server in AP mode failed with a “traffic group conflict” error because traffic group validation was incorrectly applied outside HA VRRP mode.
1190857	Virtual servers experienced timeouts and connection failures due to reverse routing lookups failing after fast forwarding entries expired.
1187948	Certificate configurations were lost after upgrade from 7.4.5 to 7.4.7 because private key passwords containing unescaped double quotes or backslashes caused configuration errors in CMDB.
1184789	FortiSandbox Cloud activation failed through a proxy with “FortiCloud internal error” due to an SSL read timing issue when responses were not received in time.
1184197	FortiADC licensed through FortiFlex remained restricted to VM01 limits despite valid VM08 entitlement due to incorrect CMDB tablesize handling after CPU allocation.
1178580	In Kubernetes environments using the FortiADC Ingress Controller, the SLB virtual server configuration in the GUI displayed an incorrect real server pool reference. When content routing was enabled, the associated real server pool field should have been hidden or disabled, as routing decisions were determined by content rules. The CLI configuration was unaffected.
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.
1168495	The system incorrectly counted SMTP (secure) and Diameter (SSL) services toward the hardware SSL instance limit. The limitation now correctly applies only to HTTPS and TCPS virtual servers.
1165214	In AAG authentication, passwords containing special characters were incorrectly URL-encoded, causing login failures for both local and remote user accounts. The issue has been corrected so that special characters are now processed properly. The characters \, ', and " remain unsupported, consistent with non-AAG local user password limitations.
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.
1153978	The FortiView real server pool statistics page did not display or allow selection of a time span for the traffic graph, unlike other FortiView views.
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.