Web proxy does not work properly to redirect Chrome browser to websites when disclaimer is enabled in proxy policy.

FortiGate web proxy should support forward server on TLS 1.3 certificate inspection connection.

WAD crashed at wad_ssl_port_p2s_supported_versions with signal 11.

HTTP 1.1 host header is lost in FortiGuard web proxy requests.

Abnormal prolonged CPU spike with cmdbsvr and WAD processes when making change to large policy list (10 000+ policies).

Cluster VDOM policy statistics data is not correct when VFID is different for same VDOM on primary/secondary.

Any changes to the security policy table causes the hit count to reset.

Internet service entry not detected due to some IP ranges being duplicated.

Sessions are marked as dirty when a route change happens, but the route still exists.

Policy with Tor-Exit.Node as source is not blocking traffic coming from Tor.

Query string parameters omitted (HTTP redirect, SSL offloading).

append command allows mixing VIP and firewall address as destination objects in a firewall policy.

External threat feed entry 0.0.0.0/0 shows as invalid but it blocks traffic.

When web filter and application control are configured, blocked sessions to play.google.com remain in the session table for 3600 seconds.

Threats drilldown for Sources, Destinations, and Country/Region (1 hour, 24 hours, 7 days) gives the error, Failed to retrieve FortiView data.

After upgrading to 6.4.x from 6.2.5 and earlier, users must clear the browser cache for the best user experience with the new firmware.

RADIUS test fails from the GUI as it does not use the configured Authentication method, and authentication fails; test passes on the CLI.

FortiGates in an HA A-P configuration may lose GUI access to the HA secondary device after a period of 8 days of inactivity, when at least one static IPv6 address is configured on an interface.

GUI does not show the configured external FortiGuard category in the SSL-SSH profile's exempt list.

Unable to select an address group when configuring Source IP Pools for an SSL VPN portal.

Filtering log results with a regular expression incorrectly yields no results.

When creating SD-WAN rules in the GUI, the destination interface preference is not saved when the strategy is manual.

Connectivity test for RADIUS server using CHAP authentication always returns failure.

LAG does not come up after link failed signal is triggered.

Out-of-sync issue caused by firewall address group member is either duplicated or out of order.

HA is failing over due to cmdbsvr crashes.

SCTP sessions are not fully synchronized between primary and secondary devices in version 5.6.11 on FG-3240C.

CSR on cluster primary is generating out-of-sync alerts on secondary and tertiary units.

Both primary and secondary consoles keep printing get_ha_sync_obj_sig_4dir: stat /etc/cert/ca/5c44d531.0 error 2.

SSL VPN related auth login user event logs do not require HA to be in sync.

Inconsistent data from FFDB caused several confsyncd crashes.

Inconsistent values for HA cluster inside the SNMP.

HA cluster uses physical port MAC address at the time of HA failover.

Long sessions lost on new primary after HA failover.

Cannot pass traffic over ADVPN if: tunnel-search is set to nexthop, net-device disable, mode-cfg enable, and add-route disable.

ADVPN spoke one behind NAT shortcut cannot connect to another spoke that is not behind NAT.

User name log empty when IPsec dialup IKEv2 has client RSA certificate with empty subject.

DHCP over IPsec randomly works when net-device is disabled.

IKE HA sync IPsec SA fails on receiver when ESP null crypto algorithm is used.

local-gw is replaced with primary IP on a secondary device when the secondary IP is used as a local-gw.

Application miglogd crashes when numerous DLP logs are generated, where DLP archive files use up system inodes.

Improve local log search logic from aggressive to passive mode to save resources and CPU.

rlogd signal 11 crashes.

The miglogd processes is bound to busy CPUs, even though there are other completely idle CPUs available.

On FG-60F, logging and FortiCloud reporting incorrect IPv6 bandwidth usage for sessions with NPU offload.

Should not be able to set inspection-mode proxy with IPS-enabled only policy.

Application WAD crash several times due to signal alarm.

WAD is crashing with signal 6 in wad_fmem_free when processing SMB2/CIFS.

WAD virtual server with HTTP multiplexing enabled causes crash after server is detached because the HTTP server object is detached from the HTTP session.

DLP FTP proxy with splice option sends delete command to server before data transfer completes.

When Kerberos (negotiate without NTLM) authentication method is used for web proxy user authentication, there may be a rare memory leak issue. This memory leak issue may eventually cause the FortiGate to go into conserve mode once it occurs after many users are authenticated by Kerberos repeatedly over time.

