When converting an explicit proxy session to SSL redirect, traffic may be interrupted inadvertently in some situations.

On the Policy & Objects > Firewall Policy page in 6.4.0 onwards, the IPv4 and IPv6 policy tables are combined but the custom section name (global label) is not automatically checked for duplicates. If there is a duplicate custom section name, the policy list may show empty for that section. This is a display issue only and does not impact policy traffic.

Workaround: rename the custom section to unique name between IPv4 and IPv6 policies.

FortiView pages with FortiAnalyzer source incorrectly display a Failed to retrieve data error on all VDOM views when there is a newly created VDOM that is not yet registered to FortiAnalyzer. The error should only show on the new VDOM view.

On the System > FortiGuard page, the override FortiGuard server for AntiVirus & IPS Updates shows an Unknown status, even if the server is working correctly. This is a display issue only; the override feature is working properly.

Managed FortiSwitch and FortiSwitch Ports pages are slow to load when there are many managed FortiSwitches.

The web page cannot be found is displayed when a dashboard ID no longer exists.

Workaround: load another page in the navigation pane. Once loaded, load the original dashboard page (that displayed the error) again.

GUI interface bandwidth widget does not show correct data for tunnel interface when ASIC offload is enabled on the firewall policy.

When there are a lot of historical logs from FortiAnalyzer, the FortiGate GUI Forward Traffic log page can take time to load if there is no specific filter for the time range.

Workaround: provide a specific time range filter, or use the FortiAnalyzer GUI to view the logs.

When a FortiGate is managed by FortiManager with FortiWLM configured, the HTTPS daemon may crash while processing some FortiWLM API requests. There is no apparent impact on the GUI operation.

On a mobile phone, the WiFi captive portal may take longer to load when the default firewall authentication login template is used and the user authentication type is set to HTTP.

Workaround: edit the login template to disable HTTP authentication or remove the href link to googleapis.

On the Log & Report > Forward Traffic page, filtering by the Source or Destination column with negation on the IP range does not work.

GUI shows user as expired after entering a comment in guest management.

Sessions not synchronized to HA secondary on an FGSP and FGCP combined setup.

In the GUI, an FQDN or ISDB can be selected for a DoS policy, which is not supported (an error message appears). The CLI shows the correct options.

The timestamp on the hyperscale SPU of a deny policy (policy id 0) is incorrect.

Traffic shaping profile does not seem to have an effect on TCP/UDP traffic in hyperscale.

The default logtraffic setting (UTM) in a security policy unexpectedly generates a traffic log.

FortiGate does not send WELF (WebTrends Enhanced Log Format) logs.

Traffic denied by security policy (NGFW policy-based mode) is shown as action="accept" in the traffic log.

Slow GUI performance in large Fabric topology with over 50 downstream devices.

The security rating for Admin Idle Timeout incorrectly fails for a FortiAnalyzer with less than 10 minutes.

The dstaddr/dstaddr6 of an SSL VPN policy can be set to all when split tunnel mode is enabled and only the default portal is set.

Forward traffic log does not generate logs for HTTP and HTTPS services with SSL VPN web mode.

Logging in with SSO to FortiAnalyzer with SSL VPN web mode fails.

When NTurbo is enabled, it is unexpectedly provided with the wrong traffic direction information (from server or from client) to decide the destination for the data. This causes the traffic to be sent back to the port where it came from.

The extender daemon crashes on Low Encryption (LENC) FortiGates.

Link status on peer device is not down when the admin port is down on the FG-500E.

A VWP named .. can be created in the GUI, but it cannot be edited or deleted.

Interface belonging to other VDOMs should be removed from interface list when configuring a GENEVE interface.

VXLAN VNI interface cannot be used with a hardware switch.

FortiGate did not restart after restoring the backup configuration via FortiManager after the following process: disable NPU offloading, change NGFW mode from profile-based to policy-based, retrieve configuration from FortiGate via FortiManager, and install the policy package via FortiManager.

Local certificates could not be saved properly, which caused issues such as not being able to properly restore them with configuration files and causing certificates and keys to be mismatched.

Traffic passing through an EMAC VLAN interface when the parent interface is in another VDOM is blocked if NP7 offloading is enabled.

Workaround: set the auto-asic-offload option to disable in the firewall policy.

PSU alarm log and SNMP trap are added for FG-20xF and FGR-60F models.

Random LTE modem disconnections due to certain carriers getting unstable due to WWAN modem USB speed under super-speed.

On FG-100F, no event is raised for PSU failure and the diagnostic command is not available.

After restoring the VDOM configuration, Interface <VLAN> not found in the list! is present for VLANs on the aggregate interface.

DoS offload does not work in 6.4.9 and the npd daemon keeps crashing if the policy-offload-level is set to dos-offload under config system npu. Affected platforms: NP6XLite.

Kernel panic occurs when a virtual switch with VLAN is created, and another port is configured with a trunk.

FG-40F with STP enabled on a hardware switch creates a loop after upgrading to 6.4.9.

FortiToken Mobile push notification not working with dynamic WAN IP service provider.

After updating the FSSO DC agent to version 5.0.0301, the DC agent keeps crashing on Windows 2012 R2 and 2016, which causes lsass.exe to reboot.

SCEP fails to renew if the local certificate name length is between 31 and 35 characters.

When a search is performed on a user (User & Authentication > User Definition page), the search results highlight all the groups the user belongs to.

Azure SDN connector replicates configuration from primary device to secondary device during configuration restore.

FG-VMX manager not showing all the nodes deployed.

Autoscale GCP health check is not successful (port 8443 HTTPS).

During every FortiGuard UTM update, there is high CPU usage because only one vCPU is available.

The security-redirect-url setting is missing when the portal-type is auth-mac.