FortiDDoS protects from both known and zero day attacks with very low latency. It’s easy to deploy and manage, and includes comprehensive reporting and analysis tools.
This article is an Initial troubleshooting for GUI access issue.
Scope
FortiDDoS VM, FortiDDoS-F.
Solution
To check the GUI access issues:
Take console access to FortiDDoS or SSH. Check the management IP address (that is trying to be accessed) and make sure the correct IP address is used:
show system interface
Run the below command to check the port numbers configured for HTTP, HTTPS, SSH, and Telnet access respectively, and make sure the correct one is used:
config system global
(global) # sh
If the issue persists. Check if the above administrative accesses are enabled at the interface level: allowaccess ping HTTPS SSH HTTP telnetL.
config system interface edit "mgmt1"
sh full
Check if the source IP address is part of the trusted host configuration if any is configured:
show system admin
config system admin
edit admin
set trusted-hosts <-----
Run the below command:
exe nginx-restart <----- Earlier release.
exe restapi-restart <----- Last release (does not affect any other system processes and does not reboot the system see FortiDDoS-F CLI Commands: Tools).
After upgrading to the last family v6.5.x or v7.0.x:
execute recover-gui
Then refresh the browser, and try GUI access.
Note:
As FortiDDoS Best Practices, keep FortiDDoS firmware up to date. The latest patch release has the most fixed bugs and vulnerabilities and should be the most stable. Firmware is periodically updated to add new features and resolve important issues.
