Description This article describes how to use FortiManager as local FDS
and the configuration needed on FortiGate. Solution 1) After enabling
service access for 'FortiGate Updates' and 'Web Filtering' on
FortiManager interface, there is option to 'Bi...
Description This article describes how to verify FortiGate to
FortiManager (FGFM) protocol TLS version. Scope FortiGate Solution 1)
Port 541 is the default port for FGFM protocol. To verify the TLS
version, it is possible to run FortiGate build-in pa...
Description This article describes how to troubleshoot SAML login fail
with invalid response. Solution 1) FortiManager/FortiAnalyzer GUI may
return the following error after SAML user authentication.
invalid_response: Could not validate timestamp: no...
Description This article describes available flags on FortiManager
set-dev-upgrade cli command. Solution 1) There are flags in '# diagnose
fwmanager set-dev-schedule' CLI command and multiple flags can be use
separated by '|'. FMG01 # diagnose fwmana...
Description This article describes the configuration needed to display
data in FortiAnalyzer secure SD-WAN monitor. Scope FortiAnalyzer.
Solution A 'No Device Selected' message will appear if FortiAnalyzer
does not receive the necessary SD-WAN logs. ...
Running a sniffer on the FMG may show us some clue here. Try filter
1443, 22, icmp and check the difference.
https://docs.fortinet.com/document/fortimanager/6.4.7/cli-reference/742130/sniffer
I'll suggest to try using custom https port. Probably something to do
with the multihome setup. config system admin setting set https_port
1443end https://10.10.10.2:1443