Application WAD crash several times due to signal alarm.

On some smaller models, WAD watchdog times out when there is a lot of SSL traffic.

SSH status in SSL profile changes to deep-inspection from disable after upgrading.

Delete validation is not working for Protecting SSL Server profile.

WAD has multiple signal 11 crashes at wad_ssl_cert_get_auth_status.

WAD memory leak caused by Kerberos proxy authentication.

Wildcard URL filter in proxy mode with ? and * not always handled properly.

FortiGate should be in SSL bypass mode for TLS 1.2 certificate inspection with client certificate request.

Cannot access specific website using proxy-based UTM with certification inspection due to delays from the server in replying to ClientHello message when a second connection from the same IP is also waiting for ClientHello.

Log traffic to remote servers does not follow SD-WAN rules.

set dscp-forward option is missing when using maximize bandwidth strategy in SD-WAN rule.

Health check SLA status log shows configured bandwidth value instead of used bandwidth value.

Kernel does not remove duplicate routes generated by SD-WAN health checks when hostname IP changes.

Need support for SSL VPN web mode traffic to follow SD-WAN rules/policy route.

SD-WAN information available in session list is confusing.

SD-WAN route tag is removed with multiple BGP paths in place.

HA secondary also sends SD-WAN sla-fail-log-period to FortiAnalyzer.

Automation stitch traffic is sent via mgmt with ha-direct to AWS Lambda after upgrading from 6.0.9 to 6.2.3.

SSL VPN crashes on parsing some special URLs.

TX packet drops on SSL root interface.

SMB/CIFS traffic via SSL VPN web mode not using correct SNAT IP (IP pool).

A page inside a bookmark not opening in SSL VPN web mode.

After SSL VPN proxy, one JS file of http://www.cm***-rm***.ca runs with an error.

Traffic cannot pass when SAML user logs in to SSL VPN portal with group match.

Slides on https://re***.nz website are displayed in SSL VPN web mode.

FortiManager tabs/page do not load when accessed via SSL VPN web mode.

SSL VPN daemon crash due to limit-user-login.

FortiGate GUI cannot be rendered and displayed via SSL VPN portal.

With SSL VPN proxy JIRA web application, get one wrong URL without proxy path.

Three of the internal applications/portal bookmarks do not load/partially work with SSL VPN web mode.

Internal SharePoint 2019 website cannot be accessed in SSL VPN web portal.

SSL VPN crashes when accessing a realm with an incorrect user, or when the correct user enters the wrong password.

Cannot authenticate to SSL VPN using 2FA if remote LDAP user and user within RADIUS group has same user name and password.

FortiClient randomly fails to connect to SSL VPN tunnel mode stuck at 98% with two-factor authentication token.

DTLS tunnel performance improvements by allowing multiple packets to be read from the kernel driver, and redistributing the UDP packets to several worker processes in the kernel.

Internal website loading issue in SSL VPN web portal for ca***.fr.

SSL VPN log entries display users from other VDOMs.

SSL VPN crashes in a scenario where a large number of groups is sent to fnbam for authentication.

The system allows enabling split tunnel when the SSL VPN policy is configured with destination all. It is not consistent with 5.6.x and 6.0.x.

Get no more IP address available error when users connect to SSL VPN after upgrading to 6.2.5.

HA cluster not synchronizing when configuring an active LACP with MCLAG via FortiManager.

The ospfNbrState OID takes too long to update.

Link monitor behavior is different between FGCP and SLBC clusters.

When system is in an extremely high memory usage state (~90%), a power supply status Power supply 1 AC is lost might be mistakenly logged.

Error in log, msg="Interface 12345678001-ext:64 not found in the list!", while creating a long name VDOM in FG-SVM.

NP-offloaded active TCP/UDP sessions established over IPsec VPN tunnels will timeout at session TTL expiry.

FG-60F/61F memory usage causes conserve mode by enabling/disabling UTM.

FortiExtender interface admin status changes cannot be detected by FortiManager because the FortiGate checksum does not change.

Rebooting FG-1500D in 5.6.x during upgrade causes an L2 loop on the heartbeat interface and VLAN is disabled on the switch side.

FortiGate restarts FGFM tunnel every two minutes when FortiManager is defined as FQDN.

Interface gets removed from SD-WAN after rebooting when the interface is defined in both SD-WAN and zone.

FG-600E stops sending out packets on its SPF and copper port on NP6.

HQIP loopback test failed with configured software switch.

FortiGuard push update is not working properly from override (FortiManager)

