Created on
03-09-2018
02:36 AM
Edited on
02-02-2025
09:31 PM
By
Anthony_E
Description
This article describes how to enable remote management for FortiGate.
Scope
FortiGate v7.0 and v7.2.
Solution
Below example port2:
Choose 'OK' to save changes after changes https, http, ssh disabled on the interface.
Using CLI.
Enable the admin access:
config system interface
edit <external-interface-name>
set allowaccess ping https http ssh telnet <---- The setting will only allow admin access to the interface.
end
Disable the Admin access:
config system interface
edit <external-interface-name>
set allowaccess ping <----- The setting will only allow pings to the interface.
end
For remote access only: The trusted host subnet should be set to the public IP address of the client’s connection, not the private IP address of the computer.
For both remote and local access: The trusted host subnet should include both the local IP address (used within your network) and the public IP address (used for external connections).
Depending on the configuration of inbound services on the FortiGate unit, HTTPS access may be in conflict.
For example, if a static NAT Virtual IP is configured to use the interface IP of your FortiGate unit, all data received on that IP is forwarded to the internal server. If this is the case explore shared, web-based remote access options.
Related article:
Working with the Technical Assistance Center (TAC) - Remote Management Access
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.