This section lists known issues in version FortiADC7.0.0, but may not be a complete list. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.
|0777422||In FortiADC deployed in AWS, DNS is resolving fails for SDN connectors (AWS, K8s, etc.).|
|0777345||FortiView page has a code injection risk in Referrer chart.|
|0777188||GLB is unable to connect to SLB and shows licd has failed to bind in SLB.|
|0777062||The aging problem on the Web Anti-Defacement page.|
|0776212||Traffic triggers A6-CORS protection but the log detail and Dashboard cannot display A6 information because currently there is no WAF Signature to support it.|
|0775632||FW NAT indication message "Out interface must be set" is incorrect; the message should indicate "Egress interface" instead of "Out interface".|
|0775509||FortiView OWASP Top10 - A1: 2017 Injection - 1Day - pop-up in the GUI.|
GLB VS may respond to DNS query even when gw is down in HA VRRP mode.
|0773648||In the HA Remote IP Monitor List, the GUI only shows the interfaces under root options, but the non-root interface is shown and can be assigned as a remote IP monitor interface in the CLI.|
|0772424||Duplicated listen port error warning when changing HA mgmt IP.|
|0769454||The SLB L4 debug has no output when the traffic coming from the IP belongs to the geo blocklist.|
|0768852||FortiADC does not withdraw BGP routes when the schedule pool is unavailable.|
|0697575||IPS adds signature check signature with api/fortiguard_proxy/fos file with no response.|