Resolved issues
The following issues have been resolved in FortiADC 7.6.7 release. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.
|
Bug ID |
Description |
|---|---|
| 1286617 | When executing a stream script using the LB:upstream or LB:set_peer functions, Layer 7 load balancing traffic is incorrectly routed to arbitrary real servers within a pool. This occurs when multiple real servers share an identical IP address but use different service ports, as the server selection mechanism fails to compare port numbers during configuration lookup. |
| 1286214 | Administrators cannot log in to the FortiADC GUI due to an HTTP 401 error, while CLI access remains functional. In high-density GSLB topologies, frequent Virtual Server status transitions generate an excessive volume of system log files, exhausting the storage capacity of the /tmp directory partition due to a lack of file rotation and size limit constraints. |
| 1282339 | Virtual IP (VIP) addresses remain bound to the kernel IP stack and continue responding to ICMP echo requests after their associated Virtual Server and NAT objects are disabled or deleted. This occurs when an IP address is shared simultaneously between a 1-to-1 NAT configuration and a Layer 4 or Layer 7 Virtual Server, as the address validation check fails to evaluate the operational status of matching objects before suppressing netlink IP removal commands. |
| 1281066 | The GUI Security widget continues to display Bot Detection (crawler) event statistics after a source IP exception has been configured. While the exception successfully suppresses the generation of new traffic logs, the security dashboard statistics module incorrectly bypasses the allowlist validation logic, counting matching traffic events despite the active exception. |
| 1273070 | Custom error pages embedded within an iframe display with truncated bottom content due to an unreliable iframe onload height calculation that fails to capture the full vertical dimension of the document. |
| 1272167 | SNMPv3 traps may fail to be processed by third-party monitoring tools (such as Zabbix) due to a lack of support for EngineID discovery through the snmpFrameworkMIB OID. Despite the EngineID being included in the trap packet, certain external management systems require this specific OID to establish the synchronization necessary for secure SNMPv3 communication. |
|
1271938 |
HTTP/HTTPS health checks configured with basic authentication credentials fail unexpectedly, causing functional real servers to be marked as down. This occurs when the backend server responds with an HTTP 401 Unauthorized status but omits the WWW-Authenticate header, preventing the health check daemon from executing its secondary credentialed probe. |
|
1271727 |
In GLB topologies, SNMP queries tracking global Virtual Server status incorrectly return an Unknown string for generic server members. While the FortiADC GUI accurately reflects the active operational state of these backend resources, the SNMP monitoring subsystem fails to poll or mirror the member-specific status updates. |
|
1265994 |
HTTP health checks using HTTP CONNECT (with Local CONNECT or Remote CONNECT) intermittently stopped functioning and caused elevated CPU utilization. This resulted from a data size mismatch between expected and received health check responses, which caused the health check process to hang and required a manual process restart to restore monitoring and traffic flow. |
|
1263251 |
Attempts to create an aggregate interface failed with "System API error" or "Enslave failed" messages. This occurred because an interface previously involved in a failed VLAN assignment remained internally locked by the system, preventing it from being added as a slave to the new aggregate master. |
|
1262109 |
Custom health check scripts failed to execute following a configuration restore or migration to a new platform. This was caused by a synchronization error between the primary configuration directory and the temporary execution environment ( |
| 1245170 | The config-sync process intermittently reported "synconf fails" or "there was some errors in configuration" despite the settings successfully synchronizing between devices. This resulted from transient CLI execution failures during the merge process, where the system incorrectly flagged non-critical processing delays or configuration order mismatches as functional errors. |