FortiGate
FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
tpatel
Staff
Staff
Article Id 415768
Description This article describes how to resolve a remote access issue with a managed FortiGate through FortiManager after upgrading the FortiGate to v7.4.9 when a trusted host is configured.
Scope FortiGate v7.4.9.
Solution

The FortiGate is connected to Central Management. 

Capture.PNG

 

Remote GUI access is also enabled on the FortiManager admin profile. Consult the link below to learn how to enable remote GUI access for FortiGate GUI access for a FortiManager administrator: Remotely access a managed FortiGate

 

On FortiManager, go to Device Manager -> Device & Groups, 'right-click' on a managed FortiGate, and select the Remote Access option appears in the context menu. It will redirect to the FortiGate's login page using the following: <FortiManager IP>:<port no>.

After entering correct FortiGate admin credentials, it shows an authentication failure. 


Capture1.PNG

 

FortiGate admin configuration:

 

config system admin
    edit "admin"
        set trusthost1 172.25.188.101 255.255.255.255
        set accprofile "super_admin"
        set vdom "root"
        set password ENC PB2ppeBKl00DyXVppwcXlygRcRTeJsZcelqaI1Nrw+Q/FL+ 
   next
end 

FortiGate System event logs show 'Administrator admin login failed from https(169.254.0.1) because of blocked IP' to check system events logs, go to Log&Report-> System Events.

date=2025-10-20 time=22:05:26 eventtime=1761023126690920065 tz="-0700" logid="0100032002" type="event" subtype="system" level="alert" vd="root" logdesc="Admin login failed" sn="0" user="admin" ui="https(169.254.0.1)" method="https" srcip=169.254.0.1 dstip=169.254.0.2 action="login" status="failed" reason="ip_blocked" msg="Administrator admin login failed from https(169.254.0.1) because of blocked IP"

This issue has been reported and is currently under investigation by Fortinet engineering teams, a workaround is available below.

Workaround:
Add the FGFM management tunnel IP address to the trusted host list for the FortiGate admin, which is used to secure communications between the FortiManager and FortiGates.

FortiGate admin configuration:

 

config system admin
    edit "admin"
        set trusthost1 172.25.188.101 255.255.255.255
                  set trusthost2 169.254.0.1 255.255.255.255
        set accprofile "super_admin"
        set vdom "root"
        set password ENC PB2ppeBKl00DyXVppwcXlygRcRTeJsZcelqaI1Nrw+Q/FL+ 
   next
end 

 

Related article:
Technical Note: Understanding secure SSL connections between FortiManager and managed FortiGate devi...