Troubleshooting Tip: FortiWeb accessible via SSH but not via graphical user interface (GUI)

Description

This article describes how to troubleshoot an issue where FortiWeb is not accessible via HTTPS that results in the following browser error:

Scope

FortiWeb.

Solution

1. Make sure there are no network issues (bandwidth, connectivity etc.) impacting the https connection between the user and the FortiWeb management interface.

2. Make sure that the administration port used to access the FortiWeb has HTTP/HTTPS enabled for GUI access. This can be checked on the CLI with the command 'show system interface <port>' where <port> is the name of the port for administrative access and the section 'allowaccess':

FortiWeb # show system interface port1
config system interface
    edit "port1"
        set type physical
        set ip 10.189.131.31/24
        set allowaccess ping ssh http https
            config  secondaryip
            end
            config  classless_static_route
            end
        next
    end

If the issue is isolated to FortiWeb, the first action is to restart httpsd as follows:

1. In the CLI, run the command 'diagnose system ps | grep https' to get process IDs of the httpsd daemon. See example output below:

Fortiweb # diagnose system ps | grep https
6078 root 108m S /bin/httpsd
6079 root 108m S /bin/httpsd
11912 root 107m S /bin/httpsd
11913 root 107m S /bin/httpsd
32467 root 108m S /bin/httpsd
23159 root 0 Z [httpsd]
24612 root 3916 S /bin/grep https

2. Kill all process IDs related to httpsd using the command 'diagnose system kill 9 <ID>':

Fortiweb # diag system kill 9 6078
Fortiweb # diag system kill 9 6079
Fortiweb # diag system kill 9 11912
Fortiweb # diag system kill 9 11913
Fortiweb # diag system kill 9 32467