Description | This article describes when the FortiGate is not accessible from GUI and in the putty access, it shows high CPU Utilization. |
Scope | FortiGate. |
Solution |
When the firewall is accessible from the SSH via putty but not through the GUI, a check in PuTTY may reveal that the httpsd daemon is consuming high resources, causing the issue. The httpsd daemon is necessary for the HTTPS server for the GUI access of the FortiGate to present the user interface in the browser.
If the error matches the above screenshot, check the admin-server-cert in the settings:
config sys global
If no admin-server was called, configure the admin certificate as Fortinet_Factory. After making these changes, the CPU utilization will lower to normal and the FortiGate GUI will become accessible. |