Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
ariroda
New Contributor

cant connect to fortiwifi web gui but can connect to cli

Hi all,

 

I had to clear the logs on the foriwifi 60c and after doing so the web gui can no longer be accessed from the web browser. Can anyone help my troubleshoot what the issue is ?! it would be greatly appreciated.

 

I have checked that http /https are allowed on the port im trying to access.

8 REPLIES 8
bikash_Shaw
New Contributor III

Hi,

 

Please follow below troubleshooting steps:

1.

show system interface (Internal interface or Wan link)

edit "wan1"  set vdom "root"  set ip aaa.bbb.ccc.ddd 255.255.255.0  set allowaccess ping https ssh <---- Make sure HTTP or HTTPS are listed here 

2.

show sys global

config system global  set admin-port 88 <----- HTTP port  set admin-sport 444 <----- HTTPS Port  set admintimeout 30 

3.

sho sys admin(Username)

config system admin  edit "noTHadmin"  set accprofile "super_admin"  set vdom "root"  set password ENC <password Removed>  next  edit "THadmin"  set trusthost1 192.168.1.0 255.255.255.0 <---- Trusted Host restriction  set accprofile "super_admin"  set vdom "root"  set password ENC <password Removed>  next

 

Please verify above output 

 

Regards

Bikash

ariroda

Hi thanks for the reply but I have allready tried those steps and everything looked fine. Although my ports for admin-port and sport where set to default which shouldnt be an issue.

bikash_Shaw
New Contributor III

Hi,

 

get sys perf top –

This will display all the running processes in the FortiGate (the second column is the process ID’s) note the ones you want to restart.  it will be two “httpsd” processes.

 

Please kill the process 

diag sys kill 11 <process-id>

And Wait for process to restart. Please try this and let me know the result.

 

Regards

Bikash

 

ashukla_FTNT
Staff
Staff

If it happened after clearing the log then most probably due to some internal issue the httpsd process got stuck, so try restarting the process.

 

Run "diag sys top" which will show as following:

 

Run Time: 8 days, 13 hours and 5 minutes 0U, 0N, 0S, 100I; 1957T, 1590F, 93KF pyfcgid 70 S 0.0 1.5 pyfcgid 105 S 0.0 1.5 pyfcgid 106 S 0.0 1.5 pyfcgid 107 S 0.0 1.5 cmdbsvr 45 S 0.0 1.3 miglogd 67 S 0.0 1.1 ipshelper 78 S < 0.0 1.0 httpsd 109 S 0.0 0.9 httpsd 69 S 0.0 0.9 httpsd 108 S 0.0 0.9 thmd 101 S 0.0 0.9 reportd 85 S 0.0 0.8 newcli 123 S < 0.0 0.7 miglogd 103 S 0.0 0.7 newcli 304 R 0.0 0.7 newcli 303 S 0.0 0.7 fgfmd 96 S 0.0 0.7 cw_acd 97 S 0.0 0.7 updated 86 S 0.0 0.6 forticldd 80 S 0.0 0.6

 

Note down the process id (second column) for all the httpsd process (like in above case 109, 69, 108)

Kill the proccess using the command:

diag sys kill 9 <pocess id>

 

Kill all the httpsd process and then try again.

vjoshi_FTNT
Staff
Staff

Hello Ariroda,

 

When you say, 'can connect to cli', do you mean connecting via 'SSH' or 'Console' of the Fortigate?

- Have you tried connecting from a different browser/PC ?

- Any proxy server configured on the browser?

- If the SSH works, but only the GUI has issues, I would recommend you to connect a PC directly to the Fortigate interface and test the GUI access. This will rule out the MTU issues where this kind of issues are mostly seen.

 

 

ariroda
New Contributor

thanks for the great ideas guys. I cant try them yet since the deice is at work but i will try as soon as i get to work and get back to youse.

ariroda
New Contributor

hi guys, restarting the processes worked and i can now coneect to the web gui again, thanks for your help !

ariroda

I can connect to the gui byt everytime i go to the log&report tab it timesout, and i have to restart the httpd process to get back in. Anyone got any ides ?

Labels
Top Kudoed Authors