FortiWeb generates frequent critical event logs stating "Something is wrong with certificate or certificate revoked, errorno(19)." This results from a certificate validation error during FortiGuard Anycast communication, though FDS updates and other services remain unaffected.

Workaround:

Disable the FortiGuard Anycast option using:

config system fortiguard
    set fortiguard-anycast disable
end

When the Login Disclaimer banner is enabled, the GUI becomes inaccessible and returns an ERR_EMPTY_RESPONSE error. The issue occurs due to a null pointer condition during cookie handling in the login disclaimer process.

Important: FIPS users are advised not to upgrade to this release, as the login disclaimer cannot be disabled in FIPS mode. Upgrading under these conditions results in loss of GUI access, leaving only SSH and console access available.

CRL files cannot be restored using the execute backup cert-config and execute restore cert-config commands, and must be manually re-imported after restoring certificate configuration.

Because large CRLs generate substantial encoded data during backup, including them can exceed CMDB capacity and lead to system instability. As a result, these commands intentionally back up and restore only certificate and key objects; the CRL store under /var/log/crl/ remains empty after a restore. Deployments that rely on CRL-based revocation checking will not retain their CRL configuration and may experience incomplete certificate-validation behavior until CRLs are reinstalled.