Description This article demonstrates how to decommission the existing
evaluation VM when a new evaluation license request fails with 'Error
downloading license: invalid serial number'. Scope FortiOS VM 7.2.1 and
later using an evaluation license. So...
Description This article describes how to request a permanent trial
license if FortiGate has an existing license uploaded. Scope FortiGate
v7.2.1 and later. Solution On v7.2.1 and above, one permanent trial
license is available per the FortiCare acco...
Description This article describes why with default configuration,
local-out traffic logs are not visible in memory logs. Scope FortiGate.
Solution By default, FortiGate does not log local traffic to memory.
However, the reason is different depending...
Description This article discusses FortiOS behavior when applying
administrative lockout after multiple invalid API keys are seen from the
same IP address. In particular, this article notes the increasing
lockout duration caused by repeated invalid A...
Description This article describes the default FortiOS Destination NAT
behavior when Central NAT is not in use. Scope FortiOS. Solution This
article assumes central NAT is disabled. For configuring Destination NAT
when central NAT is enabled, see 'Ce...
Hi Toshi,I can believe it. The Change Log has since been updated again
and CVE-2024-47575 is referenced in Resolved Issues.As you've noticed,
not all Known or Resolved Issues appear immediately in Release Notes.
Some never appear. For urgent releases...
That sounds like you may already have a renewing certificate you can
use. Verify that acme is using correct interface for renewal with
cli:get system acme statusYou can review logs of acme activity with the
following (produces a lot of text)diagnose ...
TBC,I am assuming you are using ssl vpn with a manual letsencrypt
certificate. If so the following advice applies.You can follow the
procedure in the admin guide to get a new letsencrypt certificate that
autorenews with
acme:https://docs.fortinet.com...
Hello,If the Fortigate only has one active default route, this may be
the source of your issue. You are correct that the loose RPF check only
requires one active route in the routing table. Unfortunately,
advertising a route to the Fortigate does not...