Description This article describes an unsupported configuration that may
cause VPN connections to fail after upgrade to FortiOS v7.4.9. Scope
FortiOS v7.4.9, v7.6.3 and later. Solution If Azure AD auto-connect is
enabled on the FortiClient but not co...
Description This article provides the minimum required firmware versions
for successful multifactor authentication using FortiClient manual code
entry or FortiToken mobile push when connecting to a FortiGate IKEv2
Dialup IPsec gateway. Scope FortiGat...
Description This article describes a known issue that can cause ICMP
traffic to be dropped after an upgrade when using specific models and
configurations. Scope FortiGate with 2GB RAM or less v7.6.0-v7.6.4.
Solution This issue occurs for all models l...
Description This article demonstrates how to request deletion of an
unused FortiCloud Portal account. Scope FortiCloud Portal. Solution A
user attempting to login to FortiCloud will be presented with an account
selection screen if the user exists und...
Description This article clarifies how different EAP methods operate
when performing IKEv2 user authentication on FortiOS. Scope FortiOS v7.2
and later, IKEv2. Solution User authentication for an existing IKEv2
tunnel is enabled by applying the follo...
If it works for SSL VPN, this suggests FortiClient itself has the
required permissions to access the cert. For IPsec, ensure
is enabled for the VPN connection profile. It is
disabled by
default.https://docs.fortinet.com/document/forticlient/7.4.4/xm...
Thread is old, but to avoid the use of fnsysctl (which loses permissions
to read /etc/upd.dat in later firmware versions), use "diagnose test
update info" to retrieve the FortiCare account FortiGate believes it is
registered to.diagnose test update i...
Sometimes, useful info you can only find in one place is wrong! v7.2.11
was released yesterday and v7.0.17->v7.2.11->v7.4.7 is a supported
upgrade path despite breaking the rule of thumb I just gave (v7.2.11
released 2025-02-12, v7.4.7 released 2025-...
It's not because v7.0.17 was new, upgrade from chronologically later
(v7.0.17) releases to chronologically earlier (v7.2.10) releases is not
supported. That's because those upgrade steps are not QA-tested. Upgrade
v7.0.17->v7.2.10 or earlier should b...