IPv6 push update fails.

SNMP failed to retrieve HA cluster secondary information from secondary serial number in TP mode.

Proxy ARP configuration not loaded after interface shut/not shut.

Wildcard FQDN not resolved on the secondary unit.

Issue when packets from same session are forwarded to each LACP member when NPx offload is enabled.

FG-100F memory configuration check.

Support FortiManager when private-data-encryption is enabled in FortiOS.

Forward or local bi-directional traffic from NPU inter-VDOM links through separate VDOMs is subject to high latency.

FG-100F cannot forward fragmented packets between hardware switch ports.

10G ports x1/x2 cannot be set as interfaces in firewall acl/acl6 policies.

Errors during fuzzy tests on FG-1500D.

NP6 SSE drops after a couple of hours in a stability test.

LTE does not connect after upgrading from 6.2.3 on FG-30E-3G4G models.

FG-100F memory configuration check fails because of wrong threshold.

FG-40F LAN interfaces are down after upgrading to 6.2.4 (build 5632).

FortiGate unable to boot with kernel panic by cmdbsvr when VLAN is configured on redundant interface with non-NPU port.

Interface forward-error-correction setting not honored after reboot.

FG-40F/60F kernel panic if upgrading from 6.4.0 due to configuration file having a name conflict of fortilink as both aggregate interface and virtual switch name.

Interface forward-error-correction setting not honored after reboot. Affected platforms: FG-1100E, FG-1101E, FG-2200E, FG-2201E, FG-3300E, FG-3301E, FG-3400E, and FG-3600E.

SNMP monitoring does not provide the SD-WAN member interface name.

FortiOS is providing self-signed CA certificate intermittently with flow-based SSL certificate inspection.

Unable to configure aggregate interface type on FG-30E-3G4G.

After reboot, forward-error-correction value is not maintained as it should be.

FortiGate not responding to DHCP relay requests from clients behind a DHCP relay.

NP6Xlite traffic not sent over the tunnel when NPU is enabled.

Under some circumstances, it was possible for Update D to create zombie processes.

Existing ffdb_map_res package was not automatically removed after upgrading on small storage FortiGates, even though their creation was removed in 6.2.4.

Policy package push from FortiManager fails the first time, and succeeds the second time if it is blank or has no changes.

FG-40F/41F aggregate interface gets removed after upgrading to 6.2.5 from 6.2.4 firmware version.

The maximum number of IPS supported by each NTurbo load balancer should be 7 instead of 8 on FG-3300E and FG-3301E.

HA LED off issue on FG-1100E/1101E models in 6.0.x.

Empty firewall objects after pushing several policy deletes.

It takes a long time to set the member of a firewall address group when the member size is large. In the GUI, cmdbsvr memory usage goes to 100%. In the CLI, newcli memory usage goes to 100%.

Traffic on VLAN and NPU VDOM link interfaces fails after switching from standalone to HA mode.

Support EoIP acceleration with NP7 platforms.

npd crashes because FOS object is null.

Traffic dropped with NP7 IPsec hardware acceleration when packet size higher than PMTU and lower than tunnel MTU.

Kernel crashes when using FCLF8522P2BTLFTN SFPs on HA interfaces. Affected models: FG-1800F and FG-1801F.

FG-100F/101F may continuously boot upon upgrading from FortiOS 6.4.0.

Workaround: back up the 6.4.0 configuration, perform a clean install via TFTP of FortiOS 6.4.2, and restore the 6.4.0 configuration.

De-authentication of RSSO user does not clear the login from the motherboard.

fnbamd crash.

FortiGate does not send user IP to TACACS server during authentication.

Persistent sessions for de-authenticated users.

REST API authentication fails for API user with PKI group enabled due to fnbamd crash.

FG-VM64-KVM is unable to boot up properly when doing a hard reboot with the host.

Autoscale not syncing certificate among the cluster members.

GUI and CLI interface dropdown lists are inconsistent.

Dynamic address objects are not resolved to all addresses using Azure SDN connector.

AWS Fabric connector always uses root VDOM even though it is not a management VDOM.

Slow route change for HA failover in GCP cloud.

After cloning the OCI instance, the OCID does not refresh to the new OCID.

EIP is not updating properly on FG-VM Azure.

Add URL flow filter counters to SNMP.

User browser gets URL block page instead of warning page when using HTTPS IP URL.

Group name missing on web filter warning page in proxy-based inspection.

foauthd has signal 11 crashes when FortiGate authenticates a web filter category.